[PATCH] phy: qcom-qmp: Fix failure path in phy_init functions

Fixing the clk enable failure path in qcom_qmp_phy_init() and cleanup the reset control deassertion failure path in qcom_qmp_phy_com_init(). Fixes: e78f3d15e115 ("phy: qcom-qmp: new qmp phy driver for qcom-chipsets") Cc: Kishon Vijay Abraham I Signed-off-by: Vivek Gautam

[PATCH] phy: qcom-qmp: Fix failure path in phy_init functions

Fixing the clk enable failure path in qcom_qmp_phy_init() and cleanup the reset control deassertion failure path in qcom_qmp_phy_com_init(). Fixes: e78f3d15e115 ("phy: qcom-qmp: new qmp phy driver for qcom-chipsets") Cc: Kishon Vijay Abraham I Signed-off-by: Vivek Gautam ---

Re: [PATCH 0/2] ALSA: add const to snd_ratnum structures

On Mon, 19 Jun 2017 20:41:52 +0200, Bhumika Goyal wrote: > > Declare snd_ratnum structures as const as their reference is only > stored in the rate field of a snd_pcm_hw_constraint_ratnums structure. > This field is of type const, so snd_ratnum structures can be made const. > > Bhumika Goyal

Re: [PATCH 0/2] ALSA: add const to snd_ratnum structures

On Mon, 19 Jun 2017 20:41:52 +0200, Bhumika Goyal wrote: > > Declare snd_ratnum structures as const as their reference is only > stored in the rate field of a snd_pcm_hw_constraint_ratnums structure. > This field is of type const, so snd_ratnum structures can be made const. > > Bhumika Goyal

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

On Mon, Jun 19, 2017 at 5:46 PM, Dave Chinner wrote: > On Mon, Jun 19, 2017 at 08:22:10AM -0700, Andy Lutomirski wrote: >> On Mon, Jun 19, 2017 at 6:21 AM, Dave Chinner wrote: >> > On Sat, Jun 17, 2017 at 10:05:45PM -0700, Andy Lutomirski wrote: >> >> On

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

On Mon, Jun 19, 2017 at 5:46 PM, Dave Chinner wrote: > On Mon, Jun 19, 2017 at 08:22:10AM -0700, Andy Lutomirski wrote: >> On Mon, Jun 19, 2017 at 6:21 AM, Dave Chinner wrote: >> > On Sat, Jun 17, 2017 at 10:05:45PM -0700, Andy Lutomirski wrote: >> >> On Sat, Jun 17, 2017 at 8:15 PM, Dan

[patch v3 1/3] tty: add function to convert device name to number

The function converts strings like ttyS0 and ttyUSB0 to dev_t like (4, 64) and (188, 0). It does this by scanning tty_drivers list for corresponding device name and index. If the driver is not registered, this function returns -ENODEV. It also acquires tty_mutex. Signed-off-by: Okash Khawaja

[patch v3 3/3] staging: speakup: make ttyio synths use device name

This patch introduces new module parameter, dev, which takes a string representing the device that the external synth is connected to, e.g. ttyS0, ttyUSB0 etc. This is then used to communicate with the synth. That way, speakup can support more than ttyS*. As of this patch, it only supports ttyS*,

[patch v3 0/3] staging: speakup: support more than ttyS*

Hi, I have updated the patches based on feedback. For patch 1, In favour of consistency, I've updated the code which extracts trailing digits so that it is like similar code in tty_find_polling_driver. Also fixed checkpatch warnings. Here's summary of the patches Patch 1 adds functionality to

[patch v3 2/3] staging: speakup: check and convert dev name or ser to dev_t

This patch adds functionality to validate and convert either a device name or 'ser' memmber of synth into dev_t. Subsequent patch in this set will call it to convert user-specified device into device number. For device name, this patch does some basic sanity checks on the string passed in. It

[patch v3 1/3] tty: add function to convert device name to number

The function converts strings like ttyS0 and ttyUSB0 to dev_t like (4, 64) and (188, 0). It does this by scanning tty_drivers list for corresponding device name and index. If the driver is not registered, this function returns -ENODEV. It also acquires tty_mutex. Signed-off-by: Okash Khawaja

[patch v3 3/3] staging: speakup: make ttyio synths use device name

This patch introduces new module parameter, dev, which takes a string representing the device that the external synth is connected to, e.g. ttyS0, ttyUSB0 etc. This is then used to communicate with the synth. That way, speakup can support more than ttyS*. As of this patch, it only supports ttyS*,

