[RFC PATCH 09/11] afs: Allow IPv6 address specification of VL servers

Allow VL server specifications to be given IPv6 addresses as well as IPv4 addresses, for example as: echo add procyon.org.uk :::0:::: >/proc/fs/afs/cells Note that ':' is the expected separator for separating IPv4 addresses, but if a ',' is detected or no '.'

[RFC PATCH 10/11] afs: Overhaul cell database management

Overhaul the way that the in-kernel AFS client keeps track of cells in the following manner: (1) Cells are now held in an rbtree to make walking them quicker and RCU managed (though this is probably overkill). (2) Cells now have a manager work item that: (A) Looks after fetching and

[RFC PATCH 08/11] afs: Keep and pass sockaddr_rxrpc addresses rather than in_addr

Keep and pass sockaddr_rxrpc addresses around rather than keeping and passing in_addr addresses to allow for the use of IPv6 and non-standard port numbers in future. This also allows the port and service_id fields to be removed from the afs_call struct. Signed-off-by: David Howells

[RFC PATCH 08/11] afs: Keep and pass sockaddr_rxrpc addresses rather than in_addr

Keep and pass sockaddr_rxrpc addresses around rather than keeping and passing in_addr addresses to allow for the use of IPv6 and non-standard port numbers in future. This also allows the port and service_id fields to be removed from the afs_call struct. Signed-off-by: David Howells ---

[RFC PATCH 06/11] afs: Add some protocol defs

Add some protocol definitions, including max field lengths, flag defs and an XDR-encoded UUID def. Signed-off-by: David Howells --- fs/afs/afs.h| 25 - fs/afs/afs_vl.h |6 +- 2 files changed, 25 insertions(+), 6 deletions(-) diff

[RFC PATCH 06/11] afs: Add some protocol defs

Add some protocol definitions, including max field lengths, flag defs and an XDR-encoded UUID def. Signed-off-by: David Howells --- fs/afs/afs.h| 25 - fs/afs/afs_vl.h |6 +- 2 files changed, 25 insertions(+), 6 deletions(-) diff --git a/fs/afs/afs.h

[RFC PATCH 05/11] afs: Lay the groundwork for supporting network namespaces

Lay the groundwork for supporting network namespaces (netns) to the AFS filesystem by moving various global features to a network-namespace struct (afs_net) and providing an instance of this as a temporary global variable that everything uses via accessor functions for the moment. The following

[RFC PATCH 04/11] Add a function to start/reduce a timer

Add a function, similar to mod_timer(), that will start a timer it isn't running and will modify it if it is running and has an expiry time longer than the new time. If the timer is running with an expiry time that's the same or sooner, no change is made. The function looks like: int

[RFC PATCH 04/11] Add a function to start/reduce a timer

Add a function, similar to mod_timer(), that will start a timer it isn't running and will modify it if it is running and has an expiry time longer than the new time. If the timer is running with an expiry time that's the same or sooner, no change is made. The function looks like: int

[RFC PATCH 05/11] afs: Lay the groundwork for supporting network namespaces

Lay the groundwork for supporting network namespaces (netns) to the AFS filesystem by moving various global features to a network-namespace struct (afs_net) and providing an instance of this as a temporary global variable that everything uses via accessor functions for the moment. The following

[RFC PATCH 03/11] Pass mode to wait_on_atomic_t() action funcs and provide default actions

Make wait_on_atomic_t() pass the TASK_* mode onto its action function as an extra argument and make it 'unsigned int throughout. Also, consolidate a bunch of identical action functions into a default function that can do the appropriate thing for the mode. Also, change the argument name in the

[RFC PATCH 03/11] Pass mode to wait_on_atomic_t() action funcs and provide default actions

Make wait_on_atomic_t() pass the TASK_* mode onto its action function as an extra argument and make it 'unsigned int throughout. Also, consolidate a bunch of identical action functions into a default function that can do the appropriate thing for the mode. Also, change the argument name in the

[RFC PATCH 01/11] workqueue: Add a decrement-after-return and wake if 0 facility

Add a facility to the workqueue subsystem whereby an atomic_t can be registered by a work function such that the work function dispatcher will decrement the atomic after the work function has returned and then call wake_up_atomic() on it if it reached 0. This is analogous to complete_and_exit()

[RFC PATCH 02/11] refcount: Implement inc/decrement-and-return functions

Implement functions that increment or decrement a refcount_t object and return the value. The dec-and-ret function can be used to maintain a counter in a cache where 1 means the object is unused, but available and the garbage collector can use refcount_dec_if_one() to make the object unavailable.

