[PATCH 10/12] staging: ccree: drop no longer used macro

MSB64 macro is no longer used or needed. Drop it. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_hw_queue_defs.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/ccree/cc_hw_queue_defs.h b/drivers/staging/ccree/cc_hw_queue_defs.h index

[PATCH 11/12] staging: ccree: remove dead code

Remove some unused macro definitions from hash definitions. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/hash_defs.h | 31 +++ 1 file changed, 3 insertions(+), 28 deletions(-) diff --git a/drivers/staging/ccree/hash_defs.h

[PATCH 10/12] staging: ccree: drop no longer used macro

MSB64 macro is no longer used or needed. Drop it. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_hw_queue_defs.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/ccree/cc_hw_queue_defs.h b/drivers/staging/ccree/cc_hw_queue_defs.h index ec2113a..f12761a 100644

[PATCH 11/12] staging: ccree: remove dead code

Remove some unused macro definitions from hash definitions. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/hash_defs.h | 31 +++ 1 file changed, 3 insertions(+), 28 deletions(-) diff --git a/drivers/staging/ccree/hash_defs.h

[PATCH 12/12] staging: ccree: whitespace fixes

A bunch of whitespace fixes pointed to by checkpatch. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_regs.h| 4 +- drivers/staging/ccree/dx_crys_kernel.h | 308 - drivers/staging/ccree/dx_host.h| 256

[PATCH 12/12] staging: ccree: whitespace fixes

A bunch of whitespace fixes pointed to by checkpatch. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_regs.h| 4 +- drivers/staging/ccree/dx_crys_kernel.h | 308 - drivers/staging/ccree/dx_host.h| 256 +-- 3

[PATCH 06/12] staging: ccree: move request_mgr to generic bitfield ops

request_mgr was using custom bit field macros. move over to standard kernel bitfield ops. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_regs.h | 5 + drivers/staging/ccree/ssi_request_mgr.c | 19 +-- 2 files changed, 14

[PATCH 08/12] staging: ccree: remove unused struct

struct SepHashPrivateContext is not used anywhere in the code. Remove it. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/hash_defs.h | 17 - 1 file changed, 17 deletions(-) diff --git a/drivers/staging/ccree/hash_defs.h

[PATCH 06/12] staging: ccree: move request_mgr to generic bitfield ops

request_mgr was using custom bit field macros. move over to standard kernel bitfield ops. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_regs.h | 5 + drivers/staging/ccree/ssi_request_mgr.c | 19 +-- 2 files changed, 14 insertions(+), 10 deletions(-)

[PATCH 08/12] staging: ccree: remove unused struct

struct SepHashPrivateContext is not used anywhere in the code. Remove it. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/hash_defs.h | 17 - 1 file changed, 17 deletions(-) diff --git a/drivers/staging/ccree/hash_defs.h b/drivers/staging/ccree/hash_defs.h index

[PATCH 00/12] staging: ccree: addtional driver cleanups

This is another batch of clean ups for the ccree driver. Mostly comprised of: - Coding Style fixes - Move to kernel infrastructure from custom constructs - Removal of dead code Gilad Ben-Yossef (12): staging: ccree: correct coding style violations staging: ccree: move to kernel

[PATCH 00/12] staging: ccree: addtional driver cleanups

This is another batch of clean ups for the ccree driver. Mostly comprised of: - Coding Style fixes - Move to kernel infrastructure from custom constructs - Removal of dead code Gilad Ben-Yossef (12): staging: ccree: correct coding style violations staging: ccree: move to kernel

[PATCH 01/12] staging: ccree: correct coding style violations

cc_crypto_ctx.h had multiple coding style violations reported by checkpatch. Fix them all. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_crypto_ctx.h | 66 +-- 1 file changed, 32 insertions(+), 34 deletions(-) diff --git

[PATCH 01/12] staging: ccree: correct coding style violations

cc_crypto_ctx.h had multiple coding style violations reported by checkpatch. Fix them all. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_crypto_ctx.h | 66 +-- 1 file changed, 32 insertions(+), 34 deletions(-) diff --git