[patch v3 0/3] staging: speakup: support more than ttyS*

Hi, I have updated the patches based on feedback. For patch 1, In favour of consistency, I've updated the code which extracts trailing digits so that it is like similar code in tty_find_polling_driver. Also fixed checkpatch warnings. Here's summary of the patches Patch 1 adds functionality to

[patch v3 2/3] staging: speakup: check and convert dev name or ser to dev_t

This patch adds functionality to validate and convert either a device name or 'ser' memmber of synth into dev_t. Subsequent patch in this set will call it to convert user-specified device into device number. For device name, this patch does some basic sanity checks on the string passed in. It

[PATCH] PCI: xilinx: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 195 600 0 795 31b

[PATCH] PCI: xilinx: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 195 600 0 795 31b

[PATCH] drm: dw-hdmi-i2s: add missing company name on Copyright

From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Signed-off-by: Kuninori Morimoto --- drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[PATCH] drm: dw-hdmi-i2s: add missing company name on Copyright

From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Signed-off-by: Kuninori Morimoto --- drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c

[PATCH v2] serial: 8250: 8250_omap: Fix race b/w dma completion and RX timeout

DMA RX completion handler for UART is called from a tasklet and hence may be delayed depending on the system load. In meanwhile, there may be RX timeout interrupt which can get serviced first before DMA RX completion handler is executed for the completed transfer. omap_8250_rx_dma_flush() which is

[PATCH v2] serial: 8250: 8250_omap: Fix race b/w dma completion and RX timeout

DMA RX completion handler for UART is called from a tasklet and hence may be delayed depending on the system load. In meanwhile, there may be RX timeout interrupt which can get serviced first before DMA RX completion handler is executed for the completed transfer. omap_8250_rx_dma_flush() which is

Re: [PATCH v4] Introduce v3 namespaced file capabilities

On Tue, Jun 20, 2017 at 12:34 AM, Eric W. Biederman wrote: > "Serge E. Hallyn" writes: > >> Quoting Stefan Berger (stef...@linux.vnet.ibm.com): >>> On 06/14/2017 11:05 PM, Serge E. Hallyn wrote: >>> >On Wed, Jun 14, 2017 at 08:27:40AM -0400, Stefan Berger

Re: [PATCH v4] Introduce v3 namespaced file capabilities

On Tue, Jun 20, 2017 at 12:34 AM, Eric W. Biederman wrote: > "Serge E. Hallyn" writes: > >> Quoting Stefan Berger (stef...@linux.vnet.ibm.com): >>> On 06/14/2017 11:05 PM, Serge E. Hallyn wrote: >>> >On Wed, Jun 14, 2017 at 08:27:40AM -0400, Stefan Berger wrote: >>> >>On 06/13/2017 07:55 PM,

Re: linux-next: build failure after merge of the kspp tree

On 06/19/2017 10:39 PM, Kees Cook wrote: > On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell > wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function

Re: linux-next: build failure after merge of the kspp tree

On 06/19/2017 10:39 PM, Kees Cook wrote: > On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell > wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function 'aa_path_link': >>

Re: linux-next: build failure after merge of the kspp tree

On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error:

Re: linux-next: build failure after merge of the kspp tree

On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of

Re: linux-next: build failure after merge of the kspp tree

On 06/19/2017 09:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of field in

Re: linux-next: build failure after merge of the kspp tree

On 06/19/2017 09:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of field in

Re: [PATCH 3.10 060/268] xen/gntdev: Use VM_MIXEDMAP instead of VM_IO to avoid NUMA balancing

On Mon, Jun 19, 2017 at 07:57:27PM -0700, Hugh Dickins wrote: > On Mon, 19 Jun 2017, Willy Tarreau wrote: > > > From: Boris Ostrovsky > > > > commit 30faaafdfa0c754c91bac60f216c9f34a2bfdf7e upstream. > > > > Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be

Re: [PATCH 3.10 060/268] xen/gntdev: Use VM_MIXEDMAP instead of VM_IO to avoid NUMA balancing

On Mon, Jun 19, 2017 at 07:57:27PM -0700, Hugh Dickins wrote: > On Mon, 19 Jun 2017, Willy Tarreau wrote: > > > From: Boris Ostrovsky > > > > commit 30faaafdfa0c754c91bac60f216c9f34a2bfdf7e upstream. > > > > Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be subject to > > NUMA

[PATCH] watchdog: cadence_wdt: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 1962 612 42578 a12

