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

Hi all, After merging the sunxi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpu/drm/sun4i/sun4i_crtc.c: In function 'sun4i_crtc_enable_vblank': drivers/gpu/drm/sun4i/sun4i_crtc.c:109:31: error: 'struct sun4i_crtc' has no member named 'drv' struct

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

Hi all, After merging the sunxi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpu/drm/sun4i/sun4i_crtc.c: In function 'sun4i_crtc_enable_vblank': drivers/gpu/drm/sun4i/sun4i_crtc.c:109:31: error: 'struct sun4i_crtc' has no member named 'drv' struct

Re: [PATCH] ASoC: Intel: Skylake: fix spelling mistake: "allocationf" -> "allocation"

On Tue, Feb 21, 2017 at 06:50:05PM +, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in dev_err message. Acked-by: Vinod Koul -- ~Vinod

Re: [PATCH] ASoC: Intel: Skylake: fix spelling mistake: "allocationf" -> "allocation"

On Tue, Feb 21, 2017 at 06:50:05PM +, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in dev_err message. Acked-by: Vinod Koul -- ~Vinod

Re: [linux-sunxi] [PATCH v3 0/5] Add dual-role OTG support for Allwinner H3

Hi Icenowy, when I was trying to add OTG support I found an issue with powercycling. When I have USB cable connecting PC and the OTG port on the SBC, when the board enables the vbus, it would become impossible to power cycle the board after poweroff. The reason being that when vbus is enabled,

Re: [linux-sunxi] [PATCH v3 0/5] Add dual-role OTG support for Allwinner H3

Hi Icenowy, when I was trying to add OTG support I found an issue with powercycling. When I have USB cable connecting PC and the OTG port on the SBC, when the board enables the vbus, it would become impossible to power cycle the board after poweroff. The reason being that when vbus is enabled,

Re: [PATCH] pciehp: Fix race condition handling surprise link-down

On Fri, Feb 03, 2017 at 10:51:04AM -0600, Bjorn Helgaas wrote: > On Thu, Feb 02, 2017 at 10:00:53PM -0800, Raj, Ashok wrote: > > ... > > Just to summarize, we only queue the POWEROFF due to surprise link down > > and another POWERON due to link becoming back up. The transient link-down > > events

Re: [PATCH] pciehp: Fix race condition handling surprise link-down

On Fri, Feb 03, 2017 at 10:51:04AM -0600, Bjorn Helgaas wrote: > On Thu, Feb 02, 2017 at 10:00:53PM -0800, Raj, Ashok wrote: > > ... > > Just to summarize, we only queue the POWEROFF due to surprise link down > > and another POWERON due to link becoming back up. The transient link-down > > events

Re: linux-next: manual merge of the sunxi tree with the drm-misc tree

On Tue, Mar 7, 2017 at 7:59 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the sunxi tree got a conflict in: > > drivers/gpu/drm/sun4i/sun4i_drv.c > > between commit: > > 50480a78e282 ("drm: sun4i: use vblank hooks in struct drm_crtc_funcs") > >

Re: linux-next: manual merge of the sunxi tree with the drm-misc tree

On Tue, Mar 7, 2017 at 7:59 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the sunxi tree got a conflict in: > > drivers/gpu/drm/sun4i/sun4i_drv.c > > between commit: > > 50480a78e282 ("drm: sun4i: use vblank hooks in struct drm_crtc_funcs") > > from the drm-misc tree

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

On 03/06/2017 07:07 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/net/sock.h:64:0, > from include/linux/tcp.h:23, > from

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

On 03/06/2017 07:07 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/net/sock.h:64:0, > from include/linux/tcp.h:23, > from

Re: [PATCH v2 0/4] fujitsu_init() cleanup

Hi Michael On Mon, Mar 06, 2017 at 07:47:23PM +0100, Micha?? K??pie?? wrote: > > > In light of the above findings, what would you like to do? > > > > Thanks for testing, good that we caught this before the patch series was > > applied. I think it is reasonable to skip applying this version of