Re: [x86/mm] e2a7dcce31: kernel_BUG_at_arch/x86/mm/tlb.c

On Sat, 2017-05-27 at 09:00 -0700, Andy Lutomirski wrote: > On Sat, May 27, 2017 at 6:31 AM, kernel test robot > wrote: > > > > FYI, we noticed the following commit: > > > > commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rework > > lazy TLB to track the actual

Re: [x86/mm] e2a7dcce31: kernel_BUG_at_arch/x86/mm/tlb.c

On Sat, 2017-05-27 at 09:00 -0700, Andy Lutomirski wrote: > On Sat, May 27, 2017 at 6:31 AM, kernel test robot > wrote: > > > > FYI, we noticed the following commit: > > > > commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rework > > lazy TLB to track the actual loaded mm") > >

Re: [PATCH] clocksource: moxart: Add AST2500 compatible string

On Thu, May 25, 2017 at 10:28 PM, Daniel Lezcano wrote: > Shouldn't the compatible string be: > > "aspeed,ast2400-timer", "faraday,fttmr010" > "aspeed,ast2500-timer", "faraday,fttmr010" Actually not this time. The Gemini and Moxart timers are

Re: [PATCH] clocksource: moxart: Add AST2500 compatible string

On Thu, May 25, 2017 at 10:28 PM, Daniel Lezcano wrote: > Shouldn't the compatible string be: > > "aspeed,ast2400-timer", "faraday,fttmr010" > "aspeed,ast2500-timer", "faraday,fttmr010" Actually not this time. The Gemini and Moxart timers are compatible with the pure Faraday

Re: [PATCH] clocksource: moxart: Add AST2500 compatible string

On Tue, May 16, 2017 at 9:58 AM, Andrew Jeffery wrote: > Also clean up space-before-tab issues in the documentation. > > Signed-off-by: Andrew Jeffery Reviewed-by: Linus Walleij Does this collide with Daniel's 2500 patch? Sorry for

Re: [PATCH] clocksource: moxart: Add AST2500 compatible string

On Tue, May 16, 2017 at 9:58 AM, Andrew Jeffery wrote: > Also clean up space-before-tab issues in the documentation. > > Signed-off-by: Andrew Jeffery Reviewed-by: Linus Walleij Does this collide with Daniel's 2500 patch? Sorry for the mess, tell me if I need to fix something up :( Yours,

Re: [PATCH] clocksource/drivers/fttmr010: Fix aspeed-2500 initialization

On Fri, May 26, 2017 at 10:48 AM, Daniel Lezcano wrote: > The recent changes made the fttmr010 to be more generic and support different > timers with a very few differences like moxart or aspeed. > > The aspeed timer uses a countdown and there is a test against the

Re: [PATCH] clocksource/drivers/fttmr010: Fix aspeed-2500 initialization

On Fri, May 26, 2017 at 10:48 AM, Daniel Lezcano wrote: > The recent changes made the fttmr010 to be more generic and support different > timers with a very few differences like moxart or aspeed. > > The aspeed timer uses a countdown and there is a test against the aspeed2400 > compatible string

RE:

Hello Friend I Have a Proposal for your kindly contact me via: emz...@outlook.com Thank You. ü Mielőtt kinyomtatja ezt az e-mailt, gondoljon a környezetre. P Please consider the environment before printing this email. *** Ezt az emailt a Websense ESG ellenőrizte a BKV

RE:

Hello Friend I Have a Proposal for your kindly contact me via: emz...@outlook.com Thank You. ü Mielőtt kinyomtatja ezt az e-mailt, gondoljon a környezetre. P Please consider the environment before printing this email. *** Ezt az emailt a Websense ESG ellenőrizte a BKV

Re: [PATCH 7/7] clocksource: Rename CLKSRC_ACPI

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The config option name is now renamed to 'CLKSRC_ACPI' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by:

Re: [PATCH 7/7] clocksource: Rename CLKSRC_ACPI

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The config option name is now renamed to 'CLKSRC_ACPI' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH 6/7] clocksource: Rename CLKSRC_OF to TIMER_OF

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The config option name is now renamed to 'TIMER_OF' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano After fixing the