[PATCH] watchdog: cadence_wdt: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 1962 612 42578 a12

[PATCH] staging: rtl8723bs: hal: Use (true/false) in assignment to bool

This patch assigns (true/false) to boolean EDCCA_State instead of (1/0). And, there is no need of comparing EDCCA_State explicitly with constant 1. Signed-off-by: simran singhal --- drivers/staging/rtl8723bs/hal/odm_DIG.c | 8 1 file changed, 4 insertions(+),

[PATCH] staging: rtl8723bs: hal: Use (true/false) in assignment to bool

This patch assigns (true/false) to boolean EDCCA_State instead of (1/0). And, there is no need of comparing EDCCA_State explicitly with constant 1. Signed-off-by: simran singhal --- drivers/staging/rtl8723bs/hal/odm_DIG.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

[add linux-xfs to the fray] On Fri, Jun 16, 2017 at 06:15:35PM -0700, Dan Williams wrote: > To date, the full promise of byte-addressable access to persistent > memory has only been half realized via the filesystem-dax interface. The > current filesystem-dax mechanism allows an application to

Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem

[add linux-xfs to the fray] On Fri, Jun 16, 2017 at 06:15:35PM -0700, Dan Williams wrote: > To date, the full promise of byte-addressable access to persistent > memory has only been half realized via the filesystem-dax interface. The > current filesystem-dax mechanism allows an application to

[PATCH 10/11] Fix ERROR: else should follow close brace '}'

From: Jhih-Ming Hunag Fixied "ERROR: else should follow close brace '}'". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 10/11] Fix ERROR: else should follow close brace '}'

From: Jhih-Ming Hunag Fixied "ERROR: else should follow close brace '}'". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c index

[PATCH 11/11] Fix ERROR: "foo* bar" should be "foo *bar"

From: Jhih-Ming Hunag Fixed 'ERROR: "foo* bar" should be "foo *bar"'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 11/11] Fix ERROR: "foo* bar" should be "foo *bar"

From: Jhih-Ming Hunag Fixed 'ERROR: "foo* bar" should be "foo *bar"'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c index

[PATCH 07/11] Fix ERROR: open brace '{' following function declarations go on the next line

From: Jhih-Ming Hunag Fixed "ERROR: open brace '{' following function declarations go on the next line". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

[PATCH 08/11] Fix ERROR: space prohibited before open square bracket '['

From: Jhih-Ming Hunag Fixied "ERROR: space prohibited before open square bracket '['". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 07/11] Fix ERROR: open brace '{' following function declarations go on the next line

From: Jhih-Ming Hunag Fixed "ERROR: open brace '{' following function declarations go on the next line". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 08/11] Fix ERROR: space prohibited before open square bracket '['

From: Jhih-Ming Hunag Fixied "ERROR: space prohibited before open square bracket '['". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c

[PATCH 09/11] Fix ERROR: space prohibited before that ','

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited before that ','". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 09/11] Fix ERROR: space prohibited before that ','

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited before that ','". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c index

[PATCH 06/11] Fix ERROR: space prohibited before that close parenthesis ')'

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited before that close parenthesis ')'". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 30 +++--- 1 file changed, 15 insertions(+), 15 deletions(-) diff

[PATCH 06/11] Fix ERROR: space prohibited before that close parenthesis ')'

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited before that close parenthesis ')'". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 30 +++--- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 05/11] Fix ERROR: space prohibited after that open parenthesis '('

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited after that open parenthesis '('". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH 05/11] Fix ERROR: space prohibited after that open parenthesis '('

From: Jhih-Ming Hunag Fixed "ERROR: space prohibited after that open parenthesis '('". Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 03/11] Fix ERROR: space required before the open brace

From: Jhih-Ming Hunag Fixed 'ERROR: space required before the open brace'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 04/11] Fix ERROR: that open brace { should be on the previous line

From: Jhih-Ming Hunag Fixed 'ERROR: that open brace { should be on the previous line'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH 03/11] Fix ERROR: space required before the open brace

From: Jhih-Ming Hunag Fixed 'ERROR: space required before the open brace'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c index

[PATCH 04/11] Fix ERROR: that open brace { should be on the previous line

From: Jhih-Ming Hunag Fixed 'ERROR: that open brace { should be on the previous line'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 02/11] Fix ERROR: spaces required around that

From: Jhih-Ming Hunag Fixed 'ERROR: spaces required around that' Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c

[PATCH 02/11] Fix ERROR: spaces required around that