Re: [PATCH v2 0/4] fujitsu_init() cleanup

Hi Michael On Mon, Mar 06, 2017 at 07:47:23PM +0100, Micha?? K??pie?? wrote: > > > In light of the above findings, what would you like to do? > > > > Thanks for testing, good that we caught this before the patch series was > > applied. I think it is reasonable to skip applying this version of

Re: [PATCH net-next 1/5] ldmvsw: better use of link up and down on ldom vswitch

On 03/06/2017 03:15 PM, Shannon Nelson wrote: > When an ldom VM is bound, the network vswitch infrastructure is set up for > it, but was being forced 'UP' by the userland switch configuration script. > When 'UP' but not actually connected to a running VM, the ipv6 neighbor > probes fail (not a

Re: [PATCH net-next 1/5] ldmvsw: better use of link up and down on ldom vswitch

On 03/06/2017 03:15 PM, Shannon Nelson wrote: > When an ldom VM is bound, the network vswitch infrastructure is set up for > it, but was being forced 'UP' by the userland switch configuration script. > When 'UP' but not actually connected to a running VM, the ipv6 neighbor > probes fail (not a

[PATCH net-next 2/5] sunvnet: add stats to track ldom to ldom packets and bytes

In this driver, there is a "port" created for the connection to each of the other ldoms; a netdev queue is mapped to each port, and they are collected under a single netdev. The generic netdev statistics show us all the traffic in and out of our network device, but don't show individual

Re: [PATCH] scsi: lpfc: replace init_timer by setup_timer

> "Jiri" == Jiri Slaby writes: Jiri> From: Tomas Jasek This patch shortens every Jiri> init_timer in lpfc module followed by function and data assignment Jiri> using setup_timer. This is purely cleanup patch, it does not add Jiri> new functionality nor

Re: Hundreds of null PATH records for *init_module syscall audit logs

On 2017-03-03 19:19, Paul Moore wrote: > On Tue, Feb 28, 2017 at 10:37 PM, Richard Guy Briggs wrote: > > Sorry, I forgot to include Cc: in this cover letter for context to the 4 > > alt patches. > > > > On 2017-02-28 22:15, Richard Guy Briggs wrote: > >> The background to this

Re: [PATCH] scsi: lpfc: replace init_timer by setup_timer

> "Jiri" == Jiri Slaby writes: Jiri> From: Tomas Jasek This patch shortens every Jiri> init_timer in lpfc module followed by function and data assignment Jiri> using setup_timer. This is purely cleanup patch, it does not add Jiri> new functionality nor remove any existing functionality.

Re: Hundreds of null PATH records for *init_module syscall audit logs

On 2017-03-03 19:19, Paul Moore wrote: > On Tue, Feb 28, 2017 at 10:37 PM, Richard Guy Briggs wrote: > > Sorry, I forgot to include Cc: in this cover letter for context to the 4 > > alt patches. > > > > On 2017-02-28 22:15, Richard Guy Briggs wrote: > >> The background to this is: > >>

[PATCH net-next 2/5] sunvnet: add stats to track ldom to ldom packets and bytes

In this driver, there is a "port" created for the connection to each of the other ldoms; a netdev queue is mapped to each port, and they are collected under a single netdev. The generic netdev statistics show us all the traffic in and out of our network device, but don't show individual

[PATCH v7 04/07] iommu/ipmmu-vmsa: Break out domain allocation code

From: Magnus Damm Break out the domain allocation code into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since V6: - None

[PATCH v7 04/07] iommu/ipmmu-vmsa: Break out domain allocation code

From: Magnus Damm Break out the domain allocation code into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since V6: - None drivers/iommu/ipmmu-vmsa.c | 13 + 1 file changed, 9

Re: Hundreds of null PATH records for *init_module syscall audit logs

On 2017-03-06 17:30, Jessica Yu wrote: > +++ Richard Guy Briggs [06/03/17 16:49 -0500]: > >On 2017-03-03 19:22, Paul Moore wrote: > >>On Fri, Mar 3, 2017 at 4:14 PM, Richard Guy Briggs wrote: > >>> On 2017-02-28 23:15, Steve Grubb wrote: > On Tuesday, February 28, 2017

Re: Hundreds of null PATH records for *init_module syscall audit logs

On 2017-03-06 17:30, Jessica Yu wrote: > +++ Richard Guy Briggs [06/03/17 16:49 -0500]: > >On 2017-03-03 19:22, Paul Moore wrote: > >>On Fri, Mar 3, 2017 at 4:14 PM, Richard Guy Briggs wrote: > >>> On 2017-02-28 23:15, Steve Grubb wrote: > On Tuesday, February 28, 2017 10:37:04 PM EST

Re: [PATCH] mmc: core: Fix access to HS400-ES devices

ping ... Ulf, I know it is early for a ping. However, the patch causing all HS400-ES devices to fail already made it into various stable releases, and I think it would be very desirable to get those back to working. Thanks, Guenter On Wed, Mar 01, 2017 at 02:11:47PM -0800, Guenter Roeck

Re: [PATCH] mmc: core: Fix access to HS400-ES devices

ping ... Ulf, I know it is early for a ping. However, the patch causing all HS400-ES devices to fail already made it into various stable releases, and I think it would be very desirable to get those back to working. Thanks, Guenter On Wed, Mar 01, 2017 at 02:11:47PM -0800, Guenter Roeck

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Tue, Mar 07, 2017 at 01:07:54AM +0100, Christoph Hellwig wrote: > I like killing it, but shouldn't we just try a normal kmem_zalloc? > At least for the fallback it's the right thing, and even for an > order 2 allocation it seems like a useful first try. I'm confused -- kmem_zalloc_large tries

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Tue, Mar 07, 2017 at 01:07:54AM +0100, Christoph Hellwig wrote: > I like killing it, but shouldn't we just try a normal kmem_zalloc? > At least for the fallback it's the right thing, and even for an > order 2 allocation it seems like a useful first try. I'm confused -- kmem_zalloc_large tries

Re: [PATCH] scsi: qedf: Use vsprintf extension %pad

> "Joe" == Joe Perches writes: Joe> Using %llx for a dma_addr_t can lead to format/argument mismatches. Joe> Use %pad and the address of the dma_addr_t instead. Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: qedf: Use vsprintf extension %pad

> "Joe" == Joe Perches writes: Joe> Using %llx for a dma_addr_t can lead to format/argument mismatches. Joe> Use %pad and the address of the dma_addr_t instead. Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

[PATCH net-next 0/5] sunvnet: better connection management

These patches remove some problems in handling of carrier state with the ldmvsw vswitch, remove an xoff misuse in sunvnet, and add stats for debug and tracking of point-to-point connections between the ldom VMs. Shannon Nelson (5): ldmvsw: better use of link up and down on ldom vswitch

[PATCH net-next 0/5] sunvnet: better connection management

These patches remove some problems in handling of carrier state with the ldmvsw vswitch, remove an xoff misuse in sunvnet, and add stats for debug and tracking of point-to-point connections between the ldom VMs. Shannon Nelson (5): ldmvsw: better use of link up and down on ldom vswitch

[PATCH v7 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

From: Magnus Damm Not all architectures have an iommu member in their archdata, so use #ifdefs support build with COMPILE_TEST on any architecture. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since

[PATCH v7 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

From: Magnus Damm Not all architectures have an iommu member in their archdata, so use #ifdefs support build with COMPILE_TEST on any architecture. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since V6: - Updated patch to handle newly introduced functions in: [PATCH

[PATCH v7 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code

From: Magnus Damm Break out the utlb parsing code and dev_data allocation into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since V6:

[PATCH v7 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency

From: Magnus Damm Neither the ARM page table code enabled by IOMMU_IO_PGTABLE_LPAE nor the IPMMU_VMSA driver actually depends on ARM_LPAE, so get rid of the dependency. Tested with ipmmu-vmsa on r8a7794 ALT and a kernel config using: # CONFIG_ARM_LPAE is not set

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

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/net/sock.h:64:0, from include/linux/tcp.h:23, from include/linux/ipv6.h:83, from include/net/ipv6.h:16,

[PATCH v7 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code

From: Magnus Damm Break out the utlb parsing code and dev_data allocation into a separate function. This is preparation for future code sharing. Signed-off-by: Magnus Damm Reviewed-by: Joerg Roedel --- Changes since V6: - None drivers/iommu/ipmmu-vmsa.c | 58

[PATCH v7 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency

From: Magnus Damm Neither the ARM page table code enabled by IOMMU_IO_PGTABLE_LPAE nor the IPMMU_VMSA driver actually depends on ARM_LPAE, so get rid of the dependency. Tested with ipmmu-vmsa on r8a7794 ALT and a kernel config using: # CONFIG_ARM_LPAE is not set Signed-off-by: Magnus Damm

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

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/net/sock.h:64:0, from include/linux/tcp.h:23, from include/linux/ipv6.h:83, from include/net/ipv6.h:16,

Re: [PATCH v3] MIPS: Fix build breakage caused by header file changes

On 03/06/2017 03:20 PM, James Hogan wrote: Hi Guenter, On Mon, Mar 06, 2017 at 11:13:55AM -0800, Guenter Roeck wrote: Since commit f3ac60671954 ("sched/headers: Move task-stack related APIs from to ") and commit f780d89a0e82 ("sched/headers: Remove from "), various mips builds fail as

[PATCH 2/2] usb: xhci: remove dummy extra_priv_size for size of xhci_hcd struct

because hcd_priv_size is already size of xhci_hcd struct, extra_priv_size is not needed anymore for MTK and tegra drivers. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c |1 - drivers/usb/host/xhci-tegra.c |1 - 2 files changed, 2 deletions(-)

[PATCH 1/2] usb: xhci-mtk: check hcc_params after adding primary hcd

hcc_params is set in xhci_gen_setup() called from usb_add_hcd(), so checks the Maximum Primary Stream Array Size in the hcc_params register after adding primary hcd. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c |6 +++--- 1 file changed, 3

[PATCH 2/2] usb: xhci: remove dummy extra_priv_size for size of xhci_hcd struct

because hcd_priv_size is already size of xhci_hcd struct, extra_priv_size is not needed anymore for MTK and tegra drivers. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c |1 - drivers/usb/host/xhci-tegra.c |1 - 2 files changed, 2 deletions(-) diff --git

[PATCH 1/2] usb: xhci-mtk: check hcc_params after adding primary hcd

hcc_params is set in xhci_gen_setup() called from usb_add_hcd(), so checks the Maximum Primary Stream Array Size in the hcc_params register after adding primary hcd. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

Re: [PATCH v3] MIPS: Fix build breakage caused by header file changes

On 03/06/2017 03:20 PM, James Hogan wrote: Hi Guenter, On Mon, Mar 06, 2017 at 11:13:55AM -0800, Guenter Roeck wrote: Since commit f3ac60671954 ("sched/headers: Move task-stack related APIs from to ") and commit f780d89a0e82 ("sched/headers: Remove from "), various mips builds fail as

[PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling

From: Magnus Damm The IPMMU driver is using DT these days, and platform data is no longer used by the driver. Remove unused code. Signed-off-by: Magnus Damm Reviewed-by: Laurent Pinchart Reviewed-by:

[PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling

From: Magnus Damm The IPMMU driver is using DT these days, and platform data is no longer used by the driver. Remove unused code. Signed-off-by: Magnus Damm Reviewed-by: Laurent Pinchart Reviewed-by: Joerg Roedel --- Changes since V6: - None drivers/iommu/ipmmu-vmsa.c |5 - 1

[PATCH v7 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V7

iommu/ipmmu-vmsa: IPMMU multi-arch update V7 [PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling [PATCH v7 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context [PATCH v7 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code [PATCH v7 04/07] iommu/ipmmu-vmsa:

[PATCH v7 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V7

iommu/ipmmu-vmsa: IPMMU multi-arch update V7 [PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling [PATCH v7 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context [PATCH v7 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code [PATCH v7 04/07] iommu/ipmmu-vmsa:

[PATCH v7 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context

From: Magnus Damm Introduce a bitmap for context handing and convert the interrupt routine to handle all registered contexts. At this point the number of contexts are still limited. Also remove the use of the ARM specific mapping variable from ipmmu_irq() to allow

[PATCH v7 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context

From: Magnus Damm Introduce a bitmap for context handing and convert the interrupt routine to handle all registered contexts. At this point the number of contexts are still limited. Also remove the use of the ARM specific mapping variable from ipmmu_irq() to allow compile on ARM64.

[PATCH v7 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops

From: Magnus Damm Introduce an alternative set of iommu_ops suitable for 64-bit ARM as well as 32-bit ARM when CONFIG_IOMMU_DMA=y. Also adjust the Kconfig to depend on ARM or IOMMU_DMA. Initialize the device from ->xlate() when CONFIG_IOMMU_DMA=y. Signed-off-by:

[PATCH v7 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops

From: Magnus Damm Introduce an alternative set of iommu_ops suitable for 64-bit ARM as well as 32-bit ARM when CONFIG_IOMMU_DMA=y. Also adjust the Kconfig to depend on ARM or IOMMU_DMA. Initialize the device from ->xlate() when CONFIG_IOMMU_DMA=y. Signed-off-by: Magnus Damm --- Changes since

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Mon, Mar 06, 2017 at 04:13:28PM -0800, Darrick J. Wong wrote: > On Tue, Mar 07, 2017 at 01:07:54AM +0100, Christoph Hellwig wrote: > > I like killing it, but shouldn't we just try a normal kmem_zalloc? > > At least for the fallback it's the right thing, and even for an > > order 2 allocation it

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Mon, Mar 06, 2017 at 04:13:28PM -0800, Darrick J. Wong wrote: > On Tue, Mar 07, 2017 at 01:07:54AM +0100, Christoph Hellwig wrote: > > I like killing it, but shouldn't we just try a normal kmem_zalloc? > > At least for the fallback it's the right thing, and even for an > > order 2 allocation it

[PATCH v2 2/2] ARM: qcom_defconfig: Enable Qualcomm remoteproc and related drivers

An adsp-pil node is present in at least the MSM8974 SoC. Simply enable all Qualcomm remoteproc drivers to avoid more work in the future. The SMP2P driver is required for adsp-pil to initialize correctly. Enable the SMSM driver at Bjorn Andersson's request: "We also need CONFIG_QCOM_SMSM=y here,

[PATCH v2 2/2] ARM: qcom_defconfig: Enable Qualcomm remoteproc and related drivers

An adsp-pil node is present in at least the MSM8974 SoC. Simply enable all Qualcomm remoteproc drivers to avoid more work in the future. The SMP2P driver is required for adsp-pil to initialize correctly. Enable the SMSM driver at Bjorn Andersson's request: "We also need CONFIG_QCOM_SMSM=y here,

Re: [PATCH] [v2] scsi: qedi: fix build error without DEBUG_FS

> "Arnd" == Arnd Bergmann writes: Arnd> Without CONFIG_DEBUG_FS, we run into a link error: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] [v2] scsi: qedi: fix build error without DEBUG_FS

> "Arnd" == Arnd Bergmann writes: Arnd> Without CONFIG_DEBUG_FS, we run into a link error: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] qla2xxx: Fix ql_dump_buffer

> "Joe" == Joe Perches writes: Joe> Recent printk changes for KERN_CONT cause this logging to be Joe> defectively emitted on multiple lines. Fix it. Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] qla2xxx: Fix ql_dump_buffer

> "Joe" == Joe Perches writes: Joe> Recent printk changes for KERN_CONT cause this logging to be Joe> defectively emitted on multiple lines. Fix it. Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Bart, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Bart Van Assche > Sent: Monday, March 6, 2017 6:36 PM > To: Doug Ledford > Cc: Greg Kroah-Hartman ; Sebastian

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Bart, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Bart Van Assche > Sent: Monday, March 6, 2017 6:36 PM > To: Doug Ledford > Cc: Greg Kroah-Hartman ; Sebastian Ott > ; Parav Pandit ; linux- >

[PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

The dma mapping operations of several architectures and also of several I/O MMU implementations need to translate a struct device pointer into a struct pci_dev pointer. This translation is performed by to_pci_dev(). That macro assumes that struct device is embedded in struct pci_dev. However, that

[PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

The dma mapping operations of several architectures and also of several I/O MMU implementations need to translate a struct device pointer into a struct pci_dev pointer. This translation is performed by to_pci_dev(). That macro assumes that struct device is embedded in struct pci_dev. However, that

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Tue, 2017-03-07 at 02:41 +, Parav Pandit wrote: > Compilation would break when CONFIG_PCI is not defined for some embedded > platforms. > More than that, including specific pci_dev structure pointer in generic > structure such as device just doesn't sound right. > I tested equivalent

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Tue, 2017-03-07 at 02:41 +, Parav Pandit wrote: > Compilation would break when CONFIG_PCI is not defined for some embedded > platforms. > More than that, including specific pci_dev structure pointer in generic > structure such as device just doesn't sound right. > I tested equivalent

linux-next: manual merge of the drm-misc tree with the drm-intel tree

Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/i915/i915_debugfs.c between commits: 418e3cd80051 ("drm/i915: Show the current i915_params in debugfs/i915_capabilites") 317eaa95081b ("drm/i915/debugfs: Add i915_hpd_storm_ctl") from the drm-intel

linux-next: manual merge of the drm-misc tree with the drm-intel tree

Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/i915/i915_debugfs.c between commits: 418e3cd80051 ("drm/i915: Show the current i915_params in debugfs/i915_capabilites") 317eaa95081b ("drm/i915/debugfs: Add i915_hpd_storm_ctl") from the drm-intel

Re: mmotm 2017-03-06-16-52 uploaded

Hi Andrew, On Mon, 06 Mar 2017 16:53:06 -0800 a...@linux-foundation.org wrote: > > linux-next-rejects.patch Just wondering why this includes "struct iomap" -> "const struct iomap" conversions when they should just be done in a regular patch. -- Cheers, Stephen Rothwell

Re: mmotm 2017-03-06-16-52 uploaded

Hi Andrew, On Mon, 06 Mar 2017 16:53:06 -0800 a...@linux-foundation.org wrote: > > linux-next-rejects.patch Just wondering why this includes "struct iomap" -> "const struct iomap" conversions when they should just be done in a regular patch. -- Cheers, Stephen Rothwell

Re: [alsa-devel] [PATCH v2 03/12] ASoC: sun8i-codec-analog: split out mbias

Hi Icenowy, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc1 next-20170306] [cannot apply to robh/for-next asoc/for-next] [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

Re: [alsa-devel] [PATCH v2 03/12] ASoC: sun8i-codec-analog: split out mbias

Hi Icenowy, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc1 next-20170306] [cannot apply to robh/for-next asoc/for-next] [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

[PATCH v2 1/2] ARM: dts: msm8974: Hook up adsp-pil's xo clock

Without this patch (and with CONFIG_QCOM_ADSP_PIL), I get this error: [0.711529] qcom_adsp_pil adsp-pil: failed to get xo clock [0.711540] remoteproc remoteproc0: releasing adsp-pil With this patch, adsp-pil can initialize correctly. Signed-off-by: Jonathan Neuschäfer

[PATCH v2 1/2] ARM: dts: msm8974: Hook up adsp-pil's xo clock

Without this patch (and with CONFIG_QCOM_ADSP_PIL), I get this error: [0.711529] qcom_adsp_pil adsp-pil: failed to get xo clock [0.711540] remoteproc remoteproc0: releasing adsp-pil With this patch, adsp-pil can initialize correctly. Signed-off-by: Jonathan Neuschäfer

Re: [linux-sunxi] [PATCH v3 0/5] Add dual-role OTG support for Allwinner H3

On Tue, Mar 7, 2017 at 8:24 AM, Icenowy Zheng wrote: > > > 07.03.2017, 07:48, "Ondřej Jirman" : >> Hi Icenowy, >> >> when I was trying to add OTG support I found an issue with powercycling. >> When I have USB cable connecting PC and the OTG port on the SBC,

Re: [linux-sunxi] [PATCH v3 0/5] Add dual-role OTG support for Allwinner H3

On Tue, Mar 7, 2017 at 8:24 AM, Icenowy Zheng wrote: > > > 07.03.2017, 07:48, "Ondřej Jirman" : >> Hi Icenowy, >> >> when I was trying to add OTG support I found an issue with powercycling. >> When I have USB cable connecting PC and the OTG port on the SBC, when >> the board enables the vbus, it

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Bart, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Bart Van Assche > Sent: Monday, March 6, 2017 6:36 PM > To: Doug Ledford > Cc: Greg Kroah-Hartman ; Sebastian

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Bart, > -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Bart Van Assche > Sent: Monday, March 6, 2017 6:36 PM > To: Doug Ledford > Cc: Greg Kroah-Hartman ; Sebastian Ott > ; Parav Pandit ; linux- >

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

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/machine_kexec.c: In function 'machine_kexec': arch/arm/kernel/machine_kexec.c:163:2: error: implicit declaration of function 'set_kernel_text_rw'

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

Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/machine_kexec.c: In function 'machine_kexec': arch/arm/kernel/machine_kexec.c:163:2: error: implicit declaration of function 'set_kernel_text_rw'

[PATCH] ARM: dts: at91: sama5d2: add m_can nodes

Add nodes to support the Controller Area Network(M_CAN) on SAMA5D2. As said in SAMA5D2 datasheet, the CAN clock is recommended to use frequencies of 20, 40 or 80 MHz. To achieve these frequencies, PMC GCLK3 must select the UPLLCK(480 MHz) as source clock and divide by 24, 12, or 6. So, the

[PATCH] ARM: dts: at91: sama5d2: add m_can nodes

Add nodes to support the Controller Area Network(M_CAN) on SAMA5D2. As said in SAMA5D2 datasheet, the CAN clock is recommended to use frequencies of 20, 40 or 80 MHz. To achieve these frequencies, PMC GCLK3 must select the UPLLCK(480 MHz) as source clock and divide by 24, 12, or 6. So, the

[PATCH] staging: wilc1000: Fix sparse warnings incorrect type assignment

Fixed sparse warnings drivers/staging/wilc1000//wilc_wfi_cfgoperations.c:2011:52: warning: incorrect type in assignment (different base types) drivers/staging/wilc1000//wilc_wfi_cfgoperations.c:2011:52:expected unsigned short [unsigned] [assigned] [usertype] ht_ext_params

[PATCH] staging: wilc1000: Fix sparse warnings incorrect type assignment

Fixed sparse warnings drivers/staging/wilc1000//wilc_wfi_cfgoperations.c:2011:52: warning: incorrect type in assignment (different base types) drivers/staging/wilc1000//wilc_wfi_cfgoperations.c:2011:52:expected unsigned short [unsigned] [assigned] [usertype] ht_ext_params

[PATCH] ARM: at91/defconfig: add MCAN driver to sama5_defconfig

Add the Controller Area Network (MCAN) driver compilation for sama5 default configuration. Is used by sama5d2 SoC for instance. Signed-off-by: Wenyou Yang --- arch/arm/configs/sama5_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] ARM: at91/defconfig: add MCAN driver to sama5_defconfig

Add the Controller Area Network (MCAN) driver compilation for sama5 default configuration. Is used by sama5d2 SoC for instance. Signed-off-by: Wenyou Yang --- arch/arm/configs/sama5_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/sama5_defconfig

Re: [REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Excellent! Thanks! Let me know if you see anything else that needs to change. On Mon, Mar 06, 2017 at 08:45:33AM +, Masaki Ota wrote: > Hi, Paul, > > I understand the current situation. > We have three devices that have ID: E7=73 03 28. > > DELL: Normal Pad type (There are Left and right

Re: [REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Excellent! Thanks! Let me know if you see anything else that needs to change. On Mon, Mar 06, 2017 at 08:45:33AM +, Masaki Ota wrote: > Hi, Paul, > > I understand the current situation. > We have three devices that have ID: E7=73 03 28. > > DELL: Normal Pad type (There are Left and right

[PATCH 12/18] pstore: Pass record contents instead of copying

pstore_mkfile() shouldn't have to memcpy the record contents. It can use the existing copy instead. This adjusts the allocation lifetime management and renames the contents variable from "data" to "buf" to assist moving to struct pstore_record in the future. Signed-off-by: Kees Cook

[PATCH 12/18] pstore: Pass record contents instead of copying

pstore_mkfile() shouldn't have to memcpy the record contents. It can use the existing copy instead. This adjusts the allocation lifetime management and renames the contents variable from "data" to "buf" to assist moving to struct pstore_record in the future. Signed-off-by: Kees Cook ---

RE: [PATCH 1/4] watchdog: sama5d4: fix WDDIS handling

> -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2017年3月3日 1:31 > To: Guenter Roeck > Cc: Wim Van Sebroeck ; Nicolas Ferre - M43238 > ; Wenyou Yang - A41535 >

RE: [PATCH 1/4] watchdog: sama5d4: fix WDDIS handling

> -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2017年3月3日 1:31 > To: Guenter Roeck > Cc: Wim Van Sebroeck ; Nicolas Ferre - M43238 > ; Wenyou Yang - A41535 > ; linux-watch...@vger.kernel.org; linux-arm- > ker...@lists.infradead.org;

Re: [GIT pull] CPU hotplug updates for 4.9

On Mon, 2016-10-03 at 19:37 +0200, Thomas Gleixner wrote: > Yet another batch of cpu hotplug core updates and conversions: > > - Provide core infrastructure for multi instance drivers so the drivers > do not have to keep custom lists. > > - Convert custom lists to the new infrastructure.

Re: [GIT pull] CPU hotplug updates for 4.9

On Mon, 2016-10-03 at 19:37 +0200, Thomas Gleixner wrote: > Yet another batch of cpu hotplug core updates and conversions: > > - Provide core infrastructure for multi instance drivers so the drivers > do not have to keep custom lists. > > - Convert custom lists to the new infrastructure.

RE: [PATCH 2/4] watchdog: sama5d4: fix race condition

> -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2017年3月3日 1:31 > To: Guenter Roeck > Cc: Wim Van Sebroeck ; Nicolas Ferre - M43238 > ; Wenyou Yang - A41535 >

RE: [PATCH 2/4] watchdog: sama5d4: fix race condition

> -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: 2017年3月3日 1:31 > To: Guenter Roeck > Cc: Wim Van Sebroeck ; Nicolas Ferre - M43238 > ; Wenyou Yang - A41535 > ; linux-watch...@vger.kernel.org; linux-arm- > ker...@lists.infradead.org;

<    1   2   3   4   5   6   7   8   9   10   >