[PATCH v3 8/9] ARM: OMAP2+: DMA: Add slave map entries for 24xx external request lines

The external request lines are used by tusb6010 on OMAP24xx platforms. Update the map so the driver can use dmaengine API to request the DMA channel. At the same time add temporary map containing only the external DMA request numbers for DT booted case on omap24xx since the tusb6010 stack is not

[PATCH v3 8/9] ARM: OMAP2+: DMA: Add slave map entries for 24xx external request lines

The external request lines are used by tusb6010 on OMAP24xx platforms. Update the map so the driver can use dmaengine API to request the DMA channel. At the same time add temporary map containing only the external DMA request numbers for DT booted case on omap24xx since the tusb6010 stack is not

[PATCH v3 6/9] usb: musb: tusb6010_omap: Allocate DMA channels upfront

Instead of requesting the DMA channel in tusb_omap_dma_allocate() do it when the controller is created and in runtime work from the DMA channel pool. This change is needed for the DMAengine conversion of the driver since the tusb_omap_dma_allocate() is called in interrupt context which might lead

[PATCH v3 6/9] usb: musb: tusb6010_omap: Allocate DMA channels upfront

Instead of requesting the DMA channel in tusb_omap_dma_allocate() do it when the controller is created and in runtime work from the DMA channel pool. This change is needed for the DMAengine conversion of the driver since the tusb_omap_dma_allocate() is called in interrupt context which might lead

[PATCH v3 1/9] dmaengine: omap-dma: port_window support correction for both direction

When the port_window support was verified it was done on setup where only the MEM_TO_DEV direction was enabled. This got un-noticed and thus only this direction worked. Now that I have managed to get a setup to verify both direction it turned out that the setup was incorrect: omap_desc members

[PATCH v3 1/9] dmaengine: omap-dma: port_window support correction for both direction

When the port_window support was verified it was done on setup where only the MEM_TO_DEV direction was enabled. This got un-noticed and thus only this direction worked. Now that I have managed to get a setup to verify both direction it turned out that the setup was incorrect: omap_desc members

[PATCH v3 3/9] usb: musb: tusb6010: Add MUSB_G_NO_SKB_RESERVE to quirks

When using the g_ncm for networking this flag will make sure that the buffer is alligned to 32bit so the DMA can be used to offload the data movement. Signed-off-by: Peter Ujfalusi Tested-by: Tony Lindgren --- drivers/usb/musb/tusb6010.c | 3 ++- 1 file

[PATCH v3 3/9] usb: musb: tusb6010: Add MUSB_G_NO_SKB_RESERVE to quirks

When using the g_ncm for networking this flag will make sure that the buffer is alligned to 32bit so the DMA can be used to offload the data movement. Signed-off-by: Peter Ujfalusi Tested-by: Tony Lindgren --- drivers/usb/musb/tusb6010.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[PATCH v3 5/9] usb: musb: tusb6010_omap: Create new struct for DMA data/parameters

For the DMA we have ch (channel), dmareq and sync_dev parameters both within the tusb_omap_dma_ch and tusb_omap_dma_ch struct. By creating a common struct the code can be simplified when selecting between the shared or multichannel DMA parameters. Signed-off-by: Peter Ujfalusi

[PATCH v3 5/9] usb: musb: tusb6010_omap: Create new struct for DMA data/parameters

For the DMA we have ch (channel), dmareq and sync_dev parameters both within the tusb_omap_dma_ch and tusb_omap_dma_ch struct. By creating a common struct the code can be simplified when selecting between the shared or multichannel DMA parameters. Signed-off-by: Peter Ujfalusi Tested-by: Tony