Re: [PATCH 6/7] clocksource: Rename CLKSRC_OF to TIMER_OF

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The config option name is now renamed to 'TIMER_OF' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano After fixing the offset thing found by Shawn: Reviewed-by: Linus Walleij

Re: [PATCH 5/7] clocksource: Rename clksrc

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The table name is now renamed to 'timer' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by: Linus Walleij

Re: [PATCH 5/7] clocksource: Rename clksrc

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The table name is now renamed to 'timer' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH 4/7] clocksource: Rename CLOCKSOURCE_ACPI_DECLARE

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The macro name is now renamed to 'TIMER_ACPI_DECLARE' for consistency > with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by:

Re: [PATCH 4/7] clocksource: Rename CLOCKSOURCE_ACPI_DECLARE

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The macro name is now renamed to 'TIMER_ACPI_DECLARE' for consistency > with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano Reviewed-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH] platform/x86: ideapad-laptop: Expose conservation mode switch

On 5/27/17 3:31 PM, Hao Wei Tee wrote: > This exposes the battery conservation mode present on some (?) IdeaPads. > The mode is set by calling ACPI method SBMC with argument 3 (on) or > 5 (off). Status is reported in bit 5 of the return value of ACPI method > GBMD. > > This patch was written

Re: [PATCH] platform/x86: ideapad-laptop: Expose conservation mode switch

On 5/27/17 3:31 PM, Hao Wei Tee wrote: > This exposes the battery conservation mode present on some (?) IdeaPads. > The mode is set by calling ACPI method SBMC with argument 3 (on) or > 5 (off). Status is reported in bit 5 of the return value of ACPI method > GBMD. > > This patch was written

Re: [PATCH] macintosh: move mac_hid driver to input/mouse.

On Sun, 2017-05-28 at 11:47 +0200, Michal Suchanek wrote: > On Tue, 9 May 2017 17:43:27 -0700 > Dmitry Torokhov wrote: > > > Hi Michal, > > > > On Tue, May 09, 2017 at 09:14:18PM +0200, Michal Suchanek wrote: > > > There is nothing mac-specific about this driver.

Re: [PATCH] macintosh: move mac_hid driver to input/mouse.

On Sun, 2017-05-28 at 11:47 +0200, Michal Suchanek wrote: > On Tue, 9 May 2017 17:43:27 -0700 > Dmitry Torokhov wrote: > > > Hi Michal, > > > > On Tue, May 09, 2017 at 09:14:18PM +0200, Michal Suchanek wrote: > > > There is nothing mac-specific about this driver. Non-mac hardware > > > with

Re: [PATCH] x86/kernel: Add generic handler for NMI events

Hi Adrien, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.12-rc2 next-20170526] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] x86/kernel: Add generic handler for NMI events

Hi Adrien, [auto build test ERROR on tip/auto-latest] [also build test ERROR on v4.12-rc2 next-20170526] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v5 1/7] staging: atomisp: Fix calling efivar_entry_get() with unaligned arguments

efivar_entry_get has certain alignment requirements and the atomisp platform code was not honoring these, causing an oops by triggering the WARN_ON in arch/x86/platform/efi/efi_64.c: virt_to_phys_or_null_size(). This commit fixes this by using the members of the efivar struct embedded in the

[PATCH v5 1/7] staging: atomisp: Fix calling efivar_entry_get() with unaligned arguments

efivar_entry_get has certain alignment requirements and the atomisp platform code was not honoring these, causing an oops by triggering the WARN_ON in arch/x86/platform/efi/efi_64.c: virt_to_phys_or_null_size(). This commit fixes this by using the members of the efivar struct embedded in the

[PATCH v5 3/7] staging: atomisp: Set step to 0 for mt9m114 menu control

menu controls are not allowed to have a step size, set step to 0 to fix an oops from the WARN_ON in v4l2_ctrl_new_custom() triggering because of this. Signed-off-by: Hans de Goede --- drivers/staging/media/atomisp/i2c/mt9m114.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v5 2/7] staging: atomisp: Do not call dev_warn with a NULL device