From: Jhih-Ming Hunag Fixed 'ERROR: spaces required around that' Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/staging/ccree/ssi_aead.c index

[PATCH 01/11] Fix coding style of driver/staging/ccree/ssi_aead.c ERROR: space required after that

From: Jhih-Ming Hunag In this series patches, I fix all of the coding style error in driver/staging/ccree/ssi_aead.c from 54 errors to 0 error. The first patch fixed 'ERROR: space required after that'. Signed-off-by: Jhih-Ming Hunag ---

[PATCH 01/11] Fix coding style of driver/staging/ccree/ssi_aead.c ERROR: space required after that

From: Jhih-Ming Hunag In this series patches, I fix all of the coding style error in driver/staging/ccree/ssi_aead.c from 54 errors to 0 error. The first patch fixed 'ERROR: space required after that'. Signed-off-by: Jhih-Ming Hunag --- drivers/staging/ccree/ssi_aead.c | 22

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/ipc.h between commit: 1a12979f61e4 ("randstruct: Mark various structs for randomization") from the kspp tree and commit: 893106d6be17 ("ipc: merge ipc_rcu and kern_ipc_perm") from the

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/ipc.h between commit: 1a12979f61e4 ("randstruct: Mark various structs for randomization") from the kspp tree and commit: 893106d6be17 ("ipc: merge ipc_rcu and kern_ipc_perm") from the

[git pull] ufs fixes

More UFS fixes, unfortunately including build regression fix for the 64bit s_dsize commit. Fixed in this pile: * trivial bug in signedness of 32bit timestamps on ufs1 * ESTALE instead of ufs_error() when doing open-by-fhandle on something deleted * build regression

[git pull] ufs fixes

More UFS fixes, unfortunately including build regression fix for the 64bit s_dsize commit. Fixed in this pile: * trivial bug in signedness of 32bit timestamps on ufs1 * ESTALE instead of ufs_error() when doing open-by-fhandle on something deleted * build regression

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/sem.h between commit: 1a12979f61e4 ("randstruct: Mark various structs for randomization") from the kspp tree and commit: 337e62a32a54 ("ipc/sem.c: remove sem_base, embed struct sem") from the

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/sem.h between commit: 1a12979f61e4 ("randstruct: Mark various structs for randomization") from the kspp tree and commit: 337e62a32a54 ("ipc/sem.c: remove sem_base, embed struct sem") from the

[PATCH] drm: armada: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 8836 744 09580256c

[PATCH] drm: armada: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 8836 744 09580256c

Re: [PATCH 3.10 162/268] bcma: use (get|put)_device when probing/removing device driver

Willy Tarreau writes: > From: Rafał Miłecki > > commit a971df0b9d04674e325346c17de9a895425ca5e1 upstream. > > This allows tracking device state and e.g. makes devm work as expected. > > Signed-off-by: Rafał Miłecki > Signed-off-by: Kalle

Re: [PATCH 3.10 162/268] bcma: use (get|put)_device when probing/removing device driver

Willy Tarreau writes: > From: Rafał Miłecki > > commit a971df0b9d04674e325346c17de9a895425ca5e1 upstream. > > This allows tracking device state and e.g. makes devm work as expected. > > Signed-off-by: Rafał Miłecki > Signed-off-by: Kalle Valo > Signed-off-by: Willy Tarreau UTF-8

Re: [RFC v2 00/12] powerpc: Memory Protection Keys

On Fri, 2017-06-16 at 20:52 -0700, Ram Pai wrote: > Memory protection keys enable applications to protect its > address space from inadvertent access or corruption from > itself. I presume by itself you mean protection between threads? > > The overall idea: > > A process allocates a key

Re: [RFC v2 00/12] powerpc: Memory Protection Keys

On Fri, 2017-06-16 at 20:52 -0700, Ram Pai wrote: > Memory protection keys enable applications to protect its > address space from inadvertent access or corruption from > itself. I presume by itself you mean protection between threads? > > The overall idea: > > A process allocates a key

[PATCH] ARM: dts: am437x-gp-evm: Add support for buzzer

Add support for onboard gpio buzzer. It works using the gpio-beeper driver. Pinmux entries for GPIO controlling the buzzer are also added. Signed-off-by: Faiz Abbas --- arch/arm/boot/dts/am437x-gp-evm.dts | 14 ++ 1 file changed, 14 insertions(+) diff --git

[PATCH] ARM: dts: am437x-gp-evm: Add support for buzzer