Re: [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

On 05/11/2017 03:24 PM, David Howells wrote: > Anna Schumaker wrote: > >> Is there any way to split the NFS patch into multiple pieces? > > Are you okay with a patch or two that add code that is unconnected in that > patch, but connected in a later one? Yes, I'm

Re: [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

On 05/11/2017 03:24 PM, David Howells wrote: > Anna Schumaker wrote: > >> Is there any way to split the NFS patch into multiple pieces? > > Are you okay with a patch or two that add code that is unconnected in that > patch, but connected in a later one? Yes, I'm okay with that. Thanks for

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

On Fri, May 12, 2017 at 06:24:34AM -0700, Matthew Giassa wrote: > * Matthew Giassa [2017-05-12 05:57:44 -0700]: > > > * Greg KH [2017-05-12 11:30:08 +0200]: > > > > > On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: > > > >

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

On Fri, May 12, 2017 at 06:24:34AM -0700, Matthew Giassa wrote: > * Matthew Giassa [2017-05-12 05:57:44 -0700]: > > > * Greg KH [2017-05-12 11:30:08 +0200]: > > > > > On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: > > > > +#defineREG_INT_MIG_8723B 0x0304

[PATCH] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

We have one register for each EP to set the maximum packet size for both TX and RX. If for example an RX programming would happen before the previous TX transfer finishes we would reset the TX packet side. To fix this issue, only modify the TX or RX part of the register. Fixes: 550a7375fe72

[PATCH] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

We have one register for each EP to set the maximum packet size for both TX and RX. If for example an RX programming would happen before the previous TX transfer finishes we would reset the TX packet side. To fix this issue, only modify the TX or RX part of the register. Fixes: 550a7375fe72

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On Fri 2017-05-12 14:57:29, Petr Mladek wrote: > On Thu 2017-05-11 17:41:58, Sergey Senozhatsky wrote: > > On (05/11/17 17:24), Sergey Senozhatsky wrote: > > > On (05/09/17 10:29), Sabrina Dubroca wrote: > > > [..] > > > > That's caused a change of behavior in my qemu setup, with this cmdline > >

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On Fri 2017-05-12 14:57:29, Petr Mladek wrote: > On Thu 2017-05-11 17:41:58, Sergey Senozhatsky wrote: > > On (05/11/17 17:24), Sergey Senozhatsky wrote: > > > On (05/09/17 10:29), Sabrina Dubroca wrote: > > > [..] > > > > That's caused a change of behavior in my qemu setup, with this cmdline > >

Re: [PATCH 2/2] xen/input: add multi-touch support

gentle reminder On 05/05/2017 07:45 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 09:40 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 05:10 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote:

Re: [PATCH 2/2] xen/input: add multi-touch support

gentle reminder On 05/05/2017 07:45 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 09:40 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 05:10 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote:

Re: [PATCH 1/2] xen/input: use string constants from PV protocol

gentle reminder On 05/05/2017 07:43 AM, Oleksandr Andrushchenko wrote: Hello, Dmitry! On 04/21/2017 09:42 AM, Oleksandr Andrushchenko wrote: On 04/21/2017 05:11 AM, Dmitry Torokhov wrote: On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko

Re: [PATCH 1/2] xen/input: use string constants from PV protocol

gentle reminder On 05/05/2017 07:43 AM, Oleksandr Andrushchenko wrote: Hello, Dmitry! On 04/21/2017 09:42 AM, Oleksandr Andrushchenko wrote: On 04/21/2017 05:11 AM, Dmitry Torokhov wrote: On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Thu, May 11, 2017 at 02:06:28PM -0700, Tony Lindgren wrote: > > Well maybe the minimal fix for now is just pretty much back to > square one of this thread. This should keep VBUS always on. > Then we can figure out some logic to cut VBUS later on. > > And yeah, the state machine is really hard

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Thu, May 11, 2017 at 02:06:28PM -0700, Tony Lindgren wrote: > > Well maybe the minimal fix for now is just pretty much back to > square one of this thread. This should keep VBUS always on. > Then we can figure out some logic to cut VBUS later on. > > And yeah, the state machine is really hard

Re: [PATCH v3 0/6] Introduce new mode validation callbacks

On 12.05.2017 09:32, Daniel Vetter wrote: > On Thu, May 11, 2017 at 10:05:56AM +0100, Jose Abreu wrote: >> This series is a follow up from the discussion at [1]. We start by >> introducing crtc->mode_valid(), encoder->mode_valid() and >> bridge->mode_valid() callbacks which will be used in

Re: [PATCH v3 0/6] Introduce new mode validation callbacks

On 12.05.2017 09:32, Daniel Vetter wrote: > On Thu, May 11, 2017 at 10:05:56AM +0100, Jose Abreu wrote: >> This series is a follow up from the discussion at [1]. We start by >> introducing crtc->mode_valid(), encoder->mode_valid() and >> bridge->mode_valid() callbacks which will be used in

Re: [PATCH v3] clk: at91: Add sama5d2 suspend/resume

Hi, On 11/05/2017 at 09:17:41 +0200, Nicolas Ferre wrote: > Le 10/05/2017 à 19:09, Alexandre Belloni a écrit : > > On sama5d2, VDD core maybe be cut while in suspend. This means registers > > will be lost. Ensure they are saved and restored properly. > > > > Signed-off-by: Alexandre Belloni

Re: [PATCH v3] clk: at91: Add sama5d2 suspend/resume

Hi, On 11/05/2017 at 09:17:41 +0200, Nicolas Ferre wrote: > Le 10/05/2017 à 19:09, Alexandre Belloni a écrit : > > On sama5d2, VDD core maybe be cut while in suspend. This means registers > > will be lost. Ensure they are saved and restored properly. > > > > Signed-off-by: Alexandre Belloni >

Re: Threads stuck in zap_pid_ns_processes()

Vovo Yang writes: > On Fri, May 12, 2017 at 7:19 AM, Eric W. Biederman > wrote: >> Guenter Roeck writes: >> >>> What I know so far is >>> - We see this condition on a regular basis in the field. Regular is >>> relative, of course -

Re: Threads stuck in zap_pid_ns_processes()

Vovo Yang writes: > On Fri, May 12, 2017 at 7:19 AM, Eric W. Biederman > wrote: >> Guenter Roeck writes: >> >>> What I know so far is >>> - We see this condition on a regular basis in the field. Regular is >>> relative, of course - let's say maybe 1 in a Milion Chromebooks >>> per day

Re: [PATCH v4 1/2] tpm: Refactor tpm_transmit pulling out tpm_transfer function

On 05/10/2017 07:54 PM, Stefan Berger wrote: Refactor tpm_transmit and pull out code sending the command and receiving the response and put this into tpm_transfer. Signed-off-by: Stefan Berger --- drivers/char/tpm/tpm-interface.c | 121

Re: [PATCH v4 1/2] tpm: Refactor tpm_transmit pulling out tpm_transfer function

On 05/10/2017 07:54 PM, Stefan Berger wrote: Refactor tpm_transmit and pull out code sending the command and receiving the response and put this into tpm_transfer. Signed-off-by: Stefan Berger --- drivers/char/tpm/tpm-interface.c | 121 +++ 1 file

Re: [PATCH 4/6] tty: serial: lpuart: add imx7ulp support

On Wed, May 10, 2017 at 01:37:07PM -0700, Stefan Agner wrote: > On 2017-05-09 23:14, Dong Aisheng wrote: > > Hi Stefan, > > > > On Wed, May 10, 2017 at 12:10 PM, Stefan Agner wrote: > >> On 2017-05-09 00:50, Dong Aisheng wrote: > >>> The lpuart of imx7ulp is basically the same

Re: [PATCH 4/6] tty: serial: lpuart: add imx7ulp support

On Wed, May 10, 2017 at 01:37:07PM -0700, Stefan Agner wrote: > On 2017-05-09 23:14, Dong Aisheng wrote: > > Hi Stefan, > > > > On Wed, May 10, 2017 at 12:10 PM, Stefan Agner wrote: > >> On 2017-05-09 00:50, Dong Aisheng wrote: > >>> The lpuart of imx7ulp is basically the same as ls1021a. It's

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

* Matthew Giassa [2017-05-12 05:57:44 -0700]: * Greg KH [2017-05-12 11:30:08 +0200]: On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: +#defineREG_INT_MIG_8723B 0x0304 /* Interrupt Migration */ +#define

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

* Matthew Giassa [2017-05-12 05:57:44 -0700]: * Greg KH [2017-05-12 11:30:08 +0200]: On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: +#defineREG_INT_MIG_8723B 0x0304 /* Interrupt Migration */ +#defineREG_BCNQ_DESA_8723B 0x0308 /*

Re: [PATCH v2 for-4.12-fixes 2/2] sched/fair: Fix O(# total cgroups) in load balance path

Hello, Vincent. On Thu, May 11, 2017 at 09:02:22AM +0200, Vincent Guittot wrote: > Sorry, what i mean is: > When the group entity of a cfs_rq is enqueued, we are sure that either > the parents is already enqueued or it will be enqueued in the same > sequence. We must be sure that no other branch

Re: [PATCH v2 for-4.12-fixes 2/2] sched/fair: Fix O(# total cgroups) in load balance path

Hello, Vincent. On Thu, May 11, 2017 at 09:02:22AM +0200, Vincent Guittot wrote: > Sorry, what i mean is: > When the group entity of a cfs_rq is enqueued, we are sure that either > the parents is already enqueued or it will be enqueued in the same > sequence. We must be sure that no other branch

Re: [PATCH 4.4 42/60] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

On Fri, May 12, 2017 at 12:36:13PM +0100, Ben Hutchings wrote: > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Dan Carpenter > > > >

Re: [PATCH 4.4 42/60] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

On Fri, May 12, 2017 at 12:36:13PM +0100, Ben Hutchings wrote: > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Dan Carpenter > > > > commit

Re: [PATCH 4.4 38/60] USB: serial: sierra: fix bogus alternate-setting assumption

On Fri, May 12, 2017 at 02:14:03PM +0200, Johan Hovold wrote: > On Fri, May 12, 2017 at 12:26:17PM +0100, Ben Hutchings wrote: > > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > > 4.4-stable review patch. If anyone has any objections, please let me > > > know. > > > > > >

Re: [PATCH 4.4 38/60] USB: serial: sierra: fix bogus alternate-setting assumption

On Fri, May 12, 2017 at 02:14:03PM +0200, Johan Hovold wrote: > On Fri, May 12, 2017 at 12:26:17PM +0100, Ben Hutchings wrote: > > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > > 4.4-stable review patch. If anyone has any objections, please let me > > > know. > > > > > >

[PATCH] pid_ns: Fix race between setns'ed fork() and zap_pid_ns_processes()

Imagine we have a pid namespace and a task from its parent's pid_ns, which made setns() to the pid namespace. The task is doing fork(), while the pid namespace's child reaper is dying. We have the race between them: Task from parent pid_ns Child reaper copy_process()

[PATCH] pid_ns: Fix race between setns'ed fork() and zap_pid_ns_processes()

Imagine we have a pid namespace and a task from its parent's pid_ns, which made setns() to the pid namespace. The task is doing fork(), while the pid namespace's child reaper is dying. We have the race between them: Task from parent pid_ns Child reaper copy_process()

[v6 2/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74

From: Linu Cherian Cavium ThunderX2 SMMU implementation doesn't support page 1 register space and PAGE0_REGS_ONLY option is enabled as an errata workaround. This option when turned on, replaces all page 1 offsets used for EVTQ_PROD/CONS, PRIQ_PROD/CONS register access

[v6 2/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74

From: Linu Cherian Cavium ThunderX2 SMMU implementation doesn't support page 1 register space and PAGE0_REGS_ONLY option is enabled as an errata workaround. This option when turned on, replaces all page 1 offsets used for EVTQ_PROD/CONS, PRIQ_PROD/CONS register access with page 0 offsets. SMMU

Re: [PATCH v2] perf report: distinguish between inliners in the same function

On Fri, May 12, 2017 at 12:37:01PM +0200, Milian Wolff wrote: > On Mittwoch, 10. Mai 2017 07:53:52 CEST Namhyung Kim wrote: > > Hi, > > > > On Wed, May 03, 2017 at 11:35:36PM +0200, Milian Wolff wrote: > > > > > > +static enum match_result match_chain_srcline(struct callchain_cursor_node > > >

Re: [PATCH v2] perf report: distinguish between inliners in the same function

On Fri, May 12, 2017 at 12:37:01PM +0200, Milian Wolff wrote: > On Mittwoch, 10. Mai 2017 07:53:52 CEST Namhyung Kim wrote: > > Hi, > > > > On Wed, May 03, 2017 at 11:35:36PM +0200, Milian Wolff wrote: > > > > > > +static enum match_result match_chain_srcline(struct callchain_cursor_node > > >

[v6 3/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #126

From: Geetha Sowjanya Cavium ThunderX2 SMMU doesn't support MSI and also doesn't have unique irq lines for gerror, eventq and cmdq-sync. This patch addresses the issue by checking if any interrupt sources are using same irq number, then they are registered as

[v6 3/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #126

From: Geetha Sowjanya Cavium ThunderX2 SMMU doesn't support MSI and also doesn't have unique irq lines for gerror, eventq and cmdq-sync. This patch addresses the issue by checking if any interrupt sources are using same irq number, then they are registered as shared irqs. Signed-off-by: Geetha

[v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

From: Linu Cherian Cavium ThunderX2 implementation doesn't support second page in SMMU register space. Hence, resource size is set as 64k for this model. Signed-off-by: Linu Cherian Signed-off-by: Geetha Sowjanya

[v6 1/3] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

From: Linu Cherian Cavium ThunderX2 implementation doesn't support second page in SMMU register space. Hence, resource size is set as 64k for this model. Signed-off-by: Linu Cherian Signed-off-by: Geetha Sowjanya --- drivers/acpi/arm64/iort.c | 10 +- 1 file changed, 9 insertions(+),

[v6 0/3] Cavium ThunderX2 SMMUv3 errata workarounds

From: Linu Cherian Cavium ThunderX2 SMMUv3 implementation has two Silicon Erratas. 1. Errata ID #74 SMMU register alias Page 1 is not implemented 2. Errata ID #126 SMMU doesnt support unique IRQ lines and also MSI for gerror, eventq and cmdq-sync The following

[v6 0/3] Cavium ThunderX2 SMMUv3 errata workarounds

From: Linu Cherian Cavium ThunderX2 SMMUv3 implementation has two Silicon Erratas. 1. Errata ID #74 SMMU register alias Page 1 is not implemented 2. Errata ID #126 SMMU doesnt support unique IRQ lines and also MSI for gerror, eventq and cmdq-sync The following patchset does software

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On Thu 2017-05-11 17:41:58, Sergey Senozhatsky wrote: > On (05/11/17 17:24), Sergey Senozhatsky wrote: > > On (05/09/17 10:29), Sabrina Dubroca wrote: > > [..] > > > That's caused a change of behavior in my qemu setup, with this cmdline > > > > > > root=/dev/sda1 console=ttyS1 console=ttyS0 >

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

* Greg KH [2017-05-12 11:30:08 +0200]: On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: +#defineREG_INT_MIG_8723B 0x0304 /* Interrupt Migration */ +#defineREG_BCNQ_DESA_8723B 0x0308 /* TX Beacon Descriptor

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On Thu 2017-05-11 17:41:58, Sergey Senozhatsky wrote: > On (05/11/17 17:24), Sergey Senozhatsky wrote: > > On (05/09/17 10:29), Sabrina Dubroca wrote: > > [..] > > > That's caused a change of behavior in my qemu setup, with this cmdline > > > > > > root=/dev/sda1 console=ttyS1 console=ttyS0 >

Re: [PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

* Greg KH [2017-05-12 11:30:08 +0200]: On Thu, May 11, 2017 at 06:45:24PM -0700, Matthew Giassa wrote: +#defineREG_INT_MIG_8723B 0x0304 /* Interrupt Migration */ +#defineREG_BCNQ_DESA_8723B 0x0308 /* TX Beacon Descriptor Address +

RE: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Geert, On Friday, May 12, 2017, Geert Uytterhoeven wrote: > 12 x 16 = 192, not 384. Opps, my math was off! (I think I need another cup of coffee this morning) > Do you need all possible combinations of input, output, and bi-dir? > I assumed they're mutually exclusive. If not, you need 3

RE: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Geert, On Friday, May 12, 2017, Geert Uytterhoeven wrote: > 12 x 16 = 192, not 384. Opps, my math was off! (I think I need another cup of coffee this morning) > Do you need all possible combinations of input, output, and bi-dir? > I assumed they're mutually exclusive. If not, you need 3

[GIT PULL] sound fixes for 4.12-rc1

Linus, please pull sound fixes for v4.12-rc1 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-fix-4.12-rc1 The topmost commit is 31cbee6a5611f07d2d66f55bb6f8648db5947e32 sound fixes for 4.12-rc1

[GIT PULL] sound fixes for 4.12-rc1

Linus, please pull sound fixes for v4.12-rc1 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-fix-4.12-rc1 The topmost commit is 31cbee6a5611f07d2d66f55bb6f8648db5947e32 sound fixes for 4.12-rc1

[PATCH] staging: wlan-ng: p80211conv: change args types of p80211_caphdr structure to be network compatible.

Change p80211_caphdr structure args types to __be.. to be compatible with byte ordering of the network. and in hfa384x_usb.c make calculations with respect to machine. Signed-off-by: Karim Eshapa --- drivers/staging/wlan-ng/hfa384x_usb.c | 2 +-

[PATCH] staging: wlan-ng: p80211conv: change args types of p80211_caphdr structure to be network compatible.

Change p80211_caphdr structure args types to __be.. to be compatible with byte ordering of the network. and in hfa384x_usb.c make calculations with respect to machine. Signed-off-by: Karim Eshapa --- drivers/staging/wlan-ng/hfa384x_usb.c | 2 +- drivers/staging/wlan-ng/p80211conv.h | 28

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, May 10, 2017, at 12:18 AM, Ian Kent wrote: > The fstatat(2) and statx() calls can pass the flag AT_NO_AUTOMOUNT > which is meant to clear the LOOKUP_AUTOMOUNT flag and prevent triggering > of an automount by the call. But this flag is unconditionally cleared > for all stat family system

Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On Wed, May 10, 2017, at 12:18 AM, Ian Kent wrote: > The fstatat(2) and statx() calls can pass the flag AT_NO_AUTOMOUNT > which is meant to clear the LOOKUP_AUTOMOUNT flag and prevent triggering > of an automount by the call. But this flag is unconditionally cleared > for all stat family system

Re: [Bridge] [PATCH v2 1/2] net: Added mtu parameter to dev_forward_skb calls

On Fri, May 12, 2017 at 10:05 AM, Teco Boot wrote: > IP MTU and L2 MTU are different animals. > > IMHO IP MTU is for fragmentation at sender of a link. There is no need > dropping IP packets at receiver with size > configured IP MTU. IP packets > with size > receiver L2 MTU

Re: [Bridge] [PATCH v2 1/2] net: Added mtu parameter to dev_forward_skb calls

On Fri, May 12, 2017 at 10:05 AM, Teco Boot wrote: > IP MTU and L2 MTU are different animals. > > IMHO IP MTU is for fragmentation at sender of a link. There is no need > dropping IP packets at receiver with size > configured IP MTU. IP packets > with size > receiver L2 MTU will be dropped at

RE: [PATCH] drivers:staging:wlan-ng:hfa384x_usb: Fixing sparse warnings.

On Fri, 12 May 2017 10:07:14 +0200 Greg KH wrote: >First off, why the "Re:" in the subject? > >Second, your subject sucks :) > >Try making it a bit more descriptive as to what you are doing, "fixing >sparse warnings" is very vague. > >On Wed, May 10, 2017 at 03:15:38PM +0200, Karim Eshapa wrote: >

RE: [PATCH] drivers:staging:wlan-ng:hfa384x_usb: Fixing sparse warnings.

On Fri, 12 May 2017 10:07:14 +0200 Greg KH wrote: >First off, why the "Re:" in the subject? > >Second, your subject sucks :) > >Try making it a bit more descriptive as to what you are doing, "fixing >sparse warnings" is very vague. > >On Wed, May 10, 2017 at 03:15:38PM +0200, Karim Eshapa wrote: >

[RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node()

Hi Lorenzo, Are there any news related to these patches ? WBR, Vadim

[RFC/RFT PATCH 1/3] PCI: Introduce pci_bus_find_numa_node()

Hi Lorenzo, Are there any news related to these patches ? WBR, Vadim

[PATCH v2] drm/vc4: Fix resource leak in 'vc4_get_hang_state_ioctl()' in error handling path

If one 'drm_gem_handle_create()' fails, we leak somes handles and some memory. In order to fix it: - move the 'free(bo_state)' at the end of the function so that it is also called in the eror handling path. This has the side effect to also try to free it if the first 'kcalloc' fails.

[PATCH v2] drm/vc4: Fix resource leak in 'vc4_get_hang_state_ioctl()' in error handling path

If one 'drm_gem_handle_create()' fails, we leak somes handles and some memory. In order to fix it: - move the 'free(bo_state)' at the end of the function so that it is also called in the eror handling path. This has the side effect to also try to free it if the first 'kcalloc' fails.

[GIT PULL] power-supply changes for 4.12 (part 2)

Hi Linus, The power-supply subsystem has a few more changes for the v4.12 merge window. -- Sebastian The following changes since commit 6c381663bb3b4febc15b2fb33f046f0b986ce5c5: power: supply: bq24190_charger: Use new extcon_register_notifier_all() (2017-04-14 01:45:06 +0200) are available

[GIT PULL] power-supply changes for 4.12 (part 2)

Hi Linus, The power-supply subsystem has a few more changes for the v4.12 merge window. -- Sebastian The following changes since commit 6c381663bb3b4febc15b2fb33f046f0b986ce5c5: power: supply: bq24190_charger: Use new extcon_register_notifier_all() (2017-04-14 01:45:06 +0200) are available

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Thu, May 11, 2017 at 10:37:07AM -0500, Christoph Lameter wrote: > On Tue, 2 May 2017, Luiz Capitulino wrote: > > > Ah, OK. Got this now. I'll give this patch a try. But I think we want > > to hear from Christoph (who worked on reducing the vmstat interruptions > > in the past). > > A bit

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Thu, May 11, 2017 at 10:37:07AM -0500, Christoph Lameter wrote: > On Tue, 2 May 2017, Luiz Capitulino wrote: > > > Ah, OK. Got this now. I'll give this patch a try. But I think we want > > to hear from Christoph (who worked on reducing the vmstat interruptions > > in the past). > > A bit

Re: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Chris, On Fri, May 12, 2017 at 2:13 PM, Chris Brandt wrote: > On Friday, May 12, 2017, Geert Uytterhoeven wrote: >> Jacopo, Chris: Would two bits per pin/function (none, input, output, >> bidir) >> be sufficient? >> That makes one u16 per pin. So roughtly 12 ports x

Re: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Chris, On Fri, May 12, 2017 at 2:13 PM, Chris Brandt wrote: > On Friday, May 12, 2017, Geert Uytterhoeven wrote: >> Jacopo, Chris: Would two bits per pin/function (none, input, output, >> bidir) >> be sufficient? >> That makes one u16 per pin. So roughtly 12 ports x 16 pins => 384 bytes. >>

Re: [PATCH] scsi: libfc: fix incorrect variable assingment

On Thu, 2017-05-11 at 17:24 -0500, Gustavo A. R. Silva wrote: > Previous assignment was causing the use of the uninitialized variable > _explan_ inside fc_seq_ls_rjt() function, which in this particular > case is being called by fc_seq_els_rsp_send(). > > Addresses-Coverity-ID: 1398125 >

Re: [PATCH] scsi: libfc: fix incorrect variable assingment

On Thu, 2017-05-11 at 17:24 -0500, Gustavo A. R. Silva wrote: > Previous assignment was causing the use of the uninitialized variable > _explan_ inside fc_seq_ls_rjt() function, which in this particular > case is being called by fc_seq_els_rsp_send(). > > Addresses-Coverity-ID: 1398125 >

Re: [PATCH] perf report: don't crash on invalid maps in `-g srcline` mode

On Fri, May 12, 2017 at 12:23:06PM +0200, Milian Wolff wrote: > On Mittwoch, 10. Mai 2017 08:04:23 CEST Namhyung Kim wrote: > > On Tue, May 09, 2017 at 10:50:46PM +0200, Milian Wolff wrote: > > > > > > diff --git a/tools/perf/util/callchain.c b/tools/perf/util/callchain.c > > > index

Re: [PATCH] perf report: don't crash on invalid maps in `-g srcline` mode

On Fri, May 12, 2017 at 12:23:06PM +0200, Milian Wolff wrote: > On Mittwoch, 10. Mai 2017 08:04:23 CEST Namhyung Kim wrote: > > On Tue, May 09, 2017 at 10:50:46PM +0200, Milian Wolff wrote: > > > > > > diff --git a/tools/perf/util/callchain.c b/tools/perf/util/callchain.c > > > index

Re: [PATCH 4.4 38/60] USB: serial: sierra: fix bogus alternate-setting assumption

On Fri, May 12, 2017 at 12:26:17PM +0100, Ben Hutchings wrote: > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Johan Hovold > > > > commit

Re: [PATCH 4.4 38/60] USB: serial: sierra: fix bogus alternate-setting assumption

On Fri, May 12, 2017 at 12:26:17PM +0100, Ben Hutchings wrote: > On Thu, 2017-05-11 at 16:13 +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Johan Hovold > > > > commit

RE: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Geert and Linus, On Friday, May 12, 2017, Geert Uytterhoeven wrote: > Jacopo, Chris: Would two bits per pin/function (none, input, output, > bidir) > be sufficient? > That makes one u16 per pin. So roughtly 12 ports x 16 pins => 384 bytes. > Plus code to handle it. After all not that bad...

RE: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

Hi Geert and Linus, On Friday, May 12, 2017, Geert Uytterhoeven wrote: > Jacopo, Chris: Would two bits per pin/function (none, input, output, > bidir) > be sufficient? > That makes one u16 per pin. So roughtly 12 ports x 16 pins => 384 bytes. > Plus code to handle it. After all not that bad...

Re: [PATCH v2 05/10] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

On Fri, May 12, 2017 at 09:53:55AM +0300, Peter Ujfalusi wrote: > Bin, > > On 2017-05-11 17:12, Bin Liu wrote: > >>which is valid. > > > >So will you update the patch to move the declaration to the beginning of > >the function to avoid this WARNING. I would just fix it locally if you > >prefer. >

Re: [PATCH v2 05/10] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

On Fri, May 12, 2017 at 09:53:55AM +0300, Peter Ujfalusi wrote: > Bin, > > On 2017-05-11 17:12, Bin Liu wrote: > >>which is valid. > > > >So will you update the patch to move the declaration to the beginning of > >the function to avoid this WARNING. I would just fix it locally if you > >prefer. >

Re: [ANNOUNCE] util-linux v2.30-rc1

On Fri, May 12, 2017 at 02:03:10PM +0200, Karel Zak wrote: > The util-linux release v2.30-rc1 is available at > > http://www.kernel.org/pub/linux/utils/util-linux/v2.30-rc1 Ah, the correct URL is: https://www.kernel.org/pub/linux/utils/util-linux/v2.30/ Karel -- Karel Zak

Re: [ANNOUNCE] util-linux v2.30-rc1

On Fri, May 12, 2017 at 02:03:10PM +0200, Karel Zak wrote: > The util-linux release v2.30-rc1 is available at > > http://www.kernel.org/pub/linux/utils/util-linux/v2.30-rc1 Ah, the correct URL is: https://www.kernel.org/pub/linux/utils/util-linux/v2.30/ Karel -- Karel Zak

[PATCHv2] watchdog: core: add option to avoid early handling of watchdog

On some systems its desirable to have watchdog reboot the system when it does not come up fast enough. This adds a kernel parameter to disable the auto-update of watchdog before userspace takes over and a kernel option to set the default. The info messages were added to shorten error searching on

[PATCHv2] watchdog: core: add option to avoid early handling of watchdog

On some systems its desirable to have watchdog reboot the system when it does not come up fast enough. This adds a kernel parameter to disable the auto-update of watchdog before userspace takes over and a kernel option to set the default. The info messages were added to shorten error searching on

Re: [PATCHv3] arm64/cpufeature: don't use mutex in bringup path

On 12/05/17 11:15, Mark Rutland wrote: Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which must take the jump_label mutex. We call cpus_set_cap() in the secondary bringup path, from the idle thread where interrupts are disabled. Taking a mutex in this path "is a NONO"

Re: [PATCHv3] arm64/cpufeature: don't use mutex in bringup path

On 12/05/17 11:15, Mark Rutland wrote: Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which must take the jump_label mutex. We call cpus_set_cap() in the secondary bringup path, from the idle thread where interrupts are disabled. Taking a mutex in this path "is a NONO"

[ANNOUNCE] util-linux v2.30-rc1

The util-linux release v2.30-rc1 is available at http://www.kernel.org/pub/linux/utils/util-linux/v2.30-rc1 Feedback and bug reports, as always, are welcomed. Karel Util-linux 2.30 Release Notes = The libblkid library has been fixed to extract LABEL= and

[ANNOUNCE] util-linux v2.30-rc1

The util-linux release v2.30-rc1 is available at http://www.kernel.org/pub/linux/utils/util-linux/v2.30-rc1 Feedback and bug reports, as always, are welcomed. Karel Util-linux 2.30 Release Notes = The libblkid library has been fixed to extract LABEL= and

[PATCH 2/4] irqdomain: Let irq_domain_mapping display ACPI fwnode attributes

If we're using ACPI, there is no of_node to display. But ACPI can use a struct irqchip_fwid as a domain identifier, and we can display the name contained in that structure. We end-up with something like this: pMSI 0 0 0 irqchip@e118 MSI 37 0

[PATCH 1/4] irqdomain: Let irq_domain_mapping display hierarchical domains

Hierarchical domains seem to be hard to grasp, and a number of aspiring kernel hackers find them utterly discombobulating. In order to ease their pain, let's make them appear in /sys/kernel/debug/irq_domain_mapping, such as the following: 96 0x81808 MSI0x (null) RADIX MSI

<    4   5   6   7   8   9   10   11   12   13   >