Do not call dev_warn with a NULL device, this silence the following 2 warnings: [ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO [ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO We could switch to using pr_warn for dev == NULL instead, but as

[PATCH v5 3/7] staging: atomisp: Set step to 0 for mt9m114 menu control

menu controls are not allowed to have a step size, set step to 0 to fix an oops from the WARN_ON in v4l2_ctrl_new_custom() triggering because of this. Signed-off-by: Hans de Goede --- drivers/staging/media/atomisp/i2c/mt9m114.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v5 2/7] staging: atomisp: Do not call dev_warn with a NULL device

Do not call dev_warn with a NULL device, this silence the following 2 warnings: [ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO [ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO We could switch to using pr_warn for dev == NULL instead, but as

Re: [PATCH] regulator: bd9571mwv: Statize local symbols

On 05/28/2017 08:02 AM, Axel Lin wrote: > These functions are only used by this driver, make them static. > > Signed-off-by: Axel Lin Obviously correct, Acked-by: Marek Vasut > --- > drivers/regulator/bd9571mwv-regulator.c | 12 ++-- > 1

Re: [PATCH] regulator: bd9571mwv: Statize local symbols

On 05/28/2017 08:02 AM, Axel Lin wrote: > These functions are only used by this driver, make them static. > > Signed-off-by: Axel Lin Obviously correct, Acked-by: Marek Vasut > --- > drivers/regulator/bd9571mwv-regulator.c | 12 ++-- > 1 file changed, 6 insertions(+), 6 deletions(-)

Re: [PATCH 1/3] ipc: convert ipc_namespace.count from atomic_t to refcount_t

On 05/27/2017 09:41 PM, Kees Cook wrote: On Mon, Feb 20, 2017 at 3:29 AM, Elena Reshetova wrote: refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter

Re: [PATCH 1/3] ipc: convert ipc_namespace.count from atomic_t to refcount_t

On 05/27/2017 09:41 PM, Kees Cook wrote: On Mon, Feb 20, 2017 at 3:29 AM, Elena Reshetova wrote: refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to

Re: [PATCH 00/11 linux-next] super magic values consolidation

> On 28 May 2017 at 11:34 Christoph Hellwig wrote: > > > On Sun, May 21, 2017 at 05:39:47PM +0200, Fabian Frederick wrote: > > This small patchset reorganizes magic.h and fixes filesystems > > which defined locally super magic values. > > And what's the point? Current

Re: [PATCH 00/11 linux-next] super magic values consolidation

> On 28 May 2017 at 11:34 Christoph Hellwig wrote: > > > On Sun, May 21, 2017 at 05:39:47PM +0200, Fabian Frederick wrote: > > This small patchset reorganizes magic.h and fixes filesystems > > which defined locally super magic values. > > And what's the point? Current magic.h organization is

pull request: linux-firmware: update cxgb4 firmware

Hi, Kindly pull the new firmware from the following URL. git://git.chelsio.net/pub/git/linux-firmware.git for-upstream Thanks Ganesh The following changes since commit c990aae817a1606a1fbeb0b4aac00f93dfce0e32: cxgb4: update firmware to revision 1.16.45.0. (2017-05-28 04:17:45 -0700) are

pull request: linux-firmware: update cxgb4 firmware

Hi, Kindly pull the new firmware from the following URL. git://git.chelsio.net/pub/git/linux-firmware.git for-upstream Thanks Ganesh The following changes since commit c990aae817a1606a1fbeb0b4aac00f93dfce0e32: cxgb4: update firmware to revision 1.16.45.0. (2017-05-28 04:17:45 -0700) are

Re: [PATCH V3] nvme: fix multiple ctrl removal scheduling

On Sun, May 28, 2017 at 11:40:43AM +0200, Christoph Hellwig wrote: > Hi Rakesh, > > this looks reasonable, but we'll need to also adopt the non-PCI > driver to the new state machine. I can give this a spin. > .. Thanks for handling non-PCI driver part.

Re: [PATCH V3] nvme: fix multiple ctrl removal scheduling

On Sun, May 28, 2017 at 11:40:43AM +0200, Christoph Hellwig wrote: > Hi Rakesh, > > this looks reasonable, but we'll need to also adopt the non-PCI > driver to the new state machine. I can give this a spin. > .. Thanks for handling non-PCI driver part.

Re: mips qemu test failures in -next due to "kthread: Fix use-after-free if kthread fork fails"

On 05/27/17 19:56, Guenter Roeck wrote: Hi, my qemu testis of mips images are failing in -next. Symptom is a hang during boot; see http://kerneltests.org/builders/qemu-mips-next for some examples. I bisected the problem in next-20170526. It points to commit 4d6501dce079c ("kthread: Fix

Re: mips qemu test failures in -next due to "kthread: Fix use-after-free if kthread fork fails"

On 05/27/17 19:56, Guenter Roeck wrote: Hi, my qemu testis of mips images are failing in -next. Symptom is a hang during boot; see http://kerneltests.org/builders/qemu-mips-next for some examples. I bisected the problem in next-20170526. It points to commit 4d6501dce079c ("kthread: Fix

Re: [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

Hi John, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.12-rc2 next-20170526] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

Hi John, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.12-rc2 next-20170526] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] iio: adc: meson-saradc: use NULL instead of 0 for pointer

Fix sparse warning: Using plain integer as NULL pointer Signed-off-by: Paolo Cretaro --- drivers/iio/adc/meson_saradc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iio/adc/meson_saradc.c b/drivers/iio/adc/meson_saradc.c index

[PATCH] iio: adc: meson-saradc: use NULL instead of 0 for pointer

Fix sparse warning: Using plain integer as NULL pointer Signed-off-by: Paolo Cretaro --- drivers/iio/adc/meson_saradc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iio/adc/meson_saradc.c b/drivers/iio/adc/meson_saradc.c index 81cd39a57fe3..fb3f67a9ae1f 100644 ---

Re: [Q] What about PCI mmio access alignment?

Thank you. I have some experiment on my PC. The result is: o I always can get expected value if the unaligned access doesn't across a DWORD boundary, like readw(bar0+1). I suspect that the chipset should read a whole DWORD in behind. This may trigger unexpected behaviour on device. o

Re: [Q] What about PCI mmio access alignment?

Thank you. I have some experiment on my PC. The result is: o I always can get expected value if the unaligned access doesn't across a DWORD boundary, like readw(bar0+1). I suspect that the chipset should read a whole DWORD in behind. This may trigger unexpected behaviour on device. o

cleanup UUID types V5

Hi all, this series, which is a combined effort from Amir, Andy and me introduces new uuid_t and guid_t type names that are less confusing than the existing types, adds new helpers for them and starts switching the fs code over to it. Andy has additional patches on top to convert many of the

cleanup UUID types V5

Hi all, this series, which is a combined effort from Amir, Andy and me introduces new uuid_t and guid_t type names that are less confusing than the existing types, adds new helpers for them and starts switching the fs code over to it. Andy has additional patches on top to convert many of the

[PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h"

This reverts commit ff548773106ec7f8031bc6172e0234bd2a02c19c. The V1 uuid intrepreatation in struct form isn't really useful to the rest of the kernel, and not really compatible to it either, so move it back to AFS instead of polluting the global uuid.h. Signed-off-by: Christoph Hellwig

[PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h"

This reverts commit ff548773106ec7f8031bc6172e0234bd2a02c19c. The V1 uuid intrepreatation in struct form isn't really useful to the rest of the kernel, and not really compatible to it either, so move it back to AFS instead of polluting the global uuid.h. Signed-off-by: Christoph Hellwig ---

Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2

Hi Olof, +Daniel On 26 May 2017 at 18:24, Olof Johansson wrote: > Hi Ulf, > > > On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson wrote: >> Hi Linus, >> >> Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. >> They are based on v4.12-rc2. >>

[PATCH 05/22] uuid: remove uuid_be defintions from the uapi header

We don't use uuid_be and the UUID_BE constants in any uapi headers, so make them private to the kernel. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- include/linux/uuid.h |

Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2

Hi Olof, +Daniel On 26 May 2017 at 18:24, Olof Johansson wrote: > Hi Ulf, > > > On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson wrote: >> Hi Linus, >> >> Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. >> They are based on v4.12-rc2. >> >> Details are as usual found in the

[PATCH 05/22] uuid: remove uuid_be defintions from the uapi header

We don't use uuid_be and the UUID_BE constants in any uapi headers, so make them private to the kernel. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- include/linux/uuid.h | 15 +++ include/uapi/linux/uuid.h | 16

[PATCH 10/22] S390/sysinfo: use uuid_is_null instead of opencoding it

And switch to use uuid_t instead of the old uuid_be type. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- arch/s390/include/asm/sysinfo.h | 4 ++-- arch/s390/kernel/sysinfo.c

[PATCH 10/22] S390/sysinfo: use uuid_is_null instead of opencoding it

And switch to use uuid_t instead of the old uuid_be type. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- arch/s390/include/asm/sysinfo.h | 4 ++-- arch/s390/kernel/sysinfo.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff

Hello dear

Good day dear, i hope this mail meets you well? my name is Jack, from the U.S. I know this may seem inappropriate so i ask for your forgiveness but i wish to get to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person but I am

Hello dear

Good day dear, i hope this mail meets you well? my name is Jack, from the U.S. I know this may seem inappropriate so i ask for your forgiveness but i wish to get to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person but I am

[PATCH 12/22] xfs: use the common helper uuid_is_null()

From: Amir Goldstein Use the common helper uuid_is_null() and remove the xfs specific helper uuid_is_nil(). The common helper does not check for the NULL pointer value as xfs helper did, but xfs code never calls the helper with a pointer that can be NULL. Conform comments

[PATCH 12/22] xfs: use the common helper uuid_is_null()

From: Amir Goldstein Use the common helper uuid_is_null() and remove the xfs specific helper uuid_is_nil(). The common helper does not check for the NULL pointer value as xfs helper did, but xfs code never calls the helper with a pointer that can be NULL. Conform comments and warning strings

[PATCH 17/22] partitions/ldm: switch to use uuid_t

And the uuid helpers. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- block/partitions/ldm.c | 10 +- block/partitions/ldm.h | 6 ++ 2 files changed, 7 insertions(+),

[PATCH 17/22] partitions/ldm: switch to use uuid_t

And the uuid helpers. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- block/partitions/ldm.c | 10 +- block/partitions/ldm.h | 6 ++ 2 files changed, 7 insertions(+), 9 deletions(-) diff --git a/block/partitions/ldm.c

[PATCH 15/22] fs: switch ->s_uuid to uuid_t

For some file systems we still memcpy into it, but in various places this already allows us to use the proper uuid helpers. More to come.. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar  (Changes to

[PATCH 14/22] ima/policy: switch to use uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar Reviewed-by: Andy Shevchenko --- security/integrity/ima/ima_policy.c | 11 +-- 1 file changed, 5

[PATCH 15/22] fs: switch ->s_uuid to uuid_t

For some file systems we still memcpy into it, but in various places this already allows us to use the proper uuid helpers. More to come.. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar  (Changes to IMA/EVM) Reviewed-by: Andy Shevchenko ---

[PATCH 14/22] ima/policy: switch to use uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar Reviewed-by: Andy Shevchenko --- security/integrity/ima/ima_policy.c | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/security/integrity/ima/ima_policy.c

[PATCH 16/22] overlayfs: use uuid_t instead of uuid_be

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- fs/overlayfs/copy_up.c | 2 +- fs/overlayfs/overlayfs.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 16/22] overlayfs: use uuid_t instead of uuid_be

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- fs/overlayfs/copy_up.c | 2 +- fs/overlayfs/overlayfs.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c index

[PATCH 18/22] sysctl: switch to use uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- kernel/sysctl_binary.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sysctl_binary.c

[PATCH 18/22] sysctl: switch to use uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- kernel/sysctl_binary.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sysctl_binary.c b/kernel/sysctl_binary.c index ece4b177052b..1ae520eed53c 100644 ---

[PATCH 20/22] scsi_debug: switch to uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- drivers/scsi/scsi_debug.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/scsi/scsi_debug.c

[PATCH 20/22] scsi_debug: switch to uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- drivers/scsi/scsi_debug.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c index 17249c3650fe..35ee09644cfb 100644

[PATCH 19/22] nvme: switch to uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- drivers/nvme/host/fabrics.c | 8 drivers/nvme/host/fabrics.h | 2 +- drivers/nvme/host/fc.c | 3 +--

[PATCH 22/22] MAINTAINERS: add uuid entry

I'll keep maintaining whatever little changed we need here, with Andy as my designated reviewer. Signed-off-by: Christoph Hellwig --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 053c3bdd1fe5..660c14729205 100644 ---

[PATCH 21/22] tmpfs: generate random sb->s_uuid

From: Amir Goldstein This is used by overlayfs to encode intrasystem unique file handles. Suggested-by: Miklos Szeredi Cc: Hugh Dickins Cc: Andrew Morton Signed-off-by: Amir Goldstein

[PATCH 19/22] nvme: switch to uuid_t

Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Reviewed-by: Andy Shevchenko --- drivers/nvme/host/fabrics.c | 8 drivers/nvme/host/fabrics.h | 2 +- drivers/nvme/host/fc.c | 3 +-- drivers/nvme/target/nvmet.h | 1 + include/linux/nvme-fc.h | 3 +--

[PATCH 22/22] MAINTAINERS: add uuid entry

I'll keep maintaining whatever little changed we need here, with Andy as my designated reviewer. Signed-off-by: Christoph Hellwig --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 053c3bdd1fe5..660c14729205 100644 --- a/MAINTAINERS

[PATCH 21/22] tmpfs: generate random sb->s_uuid

From: Amir Goldstein This is used by overlayfs to encode intrasystem unique file handles. Suggested-by: Miklos Szeredi Cc: Hugh Dickins Cc: Andrew Morton Signed-off-by: Amir Goldstein Signed-off-by: Christoph Hellwig --- mm/shmem.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 13/22] block: remove blk_part_pack_uuid

This helper was only used by IMA of all things, which would get spurious errors if CONFIG_BLOCK is disabled. Just opencode the call there. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar Reviewed-by:

[PATCH 11/22] xfs: remove uuid_getnodeuniq and xfs_uu_t

Opencode uuid_getnodeuniq in the only caller, and directly decode the uuid_t representation instead of using a structure cast for it. Signed-off-by: Christoph Hellwig --- fs/xfs/uuid.c | 25 - fs/xfs/uuid.h | 1 - fs/xfs/xfs_mount.c | 5 - 3

[PATCH 13/22] block: remove blk_part_pack_uuid

This helper was only used by IMA of all things, which would get spurious errors if CONFIG_BLOCK is disabled. Just opencode the call there. Signed-off-by: Christoph Hellwig Reviewed-by: Amir Goldstein Acked-by: Mimi Zohar Reviewed-by: Andy Shevchenko --- include/linux/genhd.h |

[PATCH 11/22] xfs: remove uuid_getnodeuniq and xfs_uu_t

Opencode uuid_getnodeuniq in the only caller, and directly decode the uuid_t representation instead of using a structure cast for it. Signed-off-by: Christoph Hellwig --- fs/xfs/uuid.c | 25 - fs/xfs/uuid.h | 1 - fs/xfs/xfs_mount.c | 5 - 3 files

[PATCH 08/22] uuid: hoist helpers uuid_equal() and uuid_copy() from xfs

These helper are used to compare and copy two uuid_t type objects. Signed-off-by: Amir Goldstein [hch: also provide the respective guid_ versions] Signed-off-by: Christoph Hellwig Reviewed-by: Andy Shevchenko ---

[PATCH 09/22] uuid: hoist uuid_is_null() helper from libnvdimm

Hoist the libnvdimm helper as an inline helper to linux/uuid.h using an auxiliary const variable uuid_null in lib/uuid.c. [hch: also add the guid variant. Both do the same but I'd like to keep casts to a minimum] The common helper uses the new abstract type uuid_t * instead of u8 *.

<    1   2   3   4   5   >