[RFC PATCH 01/11] workqueue: Add a decrement-after-return and wake if 0 facility

Add a facility to the workqueue subsystem whereby an atomic_t can be registered by a work function such that the work function dispatcher will decrement the atomic after the work function has returned and then call wake_up_atomic() on it if it reached 0. This is analogous to complete_and_exit()

[RFC PATCH 02/11] refcount: Implement inc/decrement-and-return functions

Implement functions that increment or decrement a refcount_t object and return the value. The dec-and-ret function can be used to maintain a counter in a cache where 1 means the object is unused, but available and the garbage collector can use refcount_dec_if_one() to make the object unavailable.

[PATCH 15/17] fs: unexport __vfs_read/__vfs_write

No modular users left, and any new ones should use kernel_read/write or iov_iter variants instead. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 2 -- include/linux/fs.h | 1 - 2 files changed, 3 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index

[PATCH 15/17] fs: unexport __vfs_read/__vfs_write

No modular users left, and any new ones should use kernel_read/write or iov_iter variants instead. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 2 -- include/linux/fs.h | 1 - 2 files changed, 3 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index

[PATCH 17/17] fs: unexport vfs_readv and vfs_writev

We've got no modular users left, and any potential modular user is better of with iov_iter based variants. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 4 +--- include/linux/fs.h | 2 -- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/fs/read_write.c

[PATCH 17/17] fs: unexport vfs_readv and vfs_writev

We've got no modular users left, and any potential modular user is better of with iov_iter based variants. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 4 +--- include/linux/fs.h | 2 -- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c

[PATCH 16/17] fs: unexport vfs_read and vfs_write

No modular users left. Given that they take user pointers there is no good reason to export it to drivers to start with. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 4 1 file changed, 4 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index

[PATCH 16/17] fs: unexport vfs_read and vfs_write

No modular users left. Given that they take user pointers there is no good reason to export it to drivers to start with. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 4 1 file changed, 4 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index

[PATCH 13/17] gadget/f_mass_storage: stop messing with the address limit

Instead use kernel_read/write consistently, which also makes sparse happy. Signed-off-by: Christoph Hellwig --- drivers/usb/gadget/function/f_mass_storage.c | 21 ++--- 1 file changed, 6 insertions(+), 15 deletions(-) diff --git

[PATCH 13/17] gadget/f_mass_storage: stop messing with the address limit

Instead use kernel_read/write consistently, which also makes sparse happy. Signed-off-by: Christoph Hellwig --- drivers/usb/gadget/function/f_mass_storage.c | 21 ++--- 1 file changed, 6 insertions(+), 15 deletions(-) diff --git a/drivers/usb/gadget/function/f_mass_storage.c

[PATCH 07/17] fs: make the buf argument to __kernel_write a void pointer

This matches kernel_read and kernel_write and avoids any need for casts in the callers. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 2 +- include/linux/fs.h | 2 +- kernel/acct.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 03/17] fs: move kernel_write to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/read_write.c | 17 - fs/splice.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index 0cc7033aa413..417dbe199505 100644 --- a/fs/read_write.c +++

[PATCH 07/17] fs: make the buf argument to __kernel_write a void pointer

This matches kernel_read and kernel_write and avoids any need for casts in the callers. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 2 +- include/linux/fs.h | 2 +- kernel/acct.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/read_write.c

[PATCH 03/17] fs: move kernel_write to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/read_write.c | 17 - fs/splice.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index 0cc7033aa413..417dbe199505 100644 --- a/fs/read_write.c +++

[PATCH 01/17] ashmem: switch to ->read_iter

And use the proper VFS helper for using the backing file. Also make sure we hold ashmem_lock while updating f_pos to make sure that it's not racy. Signed-off-by: Christoph Hellwig --- drivers/staging/android/ashmem.c | 29 - 1 file changed, 8

switch in-kernel read/write calls to kernel_read/write V2

Hi all, this series moves almost all kernel callers of vfs_read/write and friends to the kernel_read/write family that includes the set_fs calls inside the called routines. The exceptions are the integrity code (Mimi has a pending series for that one) and the splice readv code which doesn't fit

[PATCH 01/17] ashmem: switch to ->read_iter

And use the proper VFS helper for using the backing file. Also make sure we hold ashmem_lock while updating f_pos to make sure that it's not racy. Signed-off-by: Christoph Hellwig --- drivers/staging/android/ashmem.c | 29 - 1 file changed, 8 insertions(+), 21