Add support for onboard gpio buzzer. It works using the gpio-beeper driver. Pinmux entries for GPIO controlling the buzzer are also added. Signed-off-by: Faiz Abbas --- arch/arm/boot/dts/am437x-gp-evm.dts | 14 ++ 1 file changed, 14 insertions(+) diff --git

[PATCH V2 1/2] hwmon: (ibmpowernv) introduce a legacy_compatibles array

From: Cédric Le Goater Today, the type of a PowerNV sensor system is determined with the "compatible" property for legacy Firmwares and with the "sensor-type" for newer ones. The same array of strings is used for both to do the matching and this raises some issue to introduce new

[PATCH V2 2/2] hwmon: (ibmpowernv) Add current(A) sensor

This patch exports current(A) sensors in inband sensors copied to main memory by OCC. Signed-off-by: Shilpasri G Bhat --- Changes from V1: - Rebased on top of Cedric's patch to remove legay-compatible type for the current(A) sensor. drivers/hwmon/ibmpowernv.c

[PATCH V2 1/2] hwmon: (ibmpowernv) introduce a legacy_compatibles array

From: Cédric Le Goater Today, the type of a PowerNV sensor system is determined with the "compatible" property for legacy Firmwares and with the "sensor-type" for newer ones. The same array of strings is used for both to do the matching and this raises some issue to introduce new sensor types.

[PATCH V2 2/2] hwmon: (ibmpowernv) Add current(A) sensor

This patch exports current(A) sensors in inband sensors copied to main memory by OCC. Signed-off-by: Shilpasri G Bhat --- Changes from V1: - Rebased on top of Cedric's patch to remove legay-compatible type for the current(A) sensor. drivers/hwmon/ibmpowernv.c | 4 +++- 1 file changed, 3

[PATCH V2 0/2] hwmon: (ibmpowernv) Add support for current(A) sensors

The first patch from Cedric in the patchset cleans up the driver to provide a neater way to define new sensor types. The second patch adds current sensor. Cédric Le Goater (1): hwmon: (ibmpowernv) introduce a legacy_compatibles array Shilpasri G Bhat (1): hwmon: (ibmpowernv) Add current(A)

[PATCH V2 0/2] hwmon: (ibmpowernv) Add support for current(A) sensors

The first patch from Cedric in the patchset cleans up the driver to provide a neater way to define new sensor types. The second patch adds current sensor. Cédric Le Goater (1): hwmon: (ibmpowernv) introduce a legacy_compatibles array Shilpasri G Bhat (1): hwmon: (ibmpowernv) Add current(A)

[PATCH] drm: sti: sti_hqvdp: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 15845 640 0 164854065

[PATCH] drm: sti: sti_hqvdp: make of_device_ids const.

of_device_ids are not supposed to change at runtime. All functions working with of_device_ids provided by work with const of_device_ids. So mark the non-const structs as const. File size before: textdata bss dec hex filename 15845 640 0 164854065

Re: [PATCH v2 3/9] vfio: New external user group/file match

Hi Alex, [auto build test ERROR on vfio/next] [also build test ERROR on v4.12-rc6 next-20170619] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Alex-Williamson/vfio-Fix-release-ordering-races

Re: [PATCH v2 3/9] vfio: New external user group/file match

Hi Alex, [auto build test ERROR on vfio/next] [also build test ERROR on v4.12-rc6 next-20170619] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Alex-Williamson/vfio-Fix-release-ordering-races

Re: [PATCH v5 3/6] kernel/reboot.c: export pm_power_off_prepare

On 19.06.2017 13:35, Leonard Crestez wrote: On Mon, 2017-06-19 at 07:02 +0200, Oleksij Rempel wrote: Export pm_power_off_prepare. It is needed to implement power off on Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). Signed-off-by: Oleksij Rempel

Re: [PATCH v5 3/6] kernel/reboot.c: export pm_power_off_prepare

On 19.06.2017 13:35, Leonard Crestez wrote: On Mon, 2017-06-19 at 07:02 +0200, Oleksij Rempel wrote: Export pm_power_off_prepare. It is needed to implement power off on Freescale/NXP iMX6 based boards with external power management integrated circuit (PMIC). Signed-off-by: Oleksij Rempel

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: security/apparmor/file.c: In function 'aa_path_link': security/apparmor/file.c:475:23: error: positional initialization of field in 'struct' declared with 'designated_init' attribute

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: security/apparmor/file.c: In function 'aa_path_link': security/apparmor/file.c:475:23: error: positional initialization of field in 'struct' declared with 'designated_init' attribute

