[PATCH 2/2] f2fs: report error for f2fs_parent_dir

If there is no dentry, we can report its error correctly. Signed-off-by: Jaegeuk Kim --- fs/f2fs/namei.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index 78efe00..618829e 100644 --- a/fs/f2fs/namei.c

[PATCH 2/2] f2fs: report error for f2fs_parent_dir

If there is no dentry, we can report its error correctly. Signed-off-by: Jaegeuk Kim --- fs/f2fs/namei.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index 78efe00..618829e 100644 --- a/fs/f2fs/namei.c +++

[PATCH 1/2] f2fs: check only data or node for summary

We can check data or node types only for gc, since we allocate different type of data/node blocks in a different logs occasionally. Signed-off-by: Jaegeuk Kim --- fs/f2fs/gc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c

[PATCH 1/2] f2fs: check only data or node for summary

We can check data or node types only for gc, since we allocate different type of data/node blocks in a different logs occasionally. Signed-off-by: Jaegeuk Kim --- fs/f2fs/gc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index

Re: [PATCH] nfsd: Close a race between access checking/setting in nfs4_get_vfs_file

On Fri, Jun 10, 2016 at 06:50:33AM -0400, Jeff Layton wrote: > On Fri, 2016-06-10 at 00:18 -0400, Oleg Drokin wrote: > > On Jun 9, 2016, at 5:01 PM, Oleg Drokin wrote: > > > > > Currently there's an unprotected access mode check in > > > nfs4_upgrade_open > > > that then calls nfs4_get_vfs_file

Re: [PATCH] nfsd: Close a race between access checking/setting in nfs4_get_vfs_file

On Fri, Jun 10, 2016 at 06:50:33AM -0400, Jeff Layton wrote: > On Fri, 2016-06-10 at 00:18 -0400, Oleg Drokin wrote: > > On Jun 9, 2016, at 5:01 PM, Oleg Drokin wrote: > > > > > Currently there's an unprotected access mode check in > > > nfs4_upgrade_open > > > that then calls nfs4_get_vfs_file

Re: [PATCH V9 10/11] ARM64/PCI: Implement ACPI low-level calls to access PCI_Config region from AML

On Fri, Jun 10, 2016 at 09:55:18PM +0200, Tomasz Nowicki wrote: > ACPI spec6.1 - chapter: 5.5.2.4 defines OperationRegion (Declare Operation > Region). Following the spec: " [...] An Operation Region is a specific > region of operation within an address space that is declared as a subset > of the

Re: [PATCH V9 10/11] ARM64/PCI: Implement ACPI low-level calls to access PCI_Config region from AML

On Fri, Jun 10, 2016 at 09:55:18PM +0200, Tomasz Nowicki wrote: > ACPI spec6.1 - chapter: 5.5.2.4 defines OperationRegion (Declare Operation > Region). Following the spec: " [...] An Operation Region is a specific > region of operation within an address space that is declared as a subset > of the

Re: [PATCH 1/2] rxrpc: Trim line-terminal whitespace [ver #2]

David Miller wrote: > There is a clear, documented, way to do this properly with your > patches themselves. Put it in the Subject line: > > Subject: "[PATCH net-next 1/2] rxrpc: ..." Hmmm... so there is. I don't remember seeing the netdev-FAQ appear. I wonder how

Re: [PATCH 1/2] rxrpc: Trim line-terminal whitespace [ver #2]

David Miller wrote: > There is a clear, documented, way to do this properly with your > patches themselves. Put it in the Subject line: > > Subject: "[PATCH net-next 1/2] rxrpc: ..." Hmmm... so there is. I don't remember seeing the netdev-FAQ appear. I wonder how to make stgit do

Re: [PATCH] phy: marvell: remove LED config override

Hi Andrew, On Fri, Jun 10, 2016 at 08:38:57PM +0200, Andrew Lunn wrote: > On Fri, Jun 10, 2016 at 07:42:52PM +0200, Clemens Gruber wrote: > > Configuring the PHY LED registers for the Marvell 88E1510 and others is > > not possible, because regardless of the values in marvell,reg-init, it > > is

Re: [PATCH] phy: marvell: remove LED config override

Hi Andrew, On Fri, Jun 10, 2016 at 08:38:57PM +0200, Andrew Lunn wrote: > On Fri, Jun 10, 2016 at 07:42:52PM +0200, Clemens Gruber wrote: > > Configuring the PHY LED registers for the Marvell 88E1510 and others is > > not possible, because regardless of the values in marvell,reg-init, it > > is

Re: [PATCH V9 07/11] PCI: Factor DT specific pci_bus_find_domain_nr() code out

On Fri, Jun 10, 2016 at 09:55:15PM +0200, Tomasz Nowicki wrote: > pci_bus_find_domain_nr() retrieves the host bridge domain number in a DT > specific way. Factor our pci_bus_find_domain_nr() in a separate DT s/our/out > function (ie of_pci_bus_find_domain_nr()) so that DT code is self >

Re: [PATCH V9 07/11] PCI: Factor DT specific pci_bus_find_domain_nr() code out

On Fri, Jun 10, 2016 at 09:55:15PM +0200, Tomasz Nowicki wrote: > pci_bus_find_domain_nr() retrieves the host bridge domain number in a DT > specific way. Factor our pci_bus_find_domain_nr() in a separate DT s/our/out > function (ie of_pci_bus_find_domain_nr()) so that DT code is self >

Re: [PATCH V9 06/11] PCI: Refactor generic bus domain assignment

On Fri, Jun 10, 2016 at 09:55:14PM +0200, Tomasz Nowicki wrote: > Change the way PCI bus domain number is assigned and improve function > name to reflect what function does. No functional changes. > > Instead of assigning bus domain number inside of pci_bus_assign_domain_nr() > simply return

Re: [PATCH V9 06/11] PCI: Refactor generic bus domain assignment

On Fri, Jun 10, 2016 at 09:55:14PM +0200, Tomasz Nowicki wrote: > Change the way PCI bus domain number is assigned and improve function > name to reflect what function does. No functional changes. > > Instead of assigning bus domain number inside of pci_bus_assign_domain_nr() > simply return

Re: [PATCH v3] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

On Wed, Jun 1, 2016 at 10:14 PM, Vinay Simha BN wrote: > Add support for the JDI lt070me05000 WUXGA DSI panel used in > Nexus 7 2013 devices. Sorry for the late comment. [...] > +static const struct drm_display_mode default_mode = { > + .clock = 155493, > +

Re: [PATCH v3] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

On Wed, Jun 1, 2016 at 10:14 PM, Vinay Simha BN wrote: > Add support for the JDI lt070me05000 WUXGA DSI panel used in > Nexus 7 2013 devices. Sorry for the late comment. [...] > +static const struct drm_display_mode default_mode = { > + .clock = 155493, > +

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:23:47PM +0200, Luis R. Rodriguez wrote: > On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote: > > On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > > > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > > > The

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:23:47PM +0200, Luis R. Rodriguez wrote: > On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote: > > On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > > > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > > > The

[PATCH 0/4] scripts/coccicheck: add paramap and indexing options

coccicheck hasn't been updated for a while. The backports project has been using some features for a while now that we should be able to also take advantage of with coccicheck, the most important one is paramap support. glimpseindex stuff wasn't even building but today I decided to go tackle and

[PATCH 3/4] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12

[PATCH 1/4] coccicheck: move spatch binary check up

This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez --- scripts/coccicheck | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH 4/4] coccicheck: add indexing enhancement options

Enable indexing optimizations heuristics. Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code 'coccigrep', in practice though this seems to not perform better than regular grep however its expected to help with some use cases so

[PATCH 0/4] scripts/coccicheck: add paramap and indexing options

coccicheck hasn't been updated for a while. The backports project has been using some features for a while now that we should be able to also take advantage of with coccicheck, the most important one is paramap support. glimpseindex stuff wasn't even building but today I decided to go tackle and

[PATCH 3/4] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12 insertions(+) create mode

[PATCH 1/4] coccicheck: move spatch binary check up

This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez --- scripts/coccicheck | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 4/4] coccicheck: add indexing enhancement options

Enable indexing optimizations heuristics. Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code 'coccigrep', in practice though this seems to not perform better than regular grep however its expected to help with some use cases so

[PATCH 2/4] coccicheck: enable paramap support

Coccinelle has had paramap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that

[PATCH 2/4] coccicheck: enable paramap support

Coccinelle has had paramap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that

Re: [PATCH v2 00/38] Documentation/sphinx

On 11 June 2016 at 04:17, Daniel Vetter wrote: > On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote: >> On Sat, 4 Jun 2016 14:37:01 +0300 >> Jani Nikula wrote: >> >>> When this lands in docs-next and we can backmerge to drm,

Re: [PATCH v2 00/38] Documentation/sphinx

On 11 June 2016 at 04:17, Daniel Vetter wrote: > On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote: >> On Sat, 4 Jun 2016 14:37:01 +0300 >> Jani Nikula wrote: >> >>> When this lands in docs-next and we can backmerge to drm, we'll plunge >>> ahead and convert gpu.tmpl to rst, and have that

Re: [GIT PULL] Ceph updates for 4.7-rc1

On Thursday, May 26, 2016 2:18:03 PM CEST Sage Weil wrote: > Hi Linus, > > Please pull the following Ceph updates from > > git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus > > This changeset has a few main parts: > > * Ilya has finished a huge refactoring effort

Re: [GIT PULL] Ceph updates for 4.7-rc1

On Thursday, May 26, 2016 2:18:03 PM CEST Sage Weil wrote: > Hi Linus, > > Please pull the following Ceph updates from > > git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus > > This changeset has a few main parts: > > * Ilya has finished a huge refactoring effort

acpi: broken suspend to RAM with v4.7-rc1

Hi, On my laptop (DELL Vostro 1500) in v4.7-rc1 is broken suspend to RAM. Laptop doesn't finish suspend to RAM process (disks are off, but WiFi and Power LEDs are still on). The only way to get it out of this state, is to turn the power off. I've bisected the issue to commit 66b1ed5aa8dd25

acpi: broken suspend to RAM with v4.7-rc1

Hi, On my laptop (DELL Vostro 1500) in v4.7-rc1 is broken suspend to RAM. Laptop doesn't finish suspend to RAM process (disks are off, but WiFi and Power LEDs are still on). The only way to get it out of this state, is to turn the power off. I've bisected the issue to commit 66b1ed5aa8dd25

Re: [PATCH net-next 8/8] net: dsa: mv88e6xxx: fail on mismatching probe

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:56PM -0400, Vivien Didelot wrote: >> Now that we have access at probe time to the chip info described in the >> device tree, check if the probed device matches the device node, >> otherwise warn the user and fail. > > What

Re: [PATCH net-next 8/8] net: dsa: mv88e6xxx: fail on mismatching probe

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:56PM -0400, Vivien Didelot wrote: >> Now that we have access at probe time to the chip info described in the >> device tree, check if the probed device matches the device node, >> otherwise warn the user and fail. > > What good is this? So

Re: [PATCH net-next 7/8] net: dsa: mv88e6xxx: explicit compatible devices

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:55PM -0400, Vivien Didelot wrote: >> Thanks to the new device probing, we can explicit the exact switch model >> in the device tree. >> >> Name the driver "mv88e6xxx" and list all its compatible supported chips. > > No.

Re: [PATCH net-next 7/8] net: dsa: mv88e6xxx: explicit compatible devices

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:55PM -0400, Vivien Didelot wrote: >> Thanks to the new device probing, we can explicit the exact switch model >> in the device tree. >> >> Name the driver "mv88e6xxx" and list all its compatible supported chips. > > No. This goes against

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote: > On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > > The dma-mapping core and the implementations do not change the > > > DMA

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:16:00PM +0200, Krzysztof Kozlowski wrote: > On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > > The dma-mapping core and the implementations do not change the > > > DMA

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > The dma-mapping core and the implementations do not change the > > DMA attributes passed by pointer. Thus the pointer can point to const > > data. However

Re: [PATCH v4 01/44] dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 04:49:47PM +0200, Luis R. Rodriguez wrote: > On Fri, Jun 10, 2016 at 12:11:18PM +0200, Krzysztof Kozlowski wrote: > > The dma-mapping core and the implementations do not change the > > DMA attributes passed by pointer. Thus the pointer can point to const > > data. However

Re: [PATCH 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)

On Fri, Jun 10, 2016 at 1:07 PM, Oleg Nesterov wrote: > On 06/09, Andy Lutomirski wrote: >> >> On Jun 6, 2016 3:21 PM, "Oleg Nesterov" wrote: >> > >> > On 06/01, Dmitry Safonov wrote: >> > > >> > > Note, that this will work only if application has changed it's

Re: [PATCH 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)

On Fri, Jun 10, 2016 at 1:07 PM, Oleg Nesterov wrote: > On 06/09, Andy Lutomirski wrote: >> >> On Jun 6, 2016 3:21 PM, "Oleg Nesterov" wrote: >> > >> > On 06/01, Dmitry Safonov wrote: >> > > >> > > Note, that this will work only if application has changed it's CS. >> > >> > So, suppose it

[PATCH] staging: lustre: o2iblnd: remove typedefs

Remove all remaining typedefs in o2iblnd driver. Signed-off-by: James Simmons --- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c| 339 +- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h| 299

[PATCH] staging: lustre: o2iblnd: remove typedefs

Remove all remaining typedefs in o2iblnd driver. Signed-off-by: James Simmons --- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c| 339 +- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h| 299 .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 368

[PATCH] staging: lustre: socklnd: remove typedefs

Remove all remaining typedefs in socklnd driver. Signed-off-by: James Simmons --- .../staging/lustre/lnet/klnds/socklnd/socklnd.c| 302 ++-- .../staging/lustre/lnet/klnds/socklnd/socklnd.h| 209 +++---

[PATCH] staging: lustre: socklnd: remove typedefs

Remove all remaining typedefs in socklnd driver. Signed-off-by: James Simmons --- .../staging/lustre/lnet/klnds/socklnd/socklnd.c| 302 ++-- .../staging/lustre/lnet/klnds/socklnd/socklnd.h| 209 +++--- .../staging/lustre/lnet/klnds/socklnd/socklnd_cb.c | 200

[NAK] [PATCH v4 00/29] Fixed issues raised by tglx, then move visorbus to drivers/virt

> -Original Message- > From: David Kershner [mailto:david.kersh...@unisys.com] > Sent: Wednesday, June 8, 2016 5:14 PM > To: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com; > h...@zytor.com; Kershner, David A ; > gre...@linuxfoundation.org; Arfvidson, Erik

[NAK] [PATCH v4 00/29] Fixed issues raised by tglx, then move visorbus to drivers/virt

> -Original Message- > From: David Kershner [mailto:david.kersh...@unisys.com] > Sent: Wednesday, June 8, 2016 5:14 PM > To: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com; > h...@zytor.com; Kershner, David A ; > gre...@linuxfoundation.org; Arfvidson, Erik ; > Sell, Timothy C ;

Re: [tip:x86/urgent] x86/quirks: Add early quirk to reset Apple AirPort card

[+cc Matthew, Doug] On Fri, Jun 10, 2016 at 03:59:04PM +0200, Lukas Wunner wrote: > On Fri, Jun 10, 2016 at 02:59:57PM +0200, Ingo Molnar wrote: > > * Lukas Wunner wrote: > > > On Fri, Jun 10, 2016 at 01:58:45PM +0200, Ingo Molnar wrote: > > > > * Yinghai Lu

Re: [PATCH 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)

On 06/09, Andy Lutomirski wrote: > > On Jun 6, 2016 3:21 PM, "Oleg Nesterov" wrote: > > > > On 06/01, Dmitry Safonov wrote: > > > > > > Note, that this will work only if application has changed it's CS. > > > > So, suppose it changes it's CS and crashes, > > > > > If the

Re: [tip:x86/urgent] x86/quirks: Add early quirk to reset Apple AirPort card

[+cc Matthew, Doug] On Fri, Jun 10, 2016 at 03:59:04PM +0200, Lukas Wunner wrote: > On Fri, Jun 10, 2016 at 02:59:57PM +0200, Ingo Molnar wrote: > > * Lukas Wunner wrote: > > > On Fri, Jun 10, 2016 at 01:58:45PM +0200, Ingo Molnar wrote: > > > > * Yinghai Lu wrote: > > > > > On 6/9/16, Lukas

Re: [PATCH 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)

On 06/09, Andy Lutomirski wrote: > > On Jun 6, 2016 3:21 PM, "Oleg Nesterov" wrote: > > > > On 06/01, Dmitry Safonov wrote: > > > > > > Note, that this will work only if application has changed it's CS. > > > > So, suppose it changes it's CS and crashes, > > > > > If the application does 32-bit

Re: [PATCH net-next 4/8] net: dsa: mv88e6xxx: do not increment bus refcount

On Fri, Jun 10, 2016 at 03:59:22PM -0400, Vivien Didelot wrote: > Hi, > > Andrew Lunn writes: > > > On Wed, Jun 08, 2016 at 08:44:52PM -0400, Vivien Didelot wrote: > >> The MDIO device probe and remove functions are respectively incrementing > >> and decrementing the bus

Re: [PATCH net-next 4/8] net: dsa: mv88e6xxx: do not increment bus refcount

On Fri, Jun 10, 2016 at 03:59:22PM -0400, Vivien Didelot wrote: > Hi, > > Andrew Lunn writes: > > > On Wed, Jun 08, 2016 at 08:44:52PM -0400, Vivien Didelot wrote: > >> The MDIO device probe and remove functions are respectively incrementing > >> and decrementing the bus refcount themselves.

Re: [PATCH v4 39/44] sparc: dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:43:47AM -0700, David Miller wrote: > From: Krzysztof Kozlowski > Date: Fri, 10 Jun 2016 12:11:56 +0200 > > > Split out subsystem specific changes for easier reviews. This will be > > squashed with main commit. > > > > Signed-off-by: Krzysztof

Re: [PATCH v4 39/44] sparc: dma-mapping: Use unsigned long for dma_attrs

On Fri, Jun 10, 2016 at 10:43:47AM -0700, David Miller wrote: > From: Krzysztof Kozlowski > Date: Fri, 10 Jun 2016 12:11:56 +0200 > > > Split out subsystem specific changes for easier reviews. This will be > > squashed with main commit. > > > > Signed-off-by: Krzysztof Kozlowski > > If you

[GIT PULL] Btrfs

Hi Linus My for-linus-4.7 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 Has some fixes and some new self tests for btrfs. The self tests are usually disabled in the .config file (unless you're doing btrfs dev work), and this bunch is meant to find

[GIT PULL] Btrfs

Hi Linus My for-linus-4.7 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 Has some fixes and some new self tests for btrfs. The self tests are usually disabled in the .config file (unless you're doing btrfs dev work), and this bunch is meant to find

Re: [PATCH net-next 4/8] net: dsa: mv88e6xxx: do not increment bus refcount

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:52PM -0400, Vivien Didelot wrote: >> The MDIO device probe and remove functions are respectively incrementing >> and decrementing the bus refcount themselves. Since these bus level >> actions are out of the device scope,

Re: [PATCH net-next 4/8] net: dsa: mv88e6xxx: do not increment bus refcount

Hi, Andrew Lunn writes: > On Wed, Jun 08, 2016 at 08:44:52PM -0400, Vivien Didelot wrote: >> The MDIO device probe and remove functions are respectively incrementing >> and decrementing the bus refcount themselves. Since these bus level >> actions are out of the device scope, remove them. > > I

[PATCH V9 03/11] PCI: Add new function to unmap IO resources

From: Sinan Kaya We need to release I/O resources so that the same I/O resources can be allocated again in pci_remap_iospace(), like in PCI hotplug removal scenario. Therefore implement new pci_unmap_iospace() call which unmaps I/O space as the symmetry to

[PATCH V9 03/11] PCI: Add new function to unmap IO resources

From: Sinan Kaya We need to release I/O resources so that the same I/O resources can be allocated again in pci_remap_iospace(), like in PCI hotplug removal scenario. Therefore implement new pci_unmap_iospace() call which unmaps I/O space as the symmetry to pci_remap_iospace(). Signed-off-by:

[PATCH V9 04/11] ACPI/PCI: Support IO resources when parsing PCI host bridge resources

From: Jayachandran C Platforms that have memory mapped IO port (such as ARM64) need special handling for PCI I/O resources. For host bridge's resource probing case these resources need to be fixed up with pci_register_io_range()/pci_remap_iospace() etc. The same I/O

[PATCH V9 04/11] ACPI/PCI: Support IO resources when parsing PCI host bridge resources

From: Jayachandran C Platforms that have memory mapped IO port (such as ARM64) need special handling for PCI I/O resources. For host bridge's resource probing case these resources need to be fixed up with pci_register_io_range()/pci_remap_iospace() etc. The same I/O resources need to be

[PATCH V9 06/11] PCI: Refactor generic bus domain assignment

Change the way PCI bus domain number is assigned and improve function name to reflect what function does. No functional changes. Instead of assigning bus domain number inside of pci_bus_assign_domain_nr() simply return domain number and let pci_create_root_bus() do assignment. This way

[PATCH V9 06/11] PCI: Refactor generic bus domain assignment

Change the way PCI bus domain number is assigned and improve function name to reflect what function does. No functional changes. Instead of assigning bus domain number inside of pci_bus_assign_domain_nr() simply return domain number and let pci_create_root_bus() do assignment. This way

[PATCH V9 02/11] PCI/ECAM: Add parent device field to pci_config_window

From: Jayachandran C Add a parent device field to struct pci_config_window. The parent is not saved now, but will be useful to save it in some cases. Specifically in case of ACPI for ARM64, it can be used to setup ACPI companion and domain. Since the parent dev is in

[PATCH V9 02/11] PCI/ECAM: Add parent device field to pci_config_window

From: Jayachandran C Add a parent device field to struct pci_config_window. The parent is not saved now, but will be useful to save it in some cases. Specifically in case of ACPI for ARM64, it can be used to setup ACPI companion and domain. Since the parent dev is in struct pci_config_window

[PATCH V9 07/11] PCI: Factor DT specific pci_bus_find_domain_nr() code out

pci_bus_find_domain_nr() retrieves the host bridge domain number in a DT specific way. Factor our pci_bus_find_domain_nr() in a separate DT function (ie of_pci_bus_find_domain_nr()) so that DT code is self contained, paving the way for retrieving domain number in pci_bus_find_domain_nr() with

[PATCH V9 07/11] PCI: Factor DT specific pci_bus_find_domain_nr() code out

pci_bus_find_domain_nr() retrieves the host bridge domain number in a DT specific way. Factor our pci_bus_find_domain_nr() in a separate DT function (ie of_pci_bus_find_domain_nr()) so that DT code is self contained, paving the way for retrieving domain number in pci_bus_find_domain_nr() with

[PATCH V9 10/11] ARM64/PCI: Implement ACPI low-level calls to access PCI_Config region from AML

ACPI spec6.1 - chapter: 5.5.2.4 defines OperationRegion (Declare Operation Region). Following the spec: " [...] An Operation Region is a specific region of operation within an address space that is declared as a subset of the entire address space using a starting address (offset) and a length.

[PATCH V9 09/11] ARM64/PCI: ACPI support for legacy IRQs parsing and consolidation with DT code

To enable PCI legacy IRQs on platforms booting with ACPI, arch code should include ACPI specific callbacks that parse and set-up the device IRQ number, equivalent to the DT boot path. Owing to the current ACPI core scan handlers implementation, ACPI PCI legacy IRQs bindings cannot be parsed at

[PATCH V9 05/11] ACPI/PCI: Add generic MCFG table handling

According to PCI firmware specifications, on systems booting with ACPI, PCI configuration for a host bridge must be set-up through the MCFG table regions for non-hotpluggable bridges and _CBA method for hotpluggable ones. Current MCFG table handling code, as implemented for x86, cannot be easily

[PATCH V9 10/11] ARM64/PCI: Implement ACPI low-level calls to access PCI_Config region from AML

ACPI spec6.1 - chapter: 5.5.2.4 defines OperationRegion (Declare Operation Region). Following the spec: " [...] An Operation Region is a specific region of operation within an address space that is declared as a subset of the entire address space using a starting address (offset) and a length.

[PATCH V9 09/11] ARM64/PCI: ACPI support for legacy IRQs parsing and consolidation with DT code

To enable PCI legacy IRQs on platforms booting with ACPI, arch code should include ACPI specific callbacks that parse and set-up the device IRQ number, equivalent to the DT boot path. Owing to the current ACPI core scan handlers implementation, ACPI PCI legacy IRQs bindings cannot be parsed at

[PATCH V9 05/11] ACPI/PCI: Add generic MCFG table handling

According to PCI firmware specifications, on systems booting with ACPI, PCI configuration for a host bridge must be set-up through the MCFG table regions for non-hotpluggable bridges and _CBA method for hotpluggable ones. Current MCFG table handling code, as implemented for x86, cannot be easily

[PATCH V9 08/11] ARM64/PCI: Add ACPI hook to assign domain number

PCI core code provides a config option (CONFIG_PCI_DOMAINS_GENERIC) that allows assigning the PCI bus domain number generically by relying on device tree bindings, and falling back to a simple counter when the respective DT properties (ie "linux,pci-domain") are not specified in the host bridge

[PATCH V9 08/11] ARM64/PCI: Add ACPI hook to assign domain number

PCI core code provides a config option (CONFIG_PCI_DOMAINS_GENERIC) that allows assigning the PCI bus domain number generically by relying on device tree bindings, and falling back to a simple counter when the respective DT properties (ie "linux,pci-domain") are not specified in the host bridge

[PATCH V9 11/11] ARM64/PCI: Support for ACPI based PCI host controller

Implement pci_acpi_scan_root and other arch-specific call so that ARM64 can start using ACPI to setup and enumerate PCI buses. Prior to buses enumeration the pci_acpi_scan_root() implementation looks for configuration space start address (obtained through ACPI _CBA method or MCFG interface). If

[PATCH V9 11/11] ARM64/PCI: Support for ACPI based PCI host controller

Implement pci_acpi_scan_root and other arch-specific call so that ARM64 can start using ACPI to setup and enumerate PCI buses. Prior to buses enumeration the pci_acpi_scan_root() implementation looks for configuration space start address (obtained through ACPI _CBA method or MCFG interface). If

[PATCH V9 01/11] PCI/ECAM: Move ecam.h to linux/include/pci-ecam.h

From: Jayachandran C This header will be used from arch/arm64 for ACPI PCI implementation so it needs to be moved out of drivers/pci. Update users of the header file to use the new name. No functional changes. Signed-off-by: Jayachandran C

[PATCH V9 01/11] PCI/ECAM: Move ecam.h to linux/include/pci-ecam.h

From: Jayachandran C This header will be used from arch/arm64 for ACPI PCI implementation so it needs to be moved out of drivers/pci. Update users of the header file to use the new name. No functional changes. Signed-off-by: Jayachandran C Acked-by: Lorenzo Pieralisi --- drivers/pci/ecam.c

[PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

>From the functionality point of view this series may be split into the following logic parts: 1. Export ECAM API and add parent device to pci_config_window 2. Add IO resources handling to PCI core code 3. New MCFG driver 4. Cleanups and support for generic domain assignment based on ACPI 5.

[PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

>From the functionality point of view this series may be split into the following logic parts: 1. Export ECAM API and add parent device to pci_config_window 2. Add IO resources handling to PCI core code 3. New MCFG driver 4. Cleanups and support for generic domain assignment based on ACPI 5.

Re: [PATCH v2 2/3] mwifiex: move .get_tx_power logic to station ioctl file

Javier Martinez Canillas writes: >> This patch (2/3) is only for code rearrangement and adds an >> unnecessary wrapper function. We can simply drop the patch. > > Agreed. > > Kalle, > > Patch 3/3 applies cleanly even after dropping patch 2/3. > Is that Ok for you or do

Re: [PATCH v2 2/3] mwifiex: move .get_tx_power logic to station ioctl file

Javier Martinez Canillas writes: >> This patch (2/3) is only for code rearrangement and adds an >> unnecessary wrapper function. We can simply drop the patch. > > Agreed. > > Kalle, > > Patch 3/3 applies cleanly even after dropping patch 2/3. > Is that Ok for you or do you want me to re-resend a

Re: [PATCH v2 1/2] dt-bindings: add Starry KR122EA0SRA panel binding

Rob, On Fri, Jun 10, 2016 at 11:43 AM, Rob Clark wrote: > On Fri, Jun 10, 2016 at 1:02 PM, Douglas Anderson > wrote: >> The Starry KR122EA0SRA is a 12.2", 1920x1200 TFT-LCD panel connected >> using eDP interfaces. > > so drive-by comment... but

Re: [PATCH v4 16/44] infiniband: dma-mapping: Use unsigned long for dma_attrs

On 06/10/2016 03:11 AM, Krzysztof Kozlowski wrote: Split out subsystem specific changes for easier reviews. This will be squashed with main commit. Please rename 'attrs' into 'dma_attrs' in this patch such that it remains clear that that variable refers to DMA attributes. Thanks, Bart.

Re: [PATCH v2 1/2] dt-bindings: add Starry KR122EA0SRA panel binding

Rob, On Fri, Jun 10, 2016 at 11:43 AM, Rob Clark wrote: > On Fri, Jun 10, 2016 at 1:02 PM, Douglas Anderson > wrote: >> The Starry KR122EA0SRA is a 12.2", 1920x1200 TFT-LCD panel connected >> using eDP interfaces. > > so drive-by comment... but shouldn't eDP be probe-able? Not sure why > we

Re: [PATCH v4 16/44] infiniband: dma-mapping: Use unsigned long for dma_attrs

On 06/10/2016 03:11 AM, Krzysztof Kozlowski wrote: Split out subsystem specific changes for easier reviews. This will be squashed with main commit. Please rename 'attrs' into 'dma_attrs' in this patch such that it remains clear that that variable refers to DMA attributes. Thanks, Bart.

[tip:irq/core] genirq: Remove unnecessary memset() calls

Commit-ID: ff5b706f5189fe8d2a6fd576b491b769ec1d29d3 Gitweb: http://git.kernel.org/tip/ff5b706f5189fe8d2a6fd576b491b769ec1d29d3 Author: Weongyo Jeong AuthorDate: Thu, 31 Mar 2016 12:15:03 -0700 Committer: Thomas Gleixner CommitDate: Fri, 10

[tip:irq/core] genirq: Remove unnecessary memset() calls

Commit-ID: ff5b706f5189fe8d2a6fd576b491b769ec1d29d3 Gitweb: http://git.kernel.org/tip/ff5b706f5189fe8d2a6fd576b491b769ec1d29d3 Author: Weongyo Jeong AuthorDate: Thu, 31 Mar 2016 12:15:03 -0700 Committer: Thomas Gleixner CommitDate: Fri, 10 Jun 2016 17:07:50 +0200 genirq: Remove

[tip:irq/core] genirq: Remove redundant NULL check of irq_desc

Commit-ID: fe3464ca8710012a247bb4586dde21b080f88514 Gitweb: http://git.kernel.org/tip/fe3464ca8710012a247bb4586dde21b080f88514 Author: Jianyu Zhan AuthorDate: Sat, 19 Mar 2016 21:59:19 +0800 Committer: Thomas Gleixner CommitDate: Fri, 10 Jun 2016

[tip:irq/core] genirq: Remove redundant NULL check of irq_desc

Commit-ID: fe3464ca8710012a247bb4586dde21b080f88514 Gitweb: http://git.kernel.org/tip/fe3464ca8710012a247bb4586dde21b080f88514 Author: Jianyu Zhan AuthorDate: Sat, 19 Mar 2016 21:59:19 +0800 Committer: Thomas Gleixner CommitDate: Fri, 10 Jun 2016 17:07:49 +0200 genirq: Remove

[PATCH net-next,v2] tools: hv: Add a script to help bonding synthetic and VF NICs

This script helps to create bonding network devices based on synthetic NIC (the virtual network adapter usually provided by Hyper-V) and the matching VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can function as one network device, and fail over to the synthetic NIC if VF is

[PATCH net-next,v2] tools: hv: Add a script to help bonding synthetic and VF NICs

This script helps to create bonding network devices based on synthetic NIC (the virtual network adapter usually provided by Hyper-V) and the matching VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can function as one network device, and fail over to the synthetic NIC if VF is

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