switch in-kernel read/write calls to kernel_read/write V2

Hi all, this series moves almost all kernel callers of vfs_read/write and friends to the kernel_read/write family that includes the set_fs calls inside the called routines. The exceptions are the integrity code (Mimi has a pending series for that one) and the splice readv code which doesn't fit

ptp device strangeness

Hi I am currently using ptp on a Altera/Intel SOC with a dp8640 PHY. PTP functionality seems to be right. But i am doing timestamping with gpio0 and sometimes i loose the sync of the stamping and the events. So i would like to read out all messages. Reading O_NONBLOCK does not work so i tried

ptp device strangeness

Hi I am currently using ptp on a Altera/Intel SOC with a dp8640 PHY. PTP functionality seems to be right. But i am doing timestamping with gpio0 and sometimes i loose the sync of the stamping and the events. So i would like to read out all messages. Reading O_NONBLOCK does not work so i tried

Re: [PATCH v1] platform/x86: wmi: Switch to use new generic UUID API

On Fri, Sep 1, 2017 at 1:23 AM, Christoph Hellwig wrote: > On Wed, Aug 30, 2017 at 01:01:28PM -0700, Andy Lutomirski wrote: >> What I'm saying is: I agree that "RFC4122 UUID" and "wintel GUID" are >> different, but the new structs aren't called "RFC4122 UUID" and >> "wintel GUID" -

Re: [PATCH v1] platform/x86: wmi: Switch to use new generic UUID API

On Fri, Sep 1, 2017 at 1:23 AM, Christoph Hellwig wrote: > On Wed, Aug 30, 2017 at 01:01:28PM -0700, Andy Lutomirski wrote: >> What I'm saying is: I agree that "RFC4122 UUID" and "wintel GUID" are >> different, but the new structs aren't called "RFC4122 UUID" and >> "wintel GUID" - they're called

Re: [PATCH 2/2] dt-bindings: soc: qcom: Extend GLINK to cover SMEM

On Tue, Aug 29, 2017 at 6:13 PM, Bjorn Andersson wrote: > In addition to using GLINK for communication with the RPM it can be > used ontop of SMEM for communicating with remoteprocs, extend the > binding to also describe this case and reference the GLINK binding from >

Re: [PATCH 2/2] dt-bindings: soc: qcom: Extend GLINK to cover SMEM

On Tue, Aug 29, 2017 at 6:13 PM, Bjorn Andersson wrote: > In addition to using GLINK for communication with the RPM it can be > used ontop of SMEM for communicating with remoteprocs, extend the > binding to also describe this case and reference the GLINK binding from > the affected remoteproc

Re: [PATCH V2 1/5] perf tools: support new sample type for physical address

Em Fri, Sep 01, 2017 at 05:28:27PM +0200, Jiri Olsa escreveu: > On Tue, Aug 29, 2017 at 01:11:08PM -0400, kan.li...@intel.com wrote: > > SNIP > > > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c > > index a5888c7..228a78d 100644 > > --- a/tools/perf/util/evsel.c > > +++

Re: [PATCH V2 1/5] perf tools: support new sample type for physical address

Em Fri, Sep 01, 2017 at 05:28:27PM +0200, Jiri Olsa escreveu: > On Tue, Aug 29, 2017 at 01:11:08PM -0400, kan.li...@intel.com wrote: > > SNIP > > > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c > > index a5888c7..228a78d 100644 > > --- a/tools/perf/util/evsel.c > > +++

Re: [PATCHv2 1/7] dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding

On Mon, Aug 28, 2017 at 04:20:12PM +0200, Amelie Delaunay wrote: > This patch adds binding documentation for DWC2 controller in HS mode found > on STMicroelectronics STM32F7 SoC. > > Signed-off-by: Amelie Delaunay > --- > Documentation/devicetree/bindings/usb/dwc2.txt |

Re: [PATCHv2 1/7] dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding

On Mon, Aug 28, 2017 at 04:20:12PM +0200, Amelie Delaunay wrote: > This patch adds binding documentation for DWC2 controller in HS mode found > on STMicroelectronics STM32F7 SoC. > > Signed-off-by: Amelie Delaunay > --- > Documentation/devicetree/bindings/usb/dwc2.txt | 2 ++ > 1 file changed,

[PATCH] [media] rtl28xxu: make array rc_nec_tab static const