Re: [PATCH v5 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

Hi Leonard, On 19.06.2017 13:35, Leonard Crestez wrote: On Mon, 2017-06-19 at 07:02 +0200, Oleksij Rempel wrote: One of the Freescale recommended sequences for power off with external PMIC is the following: ... 3. SoC is programming PMIC for power off when standby is asserted. 4. In CCM STOP

[PATCH] drm: sti: sti_hqvdp: Fix compilation warning.

Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:- drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’: drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]

Re: [PATCH v5 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

Hi Leonard, On 19.06.2017 13:35, Leonard Crestez wrote: On Mon, 2017-06-19 at 07:02 +0200, Oleksij Rempel wrote: One of the Freescale recommended sequences for power off with external PMIC is the following: ... 3. SoC is programming PMIC for power off when standby is asserted. 4. In CCM STOP

[PATCH] drm: sti: sti_hqvdp: Fix compilation warning.

Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:- drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’: drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument of type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]

Re: [PATCH v2] drm/exynos/dsi: Remove error handling for bridge_node DT parsing

Hello Tobias, Sorry for late reply. On 06/14/2017 09:30 PM, Tobias Jakobi wrote: Hello Hoegeun, my last question (does this regress the case "node required, but absent") still stands. Hoegeun Kwon wrote: Remove the error handling of bridge_node because the bridge_node is required

Re: [PATCH v2] drm/exynos/dsi: Remove error handling for bridge_node DT parsing

Hello Tobias, Sorry for late reply. On 06/14/2017 09:30 PM, Tobias Jakobi wrote: Hello Hoegeun, my last question (does this regress the case "node required, but absent") still stands. Hoegeun Kwon wrote: Remove the error handling of bridge_node because the bridge_node is required

Re: [PATCH] hwmon: (ibmpowernv) Add current(A) sensors

Hi Cedric, On 06/19/2017 06:22 PM, Cédric Le Goater wrote: > On 06/19/2017 11:25 AM, Shilpasri G Bhat wrote: >> This patch exports current(A) sensors in inband sensors copied to >> main memory by OCC. >> >> Signed-off-by: Shilpasri G Bhat >> --- >>

Re: [PATCH] hwmon: (ibmpowernv) Add current(A) sensors

Hi Cedric, On 06/19/2017 06:22 PM, Cédric Le Goater wrote: > On 06/19/2017 11:25 AM, Shilpasri G Bhat wrote: >> This patch exports current(A) sensors in inband sensors copied to >> main memory by OCC. >> >> Signed-off-by: Shilpasri G Bhat >> --- >> drivers/hwmon/ibmpowernv.c | 4 +++- >> 1 file

[PATCH v3] selftests: lib: Skip tests on missing test modules

With older kernels, printf.sh and bitmap.sh fail because they can't find the respective test modules they are looking for. Use modprobe dry run to check for missing test_XXX module. Error out with the same error code as prime_numbers.sh. v3: As pointed out by Kees, modules can be in-built too,

[PATCH v3] selftests: lib: Skip tests on missing test modules

With older kernels, printf.sh and bitmap.sh fail because they can't find the respective test modules they are looking for. Use modprobe dry run to check for missing test_XXX module. Error out with the same error code as prime_numbers.sh. v3: As pointed out by Kees, modules can be in-built too,

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

On Wed, Jun 7, 2017 at 10:56 PM, Greg KH wrote: > On Wed, Jun 07, 2017 at 07:58:31PM -0700, Kees Cook wrote: >> Many subsystems will not use refcount_t unless there is a way to build the >> kernel so that there is no regression in speed compared to atomic_t. This >>

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

On Wed, Jun 7, 2017 at 10:56 PM, Greg KH wrote: > On Wed, Jun 07, 2017 at 07:58:31PM -0700, Kees Cook wrote: >> Many subsystems will not use refcount_t unless there is a way to build the >> kernel so that there is no regression in speed compared to atomic_t. This >> adds CONFIG_REFCOUNT_FULL to

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: > From: David Windsor > > Some userspace APIs (e.g. ipc, seq_file) provide precise control over > the size of kernel kmallocs, which provides a trivial way to perform > heap overflow attacks where the attacker must

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: > From: David Windsor > > Some userspace APIs (e.g. ipc, seq_file) provide precise control over > the size of kernel kmallocs, which provides a trivial way to perform > heap overflow attacks where the attacker must control neighboring >

  1   2   3   4   5   6   7   8   9   10   >