RE: [RESEND PATCH V6 0/6] Add support for privileged mappings

Hi Robin, >Hi Sricharan, > >On 02/12/16 14:55, Sricharan R wrote: >> This series is a resend of the V5 that Mitch sent sometime back [2] >> All the patches are the same and i have just rebased. Not sure why this >> finally did not make it last time. The last patch in the previous >> series does

RE: [RESEND PATCH V6 0/6] Add support for privileged mappings

Hi Robin, >Hi Sricharan, > >On 02/12/16 14:55, Sricharan R wrote: >> This series is a resend of the V5 that Mitch sent sometime back [2] >> All the patches are the same and i have just rebased. Not sure why this >> finally did not make it last time. The last patch in the previous >> series does

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Fri, Dec 02, 2016 at 11:55:58AM +0100, Arnd Bergmann wrote: > I have managed to bisect the link failure to a specific binutils > commit by Alan Modra now: > > d983c8c ("Strip undefined symbols from .symtab") > > went into binutils-2_26 and was reverted in > > a82e3ef ("Revert "Strip

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Fri, Dec 02, 2016 at 11:55:58AM +0100, Arnd Bergmann wrote: > I have managed to bisect the link failure to a specific binutils > commit by Alan Modra now: > > d983c8c ("Strip undefined symbols from .symtab") > > went into binutils-2_26 and was reverted in > > a82e3ef ("Revert "Strip

Re: [Intel-wired-lan] [PATCH v2] e1000e: free IRQ regardless of __E1000_DOWN

On 12/2/2016 7:02 PM, Baicar, Tyler wrote: > Hello Sasha, > > Were you able to reproduce this issue? > > Do you have a patch fixing the close function inconsistencies that you > mentioned which I could try out? > > Thanks, > Tyler > > On 11/21/2016 1:40 PM, Baicar, Tyler wrote: >> On

Re: [Intel-wired-lan] [PATCH v2] e1000e: free IRQ regardless of __E1000_DOWN

On 12/2/2016 7:02 PM, Baicar, Tyler wrote: > Hello Sasha, > > Were you able to reproduce this issue? > > Do you have a patch fixing the close function inconsistencies that you > mentioned which I could try out? > > Thanks, > Tyler > > On 11/21/2016 1:40 PM, Baicar, Tyler wrote: >> On

Re: [PATCH 1/1] infiniband: hw: mlx4: fix improper return value

On Sun, Dec 04, 2016 at 02:45:38PM +0800, Pan Bian wrote: > From: Pan Bian > > If uhw->inlen is non-zero, the value of variable err is 0 if the copy > succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it > will return 0 to the callers. As a result, the callers

Re: [PATCH 1/1] infiniband: hw: mlx4: fix improper return value

On Sun, Dec 04, 2016 at 02:45:38PM +0800, Pan Bian wrote: > From: Pan Bian > > If uhw->inlen is non-zero, the value of variable err is 0 if the copy > succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it > will return 0 to the callers. As a result, the callers cannot detect the >

[PATCH 1/1] infiniband: hw: mlx4: fix improper return value

From: Pan Bian If uhw->inlen is non-zero, the value of variable err is 0 if the copy succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it will return 0 to the callers. As a result, the callers cannot detect the errors. This patch fixes the bug, assign

[PATCH 1/1] infiniband: hw: mlx4: fix improper return value

From: Pan Bian If uhw->inlen is non-zero, the value of variable err is 0 if the copy succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it will return 0 to the callers. As a result, the callers cannot detect the errors. This patch fixes the bug, assign "-ENOMEM" to err before the

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

[PATCH 1/1] net: ethernet: broadcom: fix improper return value

From: Pan Bian Marco BNX2X_ALLOC_AND_SET(arr, lbl, func) calls kmalloc() to allocate memory, and jumps to label "lbl" if the allocation fails. Label "lbl" first cleans memory and then returns variable rc. Before calling the macro, the value of variable rc is 0. Because 0

[PATCH 1/1] net: ethernet: broadcom: fix improper return value

From: Pan Bian Marco BNX2X_ALLOC_AND_SET(arr, lbl, func) calls kmalloc() to allocate memory, and jumps to label "lbl" if the allocation fails. Label "lbl" first cleans memory and then returns variable rc. Before calling the macro, the value of variable rc is 0. Because 0 means no error, the

[PATCH 1/1] xen: set error code on failures

From: Pan Bian The return variable rc is initialized with "-ENOMEM" outside the loop. However, it is reset in the loop, and its value is not negative during the second or after repeat of the loop. If kzalloc() fails then, it will return 0. This patch fixes the bug,

[PATCH 1/1] xen: set error code on failures

From: Pan Bian The return variable rc is initialized with "-ENOMEM" outside the loop. However, it is reset in the loop, and its value is not negative during the second or after repeat of the loop. If kzalloc() fails then, it will return 0. This patch fixes the bug, assigning "-ENOMEM" to rc

Re: [PATCH 1/1] infiniband: hw: ocrdma: fix bad initialization

On Sat, Dec 03, 2016 at 09:10:21PM +0800, Pan Bian wrote: > From: Pan Bian > > In function ocrdma_mbx_create_ah_tbl(), returns the value of status on > errors. However, because status is initialized with 0, 0 will be > returned even if on error paths. This patch initialize

Re: [PATCH 1/1] infiniband: hw: ocrdma: fix bad initialization

On Sat, Dec 03, 2016 at 09:10:21PM +0800, Pan Bian wrote: > From: Pan Bian > > In function ocrdma_mbx_create_ah_tbl(), returns the value of status on > errors. However, because status is initialized with 0, 0 will be > returned even if on error paths. This patch initialize status with >

[PATCH 1/1] mtd: ubi: fix improper return value

From: Pan Bian When __vmalloc() returns a NULL pointer, the region is not checked, and we cannot make sure that only 0xFF bytes are present at offset. Thus, returning 0 seems improper. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189081 Signed-off-by: Pan Bian

[PATCH 1/1] mtd: ubi: fix improper return value

From: Pan Bian When __vmalloc() returns a NULL pointer, the region is not checked, and we cannot make sure that only 0xFF bytes are present at offset. Thus, returning 0 seems improper. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189081 Signed-off-by: Pan Bian ---

[PATCH 1/1] net: ethernet: qlogic: fix improper return value

From: Pan Bian When the call to qlcnic_alloc_mbx_args() fails, returning variable "err" seems improper. With reference to the context, returing variable "config" may be better. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189101 Signed-off-by: Pan Bian

Re: [PATCH 1/1] infiniband: hw: mlx4: fix improper return value

On Sun, Dec 04, 2016 at 01:49:04PM +0800, Pan Bian wrote: > From: Pan Bian > > If uhw->inlen is non-zero, the value of variable err is 0 if the copy > succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it > will return 0 to the callers. As a result, the callers

[PATCH 1/1] net: ethernet: qlogic: fix improper return value

From: Pan Bian When the call to qlcnic_alloc_mbx_args() fails, returning variable "err" seems improper. With reference to the context, returing variable "config" may be better. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189101 Signed-off-by: Pan Bian ---

Re: [PATCH 1/1] infiniband: hw: mlx4: fix improper return value

On Sun, Dec 04, 2016 at 01:49:04PM +0800, Pan Bian wrote: > From: Pan Bian > > If uhw->inlen is non-zero, the value of variable err is 0 if the copy > succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it > will return 0 to the callers. As a result, the callers cannot detect the >

[PATCH 1/1] net: ethernet: qlogic: set error code on failure

From: Pan Bian When calling dma_mapping_error(), the value of return variable rc is 0. And when the call returns an unexpected value, rc is not set to a negative errno. Thus, it will return 0 on the error path, and its callers cannot detect the bug. This patch fixes the bug,

[PATCH 1/1] net: ethernet: qlogic: set error code on failure

From: Pan Bian When calling dma_mapping_error(), the value of return variable rc is 0. And when the call returns an unexpected value, rc is not set to a negative errno. Thus, it will return 0 on the error path, and its callers cannot detect the bug. This patch fixes the bug, assigning "-ENOMEM"

Re: [PATCH v3 07/13] net: ethernet: ti: cpts: clean up event list if event pool is empty

Hi WingMan, [auto build test ERROR on net/master] [also build test ERROR on v4.9-rc7 next-20161202] [cannot apply to net-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v3 07/13] net: ethernet: ti: cpts: clean up event list if event pool is empty

Hi WingMan, [auto build test ERROR on net/master] [also build test ERROR on v4.9-rc7 next-20161202] [cannot apply to net-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 1/1] edac: fix improper return value

From: Pan Bian When the call to zalloc_cpumask_var() fails, returning "false" seems improper. The real value of macro "false" is 0, and 0 means no error. This patch fixes the bug, returning "-ENOMEM". Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189071

[PATCH 1/1] edac: fix improper return value

From: Pan Bian When the call to zalloc_cpumask_var() fails, returning "false" seems improper. The real value of macro "false" is 0, and 0 means no error. This patch fixes the bug, returning "-ENOMEM". Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189071 Signed-off-by: Pan Bian ---

[PATCH 1/1] scsi: snic: fix improper return value

From: Pan Bian When the calls to mempool_create_slab_pool() return unexpected values, the value of return variable ret is 0. 0 means no error. Thus, the caller of fnic_probe() cannot detect the error, and may be misled. This patch fixes the bug, assigning "-ENOMEM" to ret

[PATCH 1/1] scsi: snic: fix improper return value

From: Pan Bian When the calls to mempool_create_slab_pool() return unexpected values, the value of return variable ret is 0. 0 means no error. Thus, the caller of fnic_probe() cannot detect the error, and may be misled. This patch fixes the bug, assigning "-ENOMEM" to ret before calling

[PATCH 1/1] scsi: fnic: fix improper return value

From: Pan Bian When the calls to mempool_create_slab_pool() return unexpected values, the value of return variable err is 0. 0 means no error. Thus, the caller of fnic_probe() cannot detect the error, and may be misled. This patch fixes the bug, assigning "-ENOMEM" to err

[PATCH 1/1] scsi: fnic: fix improper return value

From: Pan Bian When the calls to mempool_create_slab_pool() return unexpected values, the value of return variable err is 0. 0 means no error. Thus, the caller of fnic_probe() cannot detect the error, and may be misled. This patch fixes the bug, assigning "-ENOMEM" to err before calling

[PATCH 1/1] infiniband: hw: mlx4: fix improper return value

From: Pan Bian If uhw->inlen is non-zero, the value of variable err is 0 if the copy succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it will return 0 to the callers. As a result, the callers cannot detect the errors. This patch fixes the bug, assigning

[PATCH 1/1] infiniband: hw: mlx4: fix improper return value

From: Pan Bian If uhw->inlen is non-zero, the value of variable err is 0 if the copy succeeds. Then, if kzalloc() or kmalloc() returns a NULL pointer, it will return 0 to the callers. As a result, the callers cannot detect the errors. This patch fixes the bug, assigning "-ENOMEM" to err before

[PATCH 1/1] atm: fix improper return value

From: Pan Bian It returns variable "error" when ioremap_nocache() returns a NULL pointer. The value of "error" is 0 then, which will mislead the callers to believe that there is no error. This patch fixes the bug, returning "-ENOMEM". Bugzilla:

[PATCH 1/1] atm: fix improper return value

From: Pan Bian It returns variable "error" when ioremap_nocache() returns a NULL pointer. The value of "error" is 0 then, which will mislead the callers to believe that there is no error. This patch fixes the bug, returning "-ENOMEM". Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189021

[PATCH 1/1] media: pci: meye: set error code on failures

From: Pan Bian The value of return variable ret is 0 on some error paths, for example, when pci_resource_start() returns a NULL pointer. 0 means no error in this context, which is contrary to the fact. This patch fixes the bug. Bugzilla:

[PATCH 1/1] media: pci: meye: set error code on failures

From: Pan Bian The value of return variable ret is 0 on some error paths, for example, when pci_resource_start() returns a NULL pointer. 0 means no error in this context, which is contrary to the fact. This patch fixes the bug. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189011

[PATCH 1/1] media: pci: meye: set error code on failures

From: Pan Bian The value of return variable ret is 0 on some error paths, for example, when pci_resource_start() returns a NULL pointer. 0 means no error in this context, which is contrary to the fact. This patch fixes the bug. Bugzilla:

[PATCH 1/2] scsi: be2iscsi: set errno on error path

From: Pan Bian Variable ret is reset in the loop, and its value will be 0 during the second and after repeat of the loop. If pci_alloc_consistent() returns a NULL pointer then, it will leaves with return value 0. 0 means no error, which is contrary to the fact. This patches

[PATCH 1/1] media: pci: meye: set error code on failures

From: Pan Bian The value of return variable ret is 0 on some error paths, for example, when pci_resource_start() returns a NULL pointer. 0 means no error in this context, which is contrary to the fact. This patch fixes the bug. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189011

[PATCH 1/2] scsi: be2iscsi: set errno on error path

From: Pan Bian Variable ret is reset in the loop, and its value will be 0 during the second and after repeat of the loop. If pci_alloc_consistent() returns a NULL pointer then, it will leaves with return value 0. 0 means no error, which is contrary to the fact. This patches fixes the bug,

[PATCH 1/1] scsi: 3w-sas: set errno on failures

From: Pan Bian On some error paths (e.g. pci_iomap() returns a NULL pointer), the value of return variable retval is 0. 0 means no error. This patch fixes the bug, set retval with negative errno on error paths. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189001

[PATCH 1/1] scsi: 3w-sas: set errno on failures

From: Pan Bian On some error paths (e.g. pci_iomap() returns a NULL pointer), the value of return variable retval is 0. 0 means no error. This patch fixes the bug, set retval with negative errno on error paths. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=189001 Signed-off-by: Pan

[PATCH 1/1] memstick: host: fix improper return value

From: Pan Bian When pci_ioremap_bar() returns a NULL pointer, the value of return variable "error" is 0. 0 means no error, which is contrary to the fact. Similarly, the return values are also improper when request_irq() or memstick_add_host() returns unexpected values. This

[PATCH 1/1] memstick: host: fix improper return value

From: Pan Bian When pci_ioremap_bar() returns a NULL pointer, the value of return variable "error" is 0. 0 means no error, which is contrary to the fact. Similarly, the return values are also improper when request_irq() or memstick_add_host() returns unexpected values. This patch fixes the bug,

include/linux/bug.h:37:45: error: bit-field '' width not an integer constant

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: 80cca775cdc4f8555612d2943a2872076b33e0ff net: fec: cache statistics while device is down date: 4 days ago config: m68k-m5272c3_defconfig (attached as

include/linux/bug.h:37:45: error: bit-field '' width not an integer constant

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: 80cca775cdc4f8555612d2943a2872076b33e0ff net: fec: cache statistics while device is down date: 4 days ago config: m68k-m5272c3_defconfig (attached as

[PATCH 1/1] net: irda: set error code on failures

From: Pan Bian When the calls to kzalloc() fail, the value of return variable ret may be 0. 0 means success in this context. This patch fixes the bug, assigning "-ENOMEM" to ret before calling kzalloc(). Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188971

[PATCH 1/1] net: irda: set error code on failures

From: Pan Bian When the calls to kzalloc() fail, the value of return variable ret may be 0. 0 means success in this context. This patch fixes the bug, assigning "-ENOMEM" to ret before calling kzalloc(). Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188971 Signed-off-by: Pan Bian ---

[PATCH 2/2] scsi: be2iscsi: set errno on error path

From: Pan Bian Variable ret is reset in the loop, and its value will be 0 during the second and after repeat of the loop. If pci_alloc_consistent() returns a NULL pointer then, it will leaves with return value 0. 0 means no error, which is contrary to the fact. This patches

[PATCH 2/2] scsi: be2iscsi: set errno on error path

From: Pan Bian Variable ret is reset in the loop, and its value will be 0 during the second and after repeat of the loop. If pci_alloc_consistent() returns a NULL pointer then, it will leaves with return value 0. 0 means no error, which is contrary to the fact. This patches fixes the bug,

[PATCH 1/1] isdn: hisax: set error code on failure

From: Pan Bian In function hfc4s8s_probe(), the value of return variable err should be negative on failures. However, when the call to request_region() returns NULL, the value of err is 0. This patch fixes the bug, assiging "-ENOMEM" to err on the path that request_region()

[PATCH 1/1] isdn: hisax: set error code on failure

From: Pan Bian In function hfc4s8s_probe(), the value of return variable err should be negative on failures. However, when the call to request_region() returns NULL, the value of err is 0. This patch fixes the bug, assiging "-ENOMEM" to err on the path that request_region() fails. Bugzilla:

[PATCH 1/1] input: usbhid: fix improper check

From: Pan Bian Function hid_post_reset() returns 0 on success, or 1 on failures. However, in function hid_reset_resume(), uses "status >= 0" to check the return value of hid_post_reset(). Obviously, the condition will always be satisfied. This patch fixes the bug, uses

[PATCH 1/1] input: usbhid: fix improper check

From: Pan Bian Function hid_post_reset() returns 0 on success, or 1 on failures. However, in function hid_reset_resume(), uses "status >= 0" to check the return value of hid_post_reset(). Obviously, the condition will always be satisfied. This patch fixes the bug, uses "status == 0" to check the

Re: [PATCH 1/1] net: dcb: set error code on failures

From: Pan Bian Date: Sat, 3 Dec 2016 21:49:08 +0800 > From: Pan Bian > > In function dcbnl_cee_fill(), returns the value of variable err on > errors. However, on some error paths (e.g. nla put fails), its value may > be 0. It may be better to

Re: [PATCH 1/1] net: dcb: set error code on failures

From: Pan Bian Date: Sat, 3 Dec 2016 21:49:08 +0800 > From: Pan Bian > > In function dcbnl_cee_fill(), returns the value of variable err on > errors. However, on some error paths (e.g. nla put fails), its value may > be 0. It may be better to explicitly set a negative errno to variable > err

[PATCH 1/1] btrfs: fix improper return value

In function btrfs_uuid_tree_iterate(), errno is assigned to variable ret on errors. However, it directly returns 0. It may be better to return ret. This patch also removes the warning, because the caller already prints a warning. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188731

[PATCH 1/1] btrfs: fix improper return value

In function btrfs_uuid_tree_iterate(), errno is assigned to variable ret on errors. However, it directly returns 0. It may be better to return ret. This patch also removes the warning, because the caller already prints a warning. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=188731

Re: [PATCH net-next] liquidio: 'imply' ptp instead of 'select'

From: Arnd Bergmann Date: Sat, 3 Dec 2016 00:04:32 +0100 > ptp now depends on the optional POSIX_TIMERS setting and fails to build > if we select it without that: > > warning: (LIQUIDIO_VF && TI_CPTS) selects PTP_1588_CLOCK which has unmet > direct dependencies (NET &&

Re: [PATCH net-next] liquidio: 'imply' ptp instead of 'select'

From: Arnd Bergmann Date: Sat, 3 Dec 2016 00:04:32 +0100 > ptp now depends on the optional POSIX_TIMERS setting and fails to build > if we select it without that: > > warning: (LIQUIDIO_VF && TI_CPTS) selects PTP_1588_CLOCK which has unmet > direct dependencies (NET && POSIX_TIMERS) >

Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available [ver #3]

On Wed, Nov 23, 2016 at 12:55:51AM +, David Howells wrote: > + * vfs_xgetattr - Get the enhanced basic attributes of a file > + * @path: The file of interest > + * @stat: Where to return the statistics > + * > + * Ask the filesystem for a file's attributes. The caller must have preset > + *

Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available [ver #3]

On Wed, Nov 23, 2016 at 12:55:51AM +, David Howells wrote: > + * vfs_xgetattr - Get the enhanced basic attributes of a file > + * @path: The file of interest > + * @stat: Where to return the statistics > + * > + * Ask the filesystem for a file's attributes. The caller must have preset > + *

Re: [PATCH] dt-binding: soc: qcom: smd: Add label property

On Wed, Oct 26, 2016 at 05:08:20PM -0500, Rob Herring wrote: > On Wed, Oct 19, 2016 at 07:38:10PM -0700, Bjorn Andersson wrote: > > The label property can be used to specify a name of the edge, for > > consistent naming purposes. > > > > Signed-off-by: Bjorn Andersson

Re: [PATCH] dt-binding: soc: qcom: smd: Add label property

On Wed, Oct 26, 2016 at 05:08:20PM -0500, Rob Herring wrote: > On Wed, Oct 19, 2016 at 07:38:10PM -0700, Bjorn Andersson wrote: > > The label property can be used to specify a name of the edge, for > > consistent naming purposes. > > > > Signed-off-by: Bjorn Andersson > > --- > >

[PATCH 1/1] net: caif: remove ineffective check

The check of the return value of sock_register() is ineffective. "if(!err)" seems to be a typo. It is better to propagate the error code to the callers of caif_sktinit_module(). This patch removes the check statment and directly returns the result of sock_register(). Bugzilla:

[PATCH 1/1] net: caif: remove ineffective check

The check of the return value of sock_register() is ineffective. "if(!err)" seems to be a typo. It is better to propagate the error code to the callers of caif_sktinit_module(). This patch removes the check statment and directly returns the result of sock_register(). Bugzilla:

cc1: error: '-march=r3900' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 8 weeks ago config:

cc1: error: '-march=r3900' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0cb65c83304a341b9d09678448d7c8b550689531 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 8 weeks ago config:

Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available [ver #3]

On Wed, Nov 23, 2016 at 12:55:51AM +, David Howells wrote: > -int vfs_getattr_nosec(struct path *path, struct kstat *stat) > +int vfs_xgetattr_nosec(struct path *path, struct kstat *stat) const struct path *, please. Especially since we feed >f_path to it. And yes, I realize that the same

Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available [ver #3]

On Wed, Nov 23, 2016 at 12:55:51AM +, David Howells wrote: > -int vfs_getattr_nosec(struct path *path, struct kstat *stat) > +int vfs_xgetattr_nosec(struct path *path, struct kstat *stat) const struct path *, please. Especially since we feed >f_path to it. And yes, I realize that the same

Re: [PATCH V4 2/2] pinctrl: tegra: Add driver to configure voltage and power of io pads

Hi Laxman, [auto build test ERROR on tegra/for-next] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V4 2/2] pinctrl: tegra: Add driver to configure voltage and power of io pads

Hi Laxman, [auto build test ERROR on tegra/for-next] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

cc1: error: '-march=r3000' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 8 weeks ago config:

cc1: error: '-march=r3000' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 8 weeks ago config:

[PATCH] zram: restrict add/remove attributes to root only

Only root must be able to create a new zram device, therefore hot_add attribute must have S_IRUSR mode, not S_IRUGO. Otherwise, anyone can create a new zram device (device initialization with the disksize attr requires root permission). Fixes: 6566d1a32bf72 ("zram: add dynamic device add/remove

[PATCH] zram: restrict add/remove attributes to root only

Only root must be able to create a new zram device, therefore hot_add attribute must have S_IRUSR mode, not S_IRUGO. Otherwise, anyone can create a new zram device (device initialization with the disksize attr requires root permission). Fixes: 6566d1a32bf72 ("zram: add dynamic device add/remove

Urgent Pls

Dear, I'm Dr. Andrea Thompson, I'm seeking for investment opportunities around the globe and wonder if you can be of assistance. Basically, all I need from you is sincerity, authenticity, integrity protection, virtue, accountability and honor which brings trust in business. As you already

Urgent Pls

Dear, I'm Dr. Andrea Thompson, I'm seeking for investment opportunities around the globe and wonder if you can be of assistance. Basically, all I need from you is sincerity, authenticity, integrity protection, virtue, accountability and honor which brings trust in business. As you already

Re: [PATCH v5 1/1] crypto: add virtio-crypto driver

Hi Gonglei, [auto build test ERROR on cryptodev/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5 1/1] crypto: add virtio-crypto driver

Hi Gonglei, [auto build test ERROR on cryptodev/master] [also build test ERROR on v4.9-rc7 next-20161202] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 04/19] staging: iio: isl29028: add power management support

This patch adds power management support to the isl29028 driver. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 59 1 file changed, 59 insertions(+) diff --git a/drivers/staging/iio/light/isl29028.c

[PATCH 04/19] staging: iio: isl29028: add power management support

This patch adds power management support to the isl29028 driver. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 59 1 file changed, 59 insertions(+) diff --git a/drivers/staging/iio/light/isl29028.c

[PATCH 11/19] staging: iio: isl29028: made column alignment in isl29028_channels consistent

The three info_mask_separate members OR several BIT(xxx) fields together. This patch changes the column alignment of these fields to be aligned at the same column to improve the overall code readability. It also moves the { for the next channel to the next line to improve code readability.

[PATCH 01/19] staging: iio: isl29028: remove nested if statements

There are two callers to the function isl29028_set_als_ir_mode() and both instances use a nested if statement to only change the chip state if it is not in the proper mode. This patch moves this check into the isl29028_set_als_ir_mode() function to remove the nested if statements. Signed-off-by:

[PATCH 11/19] staging: iio: isl29028: made column alignment in isl29028_channels consistent

The three info_mask_separate members OR several BIT(xxx) fields together. This patch changes the column alignment of these fields to be aligned at the same column to improve the overall code readability. It also moves the { for the next channel to the next line to improve code readability.

[PATCH 01/19] staging: iio: isl29028: remove nested if statements

There are two callers to the function isl29028_set_als_ir_mode() and both instances use a nested if statement to only change the chip state if it is not in the proper mode. This patch moves this check into the isl29028_set_als_ir_mode() function to remove the nested if statements. Signed-off-by:

[PATCH 12/19] staging: iio: isl29028: fix comparison between signed and unsigned integers

Fixed warning found by make W=2 to reduce the amount of build noise: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 09/19] staging: iio: isl29028: change newlines to improve readability

Add and remove newlines to improve code readability in preparation for moving the driver out of staging. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 31 ++- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git

[PATCH 12/19] staging: iio: isl29028: fix comparison between signed and unsigned integers

Fixed warning found by make W=2 to reduce the amount of build noise: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 09/19] staging: iio: isl29028: change newlines to improve readability

Add and remove newlines to improve code readability in preparation for moving the driver out of staging. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 31 ++- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git

[PATCH 10/19] staging: iio: isl29028: remove unused define ISL29028_DEV_ATTR

The #define ISL29028_DEV_ATTR was not used so this patch removes the unnecessary code. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/iio/light/isl29028.c

[PATCH 07/19] staging: iio: isl29028: fix alignment of function arguments

Two separate calls to regmap_update_bits() in isl29028_set_als_scale() and isl29028_set_als_ir_mode() did not have their function arguments on the next line aligned correctly to the open parenthesis. This patch corrects the alignment. Signed-off-by: Brian Masney ---

[PATCH 05/19] staging: iio: isl29028: made alignment of #defines consistent

The alignment of the #defines at the top of the file is not consistent. This changes all of the defines to use consistent alignment to improve the code readability. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 42

[PATCH 06/19] staging: iio: isl29028: made alignment of variables in struct isl29028_chip consistent

The alignment of the variables in the struct isl29028_chip is not consistent. This changes all of the variables to use consistent alignment to improve the code readability. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 10 +- 1 file

[PATCH 08/19] staging: iio: isl29028: combine isl29028_proxim_get() and isl29028_read_proxim()

isl29028_proxim_get() checks to see if the promixity needs to be enabled on the chip and then calls isl29028_read_proxim(). There are no other callers of isl29028_read_proxim(). The naming between these two functions can be confusing so this patch combines the two to avoid the confusion.

[PATCH 10/19] staging: iio: isl29028: remove unused define ISL29028_DEV_ATTR

The #define ISL29028_DEV_ATTR was not used so this patch removes the unnecessary code. Signed-off-by: Brian Masney --- drivers/staging/iio/light/isl29028.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/iio/light/isl29028.c b/drivers/staging/iio/light/isl29028.c index

  1   2   3   4   5   6   >