From: Colin Ian King Don't populate the array rc_nec_tab on the stack, instead make it static const. Makes the object code smaller by over 620 bytes: Before: textdata bss dec hex filename 49511 17040 64 66615 10437 rtl28xxu.o After:

[PATCH] [media] rtl28xxu: make array rc_nec_tab static const

From: Colin Ian King Don't populate the array rc_nec_tab on the stack, instead make it static const. Makes the object code smaller by over 620 bytes: Before: textdata bss dec hex filename 49511 17040 64 66615 10437 rtl28xxu.o After: textdata bss

Re: [PATCH V2 1/5] perf tools: support new sample type for physical address

On Tue, Aug 29, 2017 at 01:11:08PM -0400, kan.li...@intel.com wrote: SNIP > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c > index a5888c7..228a78d 100644 > --- a/tools/perf/util/evsel.c > +++ b/tools/perf/util/evsel.c > @@ -950,6 +950,9 @@ void perf_evsel__config(struct

Re: [PATCH V2 1/5] perf tools: support new sample type for physical address

On Tue, Aug 29, 2017 at 01:11:08PM -0400, kan.li...@intel.com wrote: SNIP > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c > index a5888c7..228a78d 100644 > --- a/tools/perf/util/evsel.c > +++ b/tools/perf/util/evsel.c > @@ -950,6 +950,9 @@ void perf_evsel__config(struct

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Thu, Aug 31, 2017 at 10:51 PM, Benjamin Herrenschmidt wrote: > This allow to (slowly) migrate those embedded platforms > to of_platform_default_populate() > > Signed-off-by: Benjamin Herrenschmidt > --- > > I'm here to collect acks (or

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Thu, Aug 31, 2017 at 10:51 PM, Benjamin Herrenschmidt wrote: > This allow to (slowly) migrate those embedded platforms > to of_platform_default_populate() > > Signed-off-by: Benjamin Herrenschmidt > --- > > I'm here to collect acks (or comments :-) I'd like this to go via > the powerpc tree

[PATCH] tools,selftest: kcmp -- Add KCMP_EPOLL_TFD testing

KCMP's KCMP_EPOLL_TFD mode merged in commit 0791e3644e5ef21646fe565b9061788d05ec71d4 but we've had no selftest for it yet (except in criu development list). Thus add it. Signed-off-by: Cyrill Gorcunov CC: Andrey Vagin CC: Andrew Morton

[PATCH] tools,selftest: kcmp -- Add KCMP_EPOLL_TFD testing

KCMP's KCMP_EPOLL_TFD mode merged in commit 0791e3644e5ef21646fe565b9061788d05ec71d4 but we've had no selftest for it yet (except in criu development list). Thus add it. Signed-off-by: Cyrill Gorcunov CC: Andrey Vagin CC: Andrew Morton CC: Pavel Emelyanov CC: Michael Kerrisk ---

Re: axonram: Delete an error message for a failed memory allocation in axon_ram_probe()

> Series applied to powerpc next, thanks. Thanks for another positive feedback. But I wonder how you can refer to the “series” when the forth update step “Delete an unnecessary variable initialisation” contained a broken suggestion. >

Re: axonram: Delete an error message for a failed memory allocation in axon_ram_probe()

> Series applied to powerpc next, thanks. Thanks for another positive feedback. But I wonder how you can refer to the “series” when the forth update step “Delete an unnecessary variable initialisation” contained a broken suggestion. >

[PATCH] ARM: dts: da850-evm: add chosen and SPI alias

At the request of Sekhar Nori from TI, this is a follow-up to pending ("ARM: dts: da850-evm: add serial and ethernet aliases") This patch will add the chosen container to point stdout-path to serial2 and set the alias for spi0 to spi1 since the SPI NOR flash exists on SPI1. Signed-off-by: Adam

[PATCH] ARM: dts: da850-evm: add chosen and SPI alias

At the request of Sekhar Nori from TI, this is a follow-up to pending ("ARM: dts: da850-evm: add serial and ethernet aliases") This patch will add the chosen container to point stdout-path to serial2 and set the alias for spi0 to spi1 since the SPI NOR flash exists on SPI1. Signed-off-by: Adam

[PATCH] cpudile: optimize cpuidle_enable_device error handling

do not fetch per cpu drv id cpuidle_curr_governor is NULL. if cpuidle_enable_device is NULL return -EIO. it prevents the addtional per cpu processing Signed-off-by: Gaurav Jindal --- diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c index

[PATCH] cpudile: optimize cpuidle_enable_device error handling

do not fetch per cpu drv id cpuidle_curr_governor is NULL. if cpuidle_enable_device is NULL return -EIO. it prevents the addtional per cpu processing Signed-off-by: Gaurav Jindal --- diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c index 1519716..6464e09 100644 ---

[PATCH] MIPS: mt7620: Rename uartlite to serial

Previously, mt7620.c defined the clocks for uarts with the names uartlite, uart1 and uart2. Rename them to serial{0,1,2} and update the devicetree node names. Signed-off-by: Harvey Hunt Cc: devicet...@vger.kernel.org Cc: linux-m...@linux-mips.org Cc:

[PATCH] MIPS: mt7620: Rename uartlite to serial

Previously, mt7620.c defined the clocks for uarts with the names uartlite, uart1 and uart2. Rename them to serial{0,1,2} and update the devicetree node names. Signed-off-by: Harvey Hunt Cc: devicet...@vger.kernel.org Cc: linux-m...@linux-mips.org Cc: linux-kernel@vger.kernel.org ---

Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback

On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote: > On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote: > > I will wait for people to test and for result of my own test before > > reposting if need be, otherwise i will post as separate patch. > > > > > But from a _very_ quick

Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback

On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote: > On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote: > > I will wait for people to test and for result of my own test before > > reposting if need be, otherwise i will post as separate patch. > > > > > But from a _very_ quick

Re: [PATCH 06/13] thermal/drivers/hisi: Remove pointless lock

On Wed, Aug 30, 2017 at 10:47:30AM +0200, Daniel Lezcano wrote: > The threaded interrupt inspect the sensors structure to look in the temp > threshold field, but this field is read-only in all the code, except in the > probe function before the threaded interrupt is set. In other words there > is

Re: [PATCH 06/13] thermal/drivers/hisi: Remove pointless lock

On Wed, Aug 30, 2017 at 10:47:30AM +0200, Daniel Lezcano wrote: > The threaded interrupt inspect the sensors structure to look in the temp > threshold field, but this field is read-only in all the code, except in the > probe function before the threaded interrupt is set. In other words there > is

Re: [PATCH 1/3] dmaengine: sun6i: Correct DMA support on H3

On Freitag, 1. September 2017 15:35:49 CEST Maxime Ripard wrote: > On Fri, Sep 01, 2017 at 05:04:54AM +0200, Stefan Bruens wrote: > > On Donnerstag, 31. August 2017 16:51:35 CEST Maxime Ripard wrote: > > > Hi, > > > > > > On Thu, Aug 31, 2017 at 01:36:07AM +0200, Stefan Brüns wrote: > > > > +/*

Re: [PATCH 1/3] dmaengine: sun6i: Correct DMA support on H3

On Freitag, 1. September 2017 15:35:49 CEST Maxime Ripard wrote: > On Fri, Sep 01, 2017 at 05:04:54AM +0200, Stefan Bruens wrote: > > On Donnerstag, 31. August 2017 16:51:35 CEST Maxime Ripard wrote: > > > Hi, > > > > > > On Thu, Aug 31, 2017 at 01:36:07AM +0200, Stefan Brüns wrote: > > > > +/*

Re: [PATCH 05/13] thermal/drivers/hisi: Fix multiple alarm interrupts firing

On Wed, Aug 30, 2017 at 10:47:29AM +0200, Daniel Lezcano wrote: > The DT specifies a threshold of 65000, we setup the register with a value in > the temperature resolution for the controller, 64656. > > When we reach 64656, the interrupt fires, the interrupt is disabled. Then the > irq thread

Re: [PATCH 05/13] thermal/drivers/hisi: Fix multiple alarm interrupts firing

On Wed, Aug 30, 2017 at 10:47:29AM +0200, Daniel Lezcano wrote: > The DT specifies a threshold of 65000, we setup the register with a value in > the temperature resolution for the controller, 64656. > > When we reach 64656, the interrupt fires, the interrupt is disabled. Then the > irq thread

Re: [PATCH] x86/idt: Fix the X86_TRAP_BP gate

On Fri, Sep 01, 2017 at 10:26:30AM +0200, Ingo Molnar wrote: > > Hi Andrei, > > * Andrei Vagin wrote: > > > Hi Thomas, > > > > We run CRIU tests for linux-next and today they detected an issue. I've > > bisected this problem and it looks like a problem is in this patch.

Re: [PATCH] x86/idt: Fix the X86_TRAP_BP gate

On Fri, Sep 01, 2017 at 10:26:30AM +0200, Ingo Molnar wrote: > > Hi Andrei, > > * Andrei Vagin wrote: > > > Hi Thomas, > > > > We run CRIU tests for linux-next and today they detected an issue. I've > > bisected this problem and it looks like a problem is in this patch. > > Ok, there appears

pull-request: wireless-drivers-next 2017-09-01

Hi Dave, here's a pull request to net-next for 4.14. If the merge window opens on Sunday I'm planning to have this as the last one. Please let me know if there are any problems. Kalle The following changes since commit d081a16db80ef7a260fb178aa1199e01f7432625: net: bcmgenet: Do not return

pull-request: wireless-drivers-next 2017-09-01

Hi Dave, here's a pull request to net-next for 4.14. If the merge window opens on Sunday I'm planning to have this as the last one. Please let me know if there are any problems. Kalle The following changes since commit d081a16db80ef7a260fb178aa1199e01f7432625: net: bcmgenet: Do not return

Re: [PATCH] swait: add missing barrier to swake_up

On Fri, Sep 01, 2017 at 07:55:29PM +1000, Nicholas Piggin wrote: > On Fri, 1 Sep 2017 11:23:22 +0200 > Andrea Parri wrote: > > > On Fri, Sep 01, 2017 at 04:14:50PM +1000, Nicholas Piggin wrote: > > > swake_up and swake_up_all test the swaitqueue outside the lock, > > >

Re: [PATCH] swait: add missing barrier to swake_up

On Fri, Sep 01, 2017 at 07:55:29PM +1000, Nicholas Piggin wrote: > On Fri, 1 Sep 2017 11:23:22 +0200 > Andrea Parri wrote: > > > On Fri, Sep 01, 2017 at 04:14:50PM +1000, Nicholas Piggin wrote: > > > swake_up and swake_up_all test the swaitqueue outside the lock, > > > but they are missing the

Re: [v2,1/2] hwmon: (adcxx) add devictree bindings documentation

On Mon, Aug 21, 2017 at 10:19:51AM +0200, Florian Eckert wrote: > Document the devicetree bindings for the adcxx. > > Signed-off-by: Florian Eckert > --- > v2: > - use regulator voltage binding > > Documentation/devicetree/bindings/hwmon/adcxx.txt | 24 >

Re: [v2,1/2] hwmon: (adcxx) add devictree bindings documentation

On Mon, Aug 21, 2017 at 10:19:51AM +0200, Florian Eckert wrote: > Document the devicetree bindings for the adcxx. > > Signed-off-by: Florian Eckert > --- > v2: > - use regulator voltage binding > > Documentation/devicetree/bindings/hwmon/adcxx.txt | 24 > +++ > 1 file

Re: [PATCH 1/3] dt-bindings: watchdog: Add Realtek RTD1295

On Mon, Aug 28, 2017 at 01:35:29PM +0200, Andreas Färber wrote: > Add a binding for the Realtek RTD1295 watchdog. > > Signed-off-by: Andreas Färber > --- > .../devicetree/bindings/watchdog/realtek,rtd119x.txt| 17 > + > 1 file changed, 17 insertions(+) >

Re: [PATCH 1/3] dt-bindings: watchdog: Add Realtek RTD1295

On Mon, Aug 28, 2017 at 01:35:29PM +0200, Andreas Färber wrote: > Add a binding for the Realtek RTD1295 watchdog. > > Signed-off-by: Andreas Färber > --- > .../devicetree/bindings/watchdog/realtek,rtd119x.txt| 17 > + > 1 file changed, 17 insertions(+) > create mode 100644

Re: [PATCH 3/3] arm64: dts: realtek: Add watchdog node for RTD1295

On Mon, Aug 28, 2017 at 01:35:31PM +0200, Andreas Färber wrote: > Add the watchdog node to the RTD1295 Device Tree. > > Signed-off-by: Andreas Färber > --- > Depends on the pending clock nodes patch. > > arch/arm64/boot/dts/realtek/rtd1295.dtsi | 6 ++ > 1 file changed,

Re: [PATCH 3/3] arm64: dts: realtek: Add watchdog node for RTD1295

On Mon, Aug 28, 2017 at 01:35:31PM +0200, Andreas Färber wrote: > Add the watchdog node to the RTD1295 Device Tree. > > Signed-off-by: Andreas Färber > --- > Depends on the pending clock nodes patch. > > arch/arm64/boot/dts/realtek/rtd1295.dtsi | 6 ++ > 1 file changed, 6 insertions(+)

Re: [PATCH v2 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295

On Mon, Aug 28, 2017 at 12:53:42PM +0200, Andreas Färber wrote: > Add binding for Realtek RTD1295 IRQ mux. > > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Dropped reference to common interrupt.txt bindings (Rob) > > .../interrupt-controller/realtek,rtd119x-mux.txt

Re: [PATCH v2 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295

On Mon, Aug 28, 2017 at 12:53:42PM +0200, Andreas Färber wrote: > Add binding for Realtek RTD1295 IRQ mux. > > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Dropped reference to common interrupt.txt bindings (Rob) > > .../interrupt-controller/realtek,rtd119x-mux.txt | 23 >

Re: [PATCH v3 2/2] hwmon: (ltq-cputemp) add devicetree bindings documentation

On Fri, Sep 01, 2017 at 08:58:18AM +0200, Florian Eckert wrote: > Document the devicetree bindings for the ltq-cputemp > > Signed-off-by: Florian Eckert I see nothing special with the bindings, and they are in line with other lantiq bindings, so I am taking the risk of

Re: [PATCH v3 2/2] hwmon: (ltq-cputemp) add devicetree bindings documentation

On Fri, Sep 01, 2017 at 08:58:18AM +0200, Florian Eckert wrote: > Document the devicetree bindings for the ltq-cputemp > > Signed-off-by: Florian Eckert I see nothing special with the bindings, and they are in line with other lantiq bindings, so I am taking the risk of accepting this patch (and

Re: [PATCH 04/13] thermal/drivers/hisi: Simplify the temperature/step computation

On Wed, Aug 30, 2017 at 10:47:28AM +0200, Daniel Lezcano wrote: > The step and the base temperature are fixed values, we can simplify the > computation by converting the base temperature to milli celsius and use a > pre-computed step value. That saves us a lot of mult + div for nothing at >

Re: [PATCH 04/13] thermal/drivers/hisi: Simplify the temperature/step computation

On Wed, Aug 30, 2017 at 10:47:28AM +0200, Daniel Lezcano wrote: > The step and the base temperature are fixed values, we can simplify the > computation by converting the base temperature to milli celsius and use a > pre-computed step value. That saves us a lot of mult + div for nothing at >

Re: [PATCH v3 1/2] hwmon: (ltq-cputemp) add cpu temp sensor driver

On Fri, Sep 01, 2017 at 08:58:17AM +0200, Florian Eckert wrote: > Add the lantiq cpu temperature sensor support for xrx200. > > Signed-off-by: Florian Eckert Applied to hwmon-next. Thanks, Guenter > --- > v2: > - remove default in Makefile > - fix spelling > - removing first

Re: [PATCH v3 1/2] hwmon: (ltq-cputemp) add cpu temp sensor driver

On Fri, Sep 01, 2017 at 08:58:17AM +0200, Florian Eckert wrote: > Add the lantiq cpu temperature sensor support for xrx200. > > Signed-off-by: Florian Eckert Applied to hwmon-next. Thanks, Guenter > --- > v2: > - remove default in Makefile > - fix spelling > - removing first read delay,

Re: [tip:locking/core] locking/osq_lock: Fix osq_lock queue corruption

On Fri, 01 Sep 2017, Peter Zijlstra wrote: On Thu, Aug 31, 2017 at 12:40:19PM -0700, Davidlohr Bueso wrote: On Thu, 10 Aug 2017, tip-bot for Prateek Sood wrote: > Signed-off-by: Prateek Sood > [ Added pictures, rewrote comments. ] > Signed-off-by: Peter Zijlstra

Re: [tip:locking/core] locking/osq_lock: Fix osq_lock queue corruption

On Fri, 01 Sep 2017, Peter Zijlstra wrote: On Thu, Aug 31, 2017 at 12:40:19PM -0700, Davidlohr Bueso wrote: On Thu, 10 Aug 2017, tip-bot for Prateek Sood wrote: > Signed-off-by: Prateek Sood > [ Added pictures, rewrote comments. ] > Signed-off-by: Peter Zijlstra (Intel) > Cc: Linus Torvalds

Re: [PATCH][staging-next] staging: typec: fusb302: make structure fusb302_psy_desc static

On Fri, Sep 01, 2017 at 11:20:57AM +0100, Colin King wrote: > From: Colin Ian King > > The const structure fusb302_psy_desc is local to the source and > does not need to be in global scope, so make it static. > > Cleans up sparse warnings > symbol 'fusb302_psy_desc'

Re: [PATCH][staging-next] staging: typec: fusb302: make structure fusb302_psy_desc static

On Fri, Sep 01, 2017 at 11:20:57AM +0100, Colin King wrote: > From: Colin Ian King > > The const structure fusb302_psy_desc is local to the source and > does not need to be in global scope, so make it static. > > Cleans up sparse warnings > symbol 'fusb302_psy_desc' was not declared. Should it

Re: [PATCH] kernfs: checking for IS_ERR() instead of NULL

On 08/30/2017 08:04 AM, Dan Carpenter wrote: > The kernfs_get_inode() returns NULL on error, it never returns error > pointers. Added for 4.14, with the ack from Tejun and Greg. -- Jens Axboe

Re: [PATCH] kernfs: checking for IS_ERR() instead of NULL

On 08/30/2017 08:04 AM, Dan Carpenter wrote: > The kernfs_get_inode() returns NULL on error, it never returns error > pointers. Added for 4.14, with the ack from Tejun and Greg. -- Jens Axboe

Re: [PATCH 03/13] thermal/drivers/hisi: Fix kernel panic on alarm interrupt

On Wed, Aug 30, 2017 at 10:47:27AM +0200, Daniel Lezcano wrote: > The threaded interrupt for the alarm interrupt is requested before the > temperature controller is setup. This one can fire an interrupt immediately > leading to a kernel panic as the sensor data is not initialized. > > In order to

Re: [PATCH 03/13] thermal/drivers/hisi: Fix kernel panic on alarm interrupt

On Wed, Aug 30, 2017 at 10:47:27AM +0200, Daniel Lezcano wrote: > The threaded interrupt for the alarm interrupt is requested before the > temperature controller is setup. This one can fire an interrupt immediately > leading to a kernel panic as the sensor data is not initialized. > > In order to

Re: [PATCH 02/13] thermal/drivers/hisi: Remove the multiple sensors support

Hi Daniel, On Wed, Aug 30, 2017 at 10:47:26AM +0200, Daniel Lezcano wrote: > By essence, the tsensor does not really support multiple sensor at the same > time. It allows to set a sensor and use it to get the temperature, another > sensor could be switched but with a delay of 3-5ms. It is

Re: [PATCH 02/13] thermal/drivers/hisi: Remove the multiple sensors support

Hi Daniel, On Wed, Aug 30, 2017 at 10:47:26AM +0200, Daniel Lezcano wrote: > By essence, the tsensor does not really support multiple sensor at the same > time. It allows to set a sensor and use it to get the temperature, another > sensor could be switched but with a delay of 3-5ms. It is

Re: [PATCH v4 4/5] net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated

On Thu, Aug 31, 2017 at 3:59 PM, Andrew Lunn wrote: > On Thu, Aug 31, 2017 at 03:18:03PM -0500, Rob Herring wrote: >> On Sat, Aug 26, 2017 at 11:20:51PM +0200, Andrew Lunn wrote: >> > Hi Corentin >> > >> > I think we have now all agreed this is an mdio-mux, plus it is also an >> >

Re: [PATCH v4 4/5] net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated

On Thu, Aug 31, 2017 at 3:59 PM, Andrew Lunn wrote: > On Thu, Aug 31, 2017 at 03:18:03PM -0500, Rob Herring wrote: >> On Sat, Aug 26, 2017 at 11:20:51PM +0200, Andrew Lunn wrote: >> > Hi Corentin >> > >> > I think we have now all agreed this is an mdio-mux, plus it is also an >> > MII mux. We

Re: [PATCH 05/13] irqchip: add initial support for ompic

On Thu, Aug 31, 2017 at 11:59:40AM +0100, Mark Rutland wrote: > On Thu, Aug 31, 2017 at 06:58:36AM +0900, Stafford Horne wrote: > > From: Stefan Kristiansson > > > > IPI driver for OpenRISC Multicore programmable interrupt controller as > > described in the

Re: [PATCH 05/13] irqchip: add initial support for ompic

On Thu, Aug 31, 2017 at 11:59:40AM +0100, Mark Rutland wrote: > On Thu, Aug 31, 2017 at 06:58:36AM +0900, Stafford Horne wrote: > > From: Stefan Kristiansson > > > > IPI driver for OpenRISC Multicore programmable interrupt controller as > > described in the Multicore support section of the

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