[PATCH v3 05/59] irqchip/gic-v3-its: Add probing for VLPI properties

Add the probing code for the ITS VLPI support. This includes configuring the ITS number if not supporting the single VMOVP command feature. Reviewed-by: Eric Auger Signed-off-by: Marc Zyngier --- drivers/irqchip/irq-gic-v3-its.c | 71

[PATCH v3 05/59] irqchip/gic-v3-its: Add probing for VLPI properties

Add the probing code for the ITS VLPI support. This includes configuring the ITS number if not supporting the single VMOVP command feature. Reviewed-by: Eric Auger Signed-off-by: Marc Zyngier --- drivers/irqchip/irq-gic-v3-its.c | 71 +++---

[PATCH v3 04/59] irqchip/gic-v3-its: Move LPI definitions around

The various LPI definitions are in the middle of the code, and would be better placed at the beginning, given that we're going to use some of them much earlier. Reviewed-by: Thomas Gleixner Reviewed-by: Eric Auger Signed-off-by: Marc Zyngier

[PATCH v3 04/59] irqchip/gic-v3-its: Move LPI definitions around

The various LPI definitions are in the middle of the code, and would be better placed at the beginning, given that we're going to use some of them much earlier. Reviewed-by: Thomas Gleixner Reviewed-by: Eric Auger Signed-off-by: Marc Zyngier --- drivers/irqchip/irq-gic-v3-its.c | 25

Re: [PATCH] fbcon: Use background color for margins

On 07/30/2017 04:51 PM, Pavel Machek wrote: Hi! Screens that don't have a black border around the active area will have ugly black bars for the margin when the text background color is not black. This is especially noticeable on an LCD screen (not the backlit kind) when the terminal colors are

Re: [PATCH] fbcon: Use background color for margins

On 07/30/2017 04:51 PM, Pavel Machek wrote: Hi! Screens that don't have a black border around the active area will have ugly black bars for the margin when the text background color is not black. This is especially noticeable on an LCD screen (not the backlit kind) when the terminal colors are

[PATCH] osq_lock: fix osq_lock queue corruption

Fix ordering of link creation between node->prev and prev->next in osq_lock(). A case in which the status of optimistic spin queue is CPU6->CPU2 in which CPU6 has acquired the lock. tail v ,-. <- ,-. |6||2| `-' -> `-' At this point if CPU0 comes in to acquire

[PATCH] osq_lock: fix osq_lock queue corruption

Fix ordering of link creation between node->prev and prev->next in osq_lock(). A case in which the status of optimistic spin queue is CPU6->CPU2 in which CPU6 has acquired the lock. tail v ,-. <- ,-. |6||2| `-' -> `-' At this point if CPU0 comes in to acquire

Re: wake_wide mechanism clarification

On Mon, 2017-07-31 at 14:48 +, Josef Bacik wrote: > On Mon, Jul 31, 2017 at 03:42:25PM +0200, Mike Galbraith wrote: > > On Mon, 2017-07-31 at 12:21 +, Josef Bacik wrote: > > > > > > I've been working in this area recently because of a cpu imbalance > > > problem. > > > Wake_wide()

Re: wake_wide mechanism clarification

On Mon, 2017-07-31 at 14:48 +, Josef Bacik wrote: > On Mon, Jul 31, 2017 at 03:42:25PM +0200, Mike Galbraith wrote: > > On Mon, 2017-07-31 at 12:21 +, Josef Bacik wrote: > > > > > > I've been working in this area recently because of a cpu imbalance > > > problem. > > > Wake_wide()

Re: [PATCH v1 3/6] staging: unisys: Switch to use new generic UUID API

On Sun, 2017-07-30 at 10:37 -0700, Greg Kroah-Hartman wrote: > On Sun, Jul 30, 2017 at 08:26:48PM +0300, Andy Shevchenko wrote: > > On Sun, Jul 30, 2017 at 6:32 PM, Greg Kroah-Hartman > > wrote: > > > Doesn't apply to the staging tree at all :( > > > > No surprises,

Re: [PATCH v1 3/6] staging: unisys: Switch to use new generic UUID API

On Sun, 2017-07-30 at 10:37 -0700, Greg Kroah-Hartman wrote: > On Sun, Jul 30, 2017 at 08:26:48PM +0300, Andy Shevchenko wrote: > > On Sun, Jul 30, 2017 at 6:32 PM, Greg Kroah-Hartman > > wrote: > > > Doesn't apply to the staging tree at all :( > > > > No surprises, it was cooked against uuid

Re: [PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6

On Fri, Jul 28, 2017 at 01:10:03PM +0200, Michal Hocko wrote: > I haven't seen a newer version posted but the same comment applies on > your hmm-v25-4.9 git version from > git://people.freedesktop.org/~glisse/linux > > On Wed 28-06-17 14:00:41, Jérôme Glisse wrote: > > This introduce a simple

Re: [PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6

On Fri, Jul 28, 2017 at 01:10:03PM +0200, Michal Hocko wrote: > I haven't seen a newer version posted but the same comment applies on > your hmm-v25-4.9 git version from > git://people.freedesktop.org/~glisse/linux > > On Wed 28-06-17 14:00:41, Jérôme Glisse wrote: > > This introduce a simple

[PATCH v2] staging: unisys: Switch to use new generic UUID API

There are new types and helpers that are supposed to be used in new code. As a preparation to get rid of legacy types and API functions do the conversion here. While here, re-indent couple of lines to increase readability. Cc: David Kershner Cc: Greg Kroah-Hartman

[PATCH v2] staging: unisys: Switch to use new generic UUID API

There are new types and helpers that are supposed to be used in new code. As a preparation to get rid of legacy types and API functions do the conversion here. While here, re-indent couple of lines to increase readability. Cc: David Kershner Cc: Greg Kroah-Hartman Cc:

Re: [PATCH 4/4] clk: sunxi-ng: Wait for lock when using fractional mode

Hi Chen-Yu, Dne ponedeljek, 31. julij 2017 ob 07:02:18 CEST je Chen-Yu Tsai napisal(a): > On Mon, Jul 31, 2017 at 12:41 AM, Jernej Skrabec > > wrote: > > Currently ccu_frac_helper_set_rate() doesn't wait for a lock bit to be > > set before returning. Because of that,

Re: [PATCH 4/4] clk: sunxi-ng: Wait for lock when using fractional mode

Hi Chen-Yu, Dne ponedeljek, 31. julij 2017 ob 07:02:18 CEST je Chen-Yu Tsai napisal(a): > On Mon, Jul 31, 2017 at 12:41 AM, Jernej Skrabec > > wrote: > > Currently ccu_frac_helper_set_rate() doesn't wait for a lock bit to be > > set before returning. Because of that, unstable clock may be used.

Re: [PATCH 4/5] mtd: spi-nor: Add driver for Adaptrum Anarion QSPI controller

On 07/29/2017 02:34 AM, Marek Vasut wrote: On 07/29/2017 12:07 AM, Alexandru Gagniuc wrote: Add support for the QSPI controller found in Adaptrum Anarion SOCs. This controller is designed specifically to handle SPI NOR chips, and the driver is modeled as such. Because the system is emulated on

Re: [PATCH 4/5] mtd: spi-nor: Add driver for Adaptrum Anarion QSPI controller

On 07/29/2017 02:34 AM, Marek Vasut wrote: On 07/29/2017 12:07 AM, Alexandru Gagniuc wrote: Add support for the QSPI controller found in Adaptrum Anarion SOCs. This controller is designed specifically to handle SPI NOR chips, and the driver is modeled as such. Because the system is emulated on

Re: [PATCH v3 0/5] ARM64: disable irq between breakpoint and step exception

Hi Pratyush, On 31/07/17 11:40, Pratyush Anand wrote: > samples/hw_breakpoint/data_breakpoint.c passes with x86_64 but fails with > ARM64. Even though it has been NAKed previously on upstream [1, 2], I have > tried to come up with patches which can resolve it for ARM64 as well. > > I noticed

Re: [PATCH v3 0/5] ARM64: disable irq between breakpoint and step exception

Hi Pratyush, On 31/07/17 11:40, Pratyush Anand wrote: > samples/hw_breakpoint/data_breakpoint.c passes with x86_64 but fails with > ARM64. Even though it has been NAKed previously on upstream [1, 2], I have > tried to come up with patches which can resolve it for ARM64 as well. > > I noticed

Re: [tip:locking/urgent] locking/static_key: Fix concurrent static_key_slow_inc()

On Mon, Jul 31, 2017 at 6:33 AM, Peter Zijlstra wrote: > On Mon, Jul 31, 2017 at 03:04:06PM +0200, Paolo Bonzini wrote: >> - key->enabled cannot go from 0 to nonzero outside jump_label_mutex. >> For this reason the atomic_try_cmpxchg is unnecessary. > > Agreed, the only

Re: [tip:locking/urgent] locking/static_key: Fix concurrent static_key_slow_inc()

On Mon, Jul 31, 2017 at 6:33 AM, Peter Zijlstra wrote: > On Mon, Jul 31, 2017 at 03:04:06PM +0200, Paolo Bonzini wrote: >> - key->enabled cannot go from 0 to nonzero outside jump_label_mutex. >> For this reason the atomic_try_cmpxchg is unnecessary. > > Agreed, the only reason was the implied

Re: [PATCH 3/3] xfs: persist S_IOMAP_IMMUTABLE in di_flags2

On Sat, Jul 29, 2017 at 12:43:46PM -0700, Dan Williams wrote: > Record the immutable state in the on-disk inode so that on the next boot > the protections against reflink and hole punch etc are automatically > restored. > > This deliberately does not add a FS_XFLAG_IOMAP_IMMUTABLE since >

Re: [PATCH 3/3] xfs: persist S_IOMAP_IMMUTABLE in di_flags2

On Sat, Jul 29, 2017 at 12:43:46PM -0700, Dan Williams wrote: > Record the immutable state in the on-disk inode so that on the next boot > the protections against reflink and hole punch etc are automatically > restored. > > This deliberately does not add a FS_XFLAG_IOMAP_IMMUTABLE since >

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Mikael Pettersson writes: > Anatoly Pugachev writes: > > On Fri, Jul 28, 2017 at 11:45 AM, Mikael Pettersson > > wrote: > > > It's an rpmbuild --rebuild of Fedora's strace-4.18-1.fc24.src.rpm, but > according to the > > > build log the following should do it: >

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Mikael Pettersson writes: > Anatoly Pugachev writes: > > On Fri, Jul 28, 2017 at 11:45 AM, Mikael Pettersson > > wrote: > > > It's an rpmbuild --rebuild of Fedora's strace-4.18-1.fc24.src.rpm, but > according to the > > > build log the following should do it: > > > > > > export

Re: [PATCH] acpi: apei: clear error status before acknowledging the error

Hi Tyler, On 31/07/17 17:15, Baicar, Tyler wrote: > On 7/29/2017 12:53 AM, Borislav Petkov wrote: >> On Fri, Jul 28, 2017 at 04:25:03PM -0600, Tyler Baicar wrote: >>> Currently we acknowledge errors before clearing the error status. >>> This could cause a new error to be populated by firmware

Re: [PATCH] acpi: apei: clear error status before acknowledging the error

Hi Tyler, On 31/07/17 17:15, Baicar, Tyler wrote: > On 7/29/2017 12:53 AM, Borislav Petkov wrote: >> On Fri, Jul 28, 2017 at 04:25:03PM -0600, Tyler Baicar wrote: >>> Currently we acknowledge errors before clearing the error status. >>> This could cause a new error to be populated by firmware

Re: [PATCH 1/2] printk: Make CONFIG_PRINTK_TIME an int

On 07/25/2017 08:55 AM, Luis R. Rodriguez wrote: > On Tue, Jul 25, 2017 at 08:17:26AM -0400, Prarit Bhargava wrote: >> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c >> index fc47863f629c..26cf6cadd267 100644 >> --- a/kernel/printk/printk.c >> +++ b/kernel/printk/printk.c >> @@

Re: [PATCH 1/2] printk: Make CONFIG_PRINTK_TIME an int

On 07/25/2017 08:55 AM, Luis R. Rodriguez wrote: > On Tue, Jul 25, 2017 at 08:17:26AM -0400, Prarit Bhargava wrote: >> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c >> index fc47863f629c..26cf6cadd267 100644 >> --- a/kernel/printk/printk.c >> +++ b/kernel/printk/printk.c >> @@

Re: [PATCH 2/3] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Sat, Jul 29, 2017 at 12:43:40PM -0700, Dan Williams wrote: > >From falloc.h: > > FALLOC_FL_SEAL_BLOCK_MAP is used to seal (make immutable) all of the > file logical-to-physical extent offset mappings in the file. The > purpose is to allow an application to assume that there are no

Re: [PATCH 2/3] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Sat, Jul 29, 2017 at 12:43:40PM -0700, Dan Williams wrote: > >From falloc.h: > > FALLOC_FL_SEAL_BLOCK_MAP is used to seal (make immutable) all of the > file logical-to-physical extent offset mappings in the file. The > purpose is to allow an application to assume that there are no

Re: [PATCH] efifb: allow user to disable write combined mapping.

On Tuesday, July 25, 2017 10:56:15 AM Bartlomiej Zolnierkiewicz wrote: > On Tuesday, July 25, 2017 02:00:00 PM Dave Airlie wrote: > > On 19 July 2017 at 00:34, Peter Jones wrote: > > > On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote: > > >> This patch allows the

Re: [PATCH] efifb: allow user to disable write combined mapping.

On Tuesday, July 25, 2017 10:56:15 AM Bartlomiej Zolnierkiewicz wrote: > On Tuesday, July 25, 2017 02:00:00 PM Dave Airlie wrote: > > On 19 July 2017 at 00:34, Peter Jones wrote: > > > On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote: > > >> This patch allows the user to disable write

Re: [PATCH] hyperv: netvsc: Neaten netvsc_send_pkt by using a temporary

On Sun, 30 Jul 2017 14:19:30 -0700 Joe Perches wrote: > Repeated dereference of nvmsg.msg.v1_msg.send_rndis_pkt can be > shortened by using a temporary. Do so. > > No change in object code. > > Signed-off-by: Joe Perches Looks good, several other places

Re: [PATCH] hyperv: netvsc: Neaten netvsc_send_pkt by using a temporary

On Sun, 30 Jul 2017 14:19:30 -0700 Joe Perches wrote: > Repeated dereference of nvmsg.msg.v1_msg.send_rndis_pkt can be > shortened by using a temporary. Do so. > > No change in object code. > > Signed-off-by: Joe Perches Looks good, several other places also suffer from to

Re: [PATCH v2 2/4] can: fixed-transceiver: Add documentation for CAN fixed transceiver bindings

Hi Kurt, On 07/28/2017 09:41 PM, Kurt Van Dijck wrote: The transceiver is an analog device that needs to support faster switching frequency (FETs) including minimizing delay to support CAN-FD ie higher bitrate. From the transceiver perspective the bits for "arbitration" and "data" look exactly

Re: [PATCH v2 2/4] can: fixed-transceiver: Add documentation for CAN fixed transceiver bindings

Hi Kurt, On 07/28/2017 09:41 PM, Kurt Van Dijck wrote: The transceiver is an analog device that needs to support faster switching frequency (FETs) including minimizing delay to support CAN-FD ie higher bitrate. From the transceiver perspective the bits for "arbitration" and "data" look exactly

Re: [PATCH nf-next] netfilter: ipset: deduplicate prefixlen maps

On Thu, Jul 20, 2017 at 02:13:00PM -0400, Aaron Conole wrote: > The prefixlen maps used here are identical, and have been since > introduction. It seems to make sense to use a single large map, > that the preprocessor will fill appropriately. Applied, thanks.

Re: [PATCH nf-next] netfilter: ipset: deduplicate prefixlen maps

On Thu, Jul 20, 2017 at 02:13:00PM -0400, Aaron Conole wrote: > The prefixlen maps used here are identical, and have been since > introduction. It seems to make sense to use a single large map, > that the preprocessor will fill appropriately. Applied, thanks.

Re: [PATCH] acpi: apei: clear error status before acknowledging the error

On Mon, Jul 31, 2017 at 10:15:27AM -0600, Baicar, Tyler wrote: > I think the better thing to do in this case is still send the ack. If > ghes_read_estatus() fails, then > either we are unable to read the estatus or the estatus is empty/invalid. Right now we silently handle that failure of

Re: [PATCH] acpi: apei: clear error status before acknowledging the error

On Mon, Jul 31, 2017 at 10:15:27AM -0600, Baicar, Tyler wrote: > I think the better thing to do in this case is still send the ack. If > ghes_read_estatus() fails, then > either we are unable to read the estatus or the estatus is empty/invalid. Right now we silently handle that failure of

[PATCH v2] MAINTAINERS: fpga: Update email and add patchwork URL

Add Q: entry for patchwork and update my email address. Signed-off-by: Moritz Fischer Acked-By: Alan Tull Cc: Alan Tull Cc: linux-f...@vger.kernel.org Cc: linux-kernel@vger.kernel.org --- Changes from v1: - Don't mess up the email address

[PATCH v2] MAINTAINERS: fpga: Update email and add patchwork URL

Add Q: entry for patchwork and update my email address. Signed-off-by: Moritz Fischer Acked-By: Alan Tull Cc: Alan Tull Cc: linux-f...@vger.kernel.org Cc: linux-kernel@vger.kernel.org --- Changes from v1: - Don't mess up the email address --- MAINTAINERS | 3 ++- 1 file changed, 2

Re: [PATCH v2 1/3] kvm: svm: Add support for additional SVM NPF error codes

On 07/31/2017 10:44 AM, Paolo Bonzini wrote: On 31/07/2017 15:30, Brijesh Singh wrote: Hi Paolo, On 07/27/2017 11:27 AM, Paolo Bonzini wrote: On 23/11/2016 18:01, Brijesh Singh wrote: +/* + * Before emulating the instruction, check if the error code + * was due to a RO

Re: [PATCH v2 1/3] kvm: svm: Add support for additional SVM NPF error codes

On 07/31/2017 10:44 AM, Paolo Bonzini wrote: On 31/07/2017 15:30, Brijesh Singh wrote: Hi Paolo, On 07/27/2017 11:27 AM, Paolo Bonzini wrote: On 23/11/2016 18:01, Brijesh Singh wrote: +/* + * Before emulating the instruction, check if the error code + * was due to a RO

Re: [linux-sunxi] Re: [PATCH 0/4] clk: sunxi-ng: Fix issues with fractional mode

Hi Chen-Yu, Dne ponedeljek, 31. julij 2017 ob 07:13:34 CEST je Chen-Yu Tsai napisal(a): > Hi Jernej, > > On Mon, Jul 31, 2017 at 12:41 AM, Jernej Skrabec > > wrote: > > During development of H3 HDMI driver, I found some issues with > > setting video clock rate. It

Re: [linux-sunxi] Re: [PATCH 0/4] clk: sunxi-ng: Fix issues with fractional mode

Hi Chen-Yu, Dne ponedeljek, 31. julij 2017 ob 07:13:34 CEST je Chen-Yu Tsai napisal(a): > Hi Jernej, > > On Mon, Jul 31, 2017 at 12:41 AM, Jernej Skrabec > > wrote: > > During development of H3 HDMI driver, I found some issues with > > setting video clock rate. It turned out that clock driver

[PATCH v3] mm: add file_fdatawait_range and file_write_and_wait

From: Jeff Layton Necessary now for gfs2_fsync and sync_file_range, but there will eventually be other callers. Signed-off-by: Jeff Layton --- include/linux/fs.h | 11 ++- mm/filemap.c | 23 +++ 2 files changed, 33

[PATCH v3] mm: add file_fdatawait_range and file_write_and_wait

From: Jeff Layton Necessary now for gfs2_fsync and sync_file_range, but there will eventually be other callers. Signed-off-by: Jeff Layton --- include/linux/fs.h | 11 ++- mm/filemap.c | 23 +++ 2 files changed, 33 insertions(+), 1 deletion(-) v3: make

Re: [PATCH] md: replace seq_release_private with seq_release

On Sat, Jul 29, 2017 at 07:52:45PM +0300, Cihangir Akturk wrote: > Since commit f15146380d28 ("fs: seq_file - add event counter to simplify > poll() support"), md.c code has been no longer used the private field of > the struct seq_file, but seq_release_private() has been continued to be > used to

Re: [PATCH] md: replace seq_release_private with seq_release

On Sat, Jul 29, 2017 at 07:52:45PM +0300, Cihangir Akturk wrote: > Since commit f15146380d28 ("fs: seq_file - add event counter to simplify > poll() support"), md.c code has been no longer used the private field of > the struct seq_file, but seq_release_private() has been continued to be > used to

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Sat, Jul 29, 2017 at 12:43:35PM -0700, Dan Williams wrote: > An inode with this flag set indicates that the file's block map cannot > be changed, no size change, deletion, hole-punch, range collapse, or > reflink. > > The implementation of toggling the flag and sealing the state of the >

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Sat, Jul 29, 2017 at 12:43:35PM -0700, Dan Williams wrote: > An inode with this flag set indicates that the file's block map cannot > be changed, no size change, deletion, hole-punch, range collapse, or > reflink. > > The implementation of toggling the flag and sealing the state of the >

Re: Simplfying copy_siginfo_to_user

Al Viro writes: 2> On Mon, Jul 24, 2017 at 10:43:34AM -0700, Linus Torvalds wrote: >> On Sat, Jul 22, 2017 at 1:25 PM, Eric W. Biederman >> wrote: >> > I played with some clever changes such as limiting the copy to 48 bytes, >> > disabling the

Re: Simplfying copy_siginfo_to_user

Al Viro writes: 2> On Mon, Jul 24, 2017 at 10:43:34AM -0700, Linus Torvalds wrote: >> On Sat, Jul 22, 2017 at 1:25 PM, Eric W. Biederman >> wrote: >> > I played with some clever changes such as limiting the copy to 48 bytes, >> > disabling the memset and the like but I could not get a strong

Re: [PATCH 2/4] mailbox: pcc: Drop uninformative output during boot

[CC'ing Rafael J. Wysocki, who picks patches for pcc.c] On Mon, Jul 31, 2017 at 3:22 PM, Punit Agrawal wrote: > Punit Agrawal writes: > >> When booting on an ACPI enabled system that does not provide the >> Platform Communications Channel Table

Re: [PATCH 2/4] mailbox: pcc: Drop uninformative output during boot

[CC'ing Rafael J. Wysocki, who picks patches for pcc.c] On Mon, Jul 31, 2017 at 3:22 PM, Punit Agrawal wrote: > Punit Agrawal writes: > >> When booting on an ACPI enabled system that does not provide the >> Platform Communications Channel Table (PCCT), the pcc mailbox driver >> prints - >> >> [

Re: wake_wide mechanism clarification

On Mon, Jul 31, 2017 at 09:21:46AM -0700, Joel Fernandes wrote: > Hi Josef, > > On Mon, Jul 31, 2017 at 5:21 AM, Josef Bacik wrote: > > On Sat, Jul 29, 2017 at 03:41:56PM -0700, Joel Fernandes wrote: > >> On Sat, Jul 29, 2017 at 3:28 PM, Joel Fernandes

Re: wake_wide mechanism clarification

On Mon, Jul 31, 2017 at 09:21:46AM -0700, Joel Fernandes wrote: > Hi Josef, > > On Mon, Jul 31, 2017 at 5:21 AM, Josef Bacik wrote: > > On Sat, Jul 29, 2017 at 03:41:56PM -0700, Joel Fernandes wrote: > >> On Sat, Jul 29, 2017 at 3:28 PM, Joel Fernandes wrote: > >> > >> Again I didn't

Re: [PATCH RESEND] fbdev: omapfb: remove unused variable

On Wednesday, July 26, 2017 04:27:30 PM Bartlomiej Zolnierkiewicz wrote: > > Hi, > > On Wednesday, July 26, 2017 03:57:55 PM Arnd Bergmann wrote: > > Removing the default display name left a harmless warning: > > > > fbdev/omap2/omapfb/dss/core.c: In function 'omap_dss_probe': > >

[RFT PATCH 2/9] sh/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

Re: [PATCH RESEND] fbdev: omapfb: remove unused variable

On Wednesday, July 26, 2017 04:27:30 PM Bartlomiej Zolnierkiewicz wrote: > > Hi, > > On Wednesday, July 26, 2017 03:57:55 PM Arnd Bergmann wrote: > > Removing the default display name left a harmless warning: > > > > fbdev/omap2/omapfb/dss/core.c: In function 'omap_dss_probe': > >

[RFT PATCH 2/9] sh/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 1/9] sh/PCI: Remove __init optimisations from IRQ mapping functions/data

From: Matthew Minter Currently the many IRQ mapping functions and data structures use the __init and __initdata optimisations. These result in the relevant functions being innacessable after boot time. However for deferred IRQ assignment it is important to have access to

[RFT PATCH 1/9] sh/PCI: Remove __init optimisations from IRQ mapping functions/data

From: Matthew Minter Currently the many IRQ mapping functions and data structures use the __init and __initdata optimisations. These result in the relevant functions being innacessable after boot time. However for deferred IRQ assignment it is important to have access to these functions at PCI

[RFT PATCH 4/9] m68k/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 4/9] m68k/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 3/9] alpha/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 3/9] alpha/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 7/9] unicore32/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 7/9] unicore32/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 6/9] tile/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 6/9] tile/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

Re: [PATCH v2 1/3] dmaengine: add DMA_PREP_CMD for non-Data descriptors.

On 07/31/2017 05:34 AM, Vinod Koul wrote: > On Fri, Jul 28, 2017 at 09:38:56PM +0530, Abhishek Sahu wrote: >> On 2017-07-19 17:48, Abhishek Sahu wrote: >>> On 2017-07-19 15:37, Vinod Koul wrote: On Mon, Jun 26, 2017 at 06:19:27PM +0530, Abhishek Sahu wrote: > Some of the DMA controllers

Re: [PATCH v2 1/3] dmaengine: add DMA_PREP_CMD for non-Data descriptors.

On 07/31/2017 05:34 AM, Vinod Koul wrote: > On Fri, Jul 28, 2017 at 09:38:56PM +0530, Abhishek Sahu wrote: >> On 2017-07-19 17:48, Abhishek Sahu wrote: >>> On 2017-07-19 15:37, Vinod Koul wrote: On Mon, Jun 26, 2017 at 06:19:27PM +0530, Abhishek Sahu wrote: > Some of the DMA controllers

[RFT PATCH 9/9] PCI: Remove pci_fixup_irqs() function

From: Matthew Minter Now we have removed all callers of pci_fixup_irqs() and migrated everything to pci_assign_irq() delete the pci_fixup_irqs() function completely. Signed-off-by: Matthew Minter [lorenzo.pieral...@arm.com: updated commit log]

[RFT PATCH 9/9] PCI: Remove pci_fixup_irqs() function

From: Matthew Minter Now we have removed all callers of pci_fixup_irqs() and migrated everything to pci_assign_irq() delete the pci_fixup_irqs() function completely. Signed-off-by: Matthew Minter [lorenzo.pieral...@arm.com: updated commit log] Signed-off-by: Lorenzo Pieralisi ---

[RFT PATCH 8/9] sparc/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 5/9] MIPS/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 8/9] sparc/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 5/9] MIPS/PCI: Replace pci_fixup_irqs() call with PCI host bridge IRQ mapping hooks

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 0/9] PCI: Remove pci_fixup_irqs()

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

[RFT PATCH 0/9] PCI: Remove pci_fixup_irqs()

The pci_fixup_irqs() function allocates IRQs for all PCI devices present in a system; those PCI devices possibly belong to different PCI bus trees (and possibly rooted at different host bridges) and may well be enabled (ie probed and bound to a driver) by the time pci_fixup_irqs() is called when

Re: [PATCH 2/2] kbuild: clang: Disable the 'duplicate-decl-specifier' warning

El Wed, Jun 21, 2017 at 07:59:42PM +0200 Arnd Bergmann ha dit: > On Wed, Jun 21, 2017 at 6:58 PM, Matthias Kaehlcke wrote: > > El Wed, Jun 21, 2017 at 12:11:55PM +0200 Arnd Bergmann ha dit: > >> I see that container_of() has been modified in linux-next and no longer > >> adds

Re: [PATCH 2/2] kbuild: clang: Disable the 'duplicate-decl-specifier' warning

El Wed, Jun 21, 2017 at 07:59:42PM +0200 Arnd Bergmann ha dit: > On Wed, Jun 21, 2017 at 6:58 PM, Matthias Kaehlcke wrote: > > El Wed, Jun 21, 2017 at 12:11:55PM +0200 Arnd Bergmann ha dit: > >> I see that container_of() has been modified in linux-next and no longer > >> adds > >> the 'const'

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Mon, Jul 31, 2017, at 12:29 PM, Dan Williams wrote: > > How is S_CONTENTS_IMMUTABLE different than S_IMMUTABLE? We still want the ability to make hardlinks.

Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

On 31/07/17 10:10 AM, Andy Shevchenko wrote: > Some drivers (hardware) would like to have non-atomic MMIO accesses > when readq() defined Huh? But that's the whole point of the io64-nonatomic header. If a driver wants a specific non-atomic access they should just code two 32 bit accesses. > In

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Mon, Jul 31, 2017, at 12:29 PM, Dan Williams wrote: > > How is S_CONTENTS_IMMUTABLE different than S_IMMUTABLE? We still want the ability to make hardlinks.

Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

On 31/07/17 10:10 AM, Andy Shevchenko wrote: > Some drivers (hardware) would like to have non-atomic MMIO accesses > when readq() defined Huh? But that's the whole point of the io64-nonatomic header. If a driver wants a specific non-atomic access they should just code two 32 bit accesses. > In

Re: [PATCH] nand: fix wrong default oob layout for small pages using soft ecc

On Wed, 5 Jul 2017 09:04:53 +0200 Boris Brezillon wrote: > Hi Miquel, > > On Wed, 5 Jul 2017 08:51:09 +0200 > Miquel Raynal wrote: > > > When using soft ecc, if no ooblayout is given, the core automatically > > uses one of

Re: [PATCH] nand: fix wrong default oob layout for small pages using soft ecc

On Wed, 5 Jul 2017 09:04:53 +0200 Boris Brezillon wrote: > Hi Miquel, > > On Wed, 5 Jul 2017 08:51:09 +0200 > Miquel Raynal wrote: > > > When using soft ecc, if no ooblayout is given, the core automatically > > uses one of the nand_ooblayout_{sp,lp}*() functions to determine the > > layout

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Mon, Jul 31, 2017 at 9:02 AM, Colin Walters wrote: > On Sat, Jul 29, 2017, at 03:43 PM, Dan Williams wrote: >> An inode with this flag set indicates that the file's block map cannot >> be changed, no size change, deletion, hole-punch, range collapse, or >> reflink. >> >>

Re: [PATCH 1/3] fs, xfs: introduce S_IOMAP_IMMUTABLE

On Mon, Jul 31, 2017 at 9:02 AM, Colin Walters wrote: > On Sat, Jul 29, 2017, at 03:43 PM, Dan Williams wrote: >> An inode with this flag set indicates that the file's block map cannot >> be changed, no size change, deletion, hole-punch, range collapse, or >> reflink. >> >> The implementation of

Re: [PATCH] mtd: nand: sunxi: fix potential divide-by-zero error

On Fri, 28 Jul 2017 14:22:57 +0100 Bryan O'Donoghue wrote: > clk_round_rate() can return <= 0. Currently the value returned by > clk_round_rate() is used directly for a division. This patch introduces a > guard to ensure a divide-by-zero or a divide by a negative

Re: [PATCH] mtd: nand: sunxi: fix potential divide-by-zero error

On Fri, 28 Jul 2017 14:22:57 +0100 Bryan O'Donoghue wrote: > clk_round_rate() can return <= 0. Currently the value returned by > clk_round_rate() is used directly for a division. This patch introduces a > guard to ensure a divide-by-zero or a divide by a negative number for that > matter can't

Re: [PATCH] mux: include compiler.h from mux/consumer.h

On 2017-07-31 18:00, Greg Kroah-Hartman wrote: > On Mon, Jul 31, 2017 at 12:04:35PM +0200, Peter Rosin wrote: >> From: Ulrich Hecht >> >> Required for __must_check. >> >> Signed-off-by: Ulrich Hecht >> Signed-off-by: Peter Rosin

Re: [PATCH] mux: include compiler.h from mux/consumer.h

On 2017-07-31 18:00, Greg Kroah-Hartman wrote: > On Mon, Jul 31, 2017 at 12:04:35PM +0200, Peter Rosin wrote: >> From: Ulrich Hecht >> >> Required for __must_check. >> >> Signed-off-by: Ulrich Hecht >> Signed-off-by: Peter Rosin >> --- >> include/linux/mux/consumer.h | 2 ++ >> 1 file changed,

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