[PATCH v5 2/6] timekeeper: introduce boot field in system_time_snapshot

The field keeps monotonic time since boot. The value of boot will be used in KVM for masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM Signed-off-by: Denis Plotnikov ---

[PATCH v5 2/6] timekeeper: introduce boot field in system_time_snapshot

The field keeps monotonic time since boot. The value of boot will be used in KVM for masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM Signed-off-by: Denis Plotnikov --- include/linux/timekeeping.h | 2 ++

RE: [PATCH] cpufreq: imx6q: Fix imx6sx low frequency support

> -Original Message- > From: Leonard Crestez [mailto:leonard.cres...@nxp.com] > Sent: Monday, August 28, 2017 7:05 PM > To: Shawn Guo; Viresh Kumar; Rafael J. Wysocki > Cc: Anson Huang; Fabio Estevam; A.s. Dong; Lucas Stach; Jacky Bai; > ker...@pengutronix.de; linux...@vger.kernel.org;

RE: [PATCH] cpufreq: imx6q: Fix imx6sx low frequency support

> -Original Message- > From: Leonard Crestez [mailto:leonard.cres...@nxp.com] > Sent: Monday, August 28, 2017 7:05 PM > To: Shawn Guo; Viresh Kumar; Rafael J. Wysocki > Cc: Anson Huang; Fabio Estevam; A.s. Dong; Lucas Stach; Jacky Bai; > ker...@pengutronix.de; linux...@vger.kernel.org;

[PATCH v5 6/6] KVM: x86: remove not used pvclock_gtod_copy

Since, KVM has been switched to getting masterclock related data right from the timekeeper by the previous patches, now we are able to remove all the parts related to the old scheme of getting masterclock data. This patch removes those parts. Using of pvclock_gtod_copy notifier might be

[PATCH v5 6/6] KVM: x86: remove not used pvclock_gtod_copy

Since, KVM has been switched to getting masterclock related data right from the timekeeper by the previous patches, now we are able to remove all the parts related to the old scheme of getting masterclock data. This patch removes those parts. Using of pvclock_gtod_copy notifier might be

[PATCH v5 1/6] timekeeper: introduce extended clocksource reading callback

The callback provides extended information about just read clocksource value. It's going to be used in cases when detailed system information needed for further time related values calculation, e.g in KVM masterclock settings calculation. Signed-off-by: Denis Plotnikov

[PATCH v5 1/6] timekeeper: introduce extended clocksource reading callback

The callback provides extended information about just read clocksource value. It's going to be used in cases when detailed system information needed for further time related values calculation, e.g in KVM masterclock settings calculation. Signed-off-by: Denis Plotnikov ---

[PATCH v5 3/6] timekeeper: use the extended reading function on snapshot acquiring

Make use of the extended reading function on time snapshot getting: get raw cycles value if extended function is defined. The raw cycles value then is used for KVM masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM

[PATCH v5 3/6] timekeeper: use the extended reading function on snapshot acquiring

Make use of the extended reading function on time snapshot getting: get raw cycles value if extended function is defined. The raw cycles value then is used for KVM masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM

[PATCH v5 5/6] KVM: x86: switch to masterclock update using timekeeper functionality

It is reasonable to switch KVM to using a more simple, effective and conceptually correct scheme of dealing with the data needed for kvm masterclock values calculation. With the current scheme the kvm needs to have an up-to-date copy of some timekeeper data to provide a guest using kvmclock with

[PATCH v5 5/6] KVM: x86: switch to masterclock update using timekeeper functionality

It is reasonable to switch KVM to using a more simple, effective and conceptually correct scheme of dealing with the data needed for kvm masterclock values calculation. With the current scheme the kvm needs to have an up-to-date copy of some timekeeper data to provide a guest using kvmclock with

[PATCH v5 4/6] tsc: implement the extended tsc reading function

By doing that, add tsc clocksource to a list of KVM clocksources providing valid cycle values, meaning that KVM can use its masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM. Signed-off-by: Denis Plotnikov

[PATCH v5 0/6] KVM: x86: get rid of pvclock_gtod_copy

V5: It was decided to split the series "make L2's kvm-clock stable, get rid of pvclock_gtod_copy in KVM" into two parts to make the changes finer grained: 1. get rid of pvclock_gtod_copy in KVM 2. make L2's kvm-clock stable This V5 series implements the 1st part. This part gets

[PATCH v5 4/6] tsc: implement the extended tsc reading function

By doing that, add tsc clocksource to a list of KVM clocksources providing valid cycle values, meaning that KVM can use its masterclock. This is a part of the work aiming to move to a more simple scheme of masterclock related values calculation in KVM. Signed-off-by: Denis Plotnikov ---

[PATCH v5 0/6] KVM: x86: get rid of pvclock_gtod_copy

V5: It was decided to split the series "make L2's kvm-clock stable, get rid of pvclock_gtod_copy in KVM" into two parts to make the changes finer grained: 1. get rid of pvclock_gtod_copy in KVM 2. make L2's kvm-clock stable This V5 series implements the 1st part. This part gets

Re: [RESEND PATCH 2/3] regulator: Add support for stm32-vrefbuf

On 08/30/2017 05:02 PM, Mark Brown wrote: > On Wed, Aug 30, 2017 at 11:11:24AM +0200, Fabrice Gasnier wrote: >> On 08/29/2017 08:57 PM, Mark Brown wrote: >>> On Mon, Aug 28, 2017 at 02:58:52PM +0200, Fabrice Gasnier wrote: > +static int __init stm32_vrefbuf_init(void) +{ +

Re: [RESEND PATCH 2/3] regulator: Add support for stm32-vrefbuf

On 08/30/2017 05:02 PM, Mark Brown wrote: > On Wed, Aug 30, 2017 at 11:11:24AM +0200, Fabrice Gasnier wrote: >> On 08/29/2017 08:57 PM, Mark Brown wrote: >>> On Mon, Aug 28, 2017 at 02:58:52PM +0200, Fabrice Gasnier wrote: > +static int __init stm32_vrefbuf_init(void) +{ +

Applied "regulator: da9063: Return an error code on probe failure" to the regulator tree

The patch regulator: da9063: Return an error code on probe failure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: da9063: Return an error code on probe failure" to the regulator tree

The patch regulator: da9063: Return an error code on probe failure has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: pv88090: Exception handling for out of bounds" to the regulator tree

The patch regulator: pv88090: Exception handling for out of bounds has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: pv88090: Exception handling for out of bounds" to the regulator tree

The patch regulator: pv88090: Exception handling for out of bounds has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: rockchip: constify snd_soc_ops structures" to the asoc tree

The patch ASoC: rockchip: constify snd_soc_ops structures has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "ASoC: rockchip: constify snd_soc_ops structures" to the asoc tree

The patch ASoC: rockchip: constify snd_soc_ops structures has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Re: [PATCH] acpi: apei: call into AER handling regardless of severity

On Wed, Aug 30, 2017 at 10:05:44AM -0400, Sinan Kaya wrote: > Link reset is not the only recovery mechanism. In the case of nonfatal > errors, it is assumed that the endpoint CSR is still reachable. > Error is propagated the PCIe endpoint driver. Endpoint driver does a > re-initialization, we are

Re: [PATCH] acpi: apei: call into AER handling regardless of severity

On Wed, Aug 30, 2017 at 10:05:44AM -0400, Sinan Kaya wrote: > Link reset is not the only recovery mechanism. In the case of nonfatal > errors, it is assumed that the endpoint CSR is still reachable. > Error is propagated the PCIe endpoint driver. Endpoint driver does a > re-initialization, we are

[PATCH v2 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R ---

[PATCH v2 2/6] remoteproc: Export rproc_elf_get_boot_addr

Export rproc_elf_get_boot_addr so that it can be used by any remoteproc to get the bootaddr of the elf type firmware images. This is used in the subsequent patch by the q6v5 based remoteproc while loading its elf based mdt type image. Signed-off-by: Sricharan R ---

[PATCH v2 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 165

[PATCH v2 4/6] remoteproc: qcom: Split the head and tail of the q6v5-pil rproc start function

Most of the q6v5-pil start function is same for the q6v5-wcss rproc that will be added later. So split and move out the common pieces so that the same code can be reused. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 165 + 1 file

[PATCH v2 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R

[PATCH v2 5/6] remoteproc: qcom: Add support for q6v5-wcss pil

IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan (Lithium) IP. An mdt type single image format is used for the firmware. So the mdt_load function can be directly used to load the firmware. Also add the relevant resets required for this core. Signed-off-by: Sricharan R ---

[PATCH v2 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff

[PATCH v2 6/6] remoteproc: qcom: Add q6v5-wcss rproc ops

q6v5-wcss core's start function is mostly common with the q6v5 of msm8996. So reuse that and add the stop function. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 212 + 1 file changed, 212 insertions(+) diff --git

[PATCH v2 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c

[PATCH v2 3/6] remoteproc: qcom: Push reset ops, fw ops, rproc ops in to of_match data

Instead of directly assigning reset, fw and rproc ops, put them in to of_match data and get from that. Currently same ops are used for all compatibles, but that will change when we add q6v5-wcss support. Signed-off-by: Sricharan R --- drivers/remoteproc/qcom_q6v5_pil.c | 38

[PATCH v2 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R ---

[PATCH v2 1/6] remoteproc: qcom: mdt_loader: Make the firmware authentication optional

qcom_mdt_load function loads the mdt type firmware and initialises the secure memory as well. Make the initialisation only when requested by the caller, so that the function can be used by self-authenticating remoteproc as well. Signed-off-by: Sricharan R --- drivers/soc/qcom/mdt_loader.c

[PATCH v2 0/6] Add support for Hexagon q6v5-wcss integrated core

IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan (Lithium) IP. This series adds the remoteproc driver to reset, load and boot Q6 firmware. The first patch is to make the mdt_loader authenticate the firmware only if required, so that the code can be reused for self-authenticating

[PATCH v2 0/6] Add support for Hexagon q6v5-wcss integrated core

IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan (Lithium) IP. This series adds the remoteproc driver to reset, load and boot Q6 firmware. The first patch is to make the mdt_loader authenticate the firmware only if required, so that the code can be reused for self-authenticating

Re: [PATCH V1] regulator: pv88090: Exception handling for out of bounds

On Wed, Aug 30, 2017 at 05:54:27PM +0900, Eric Jeong wrote: I've applied this but a few things to bear in mind for future submissions: > From: Eric Jeong Please try to ensure that your e-mail address matches the one you use for signoff, this avoids your mail

Re: [PATCH V1] regulator: pv88090: Exception handling for out of bounds

On Wed, Aug 30, 2017 at 05:54:27PM +0900, Eric Jeong wrote: I've applied this but a few things to bear in mind for future submissions: > From: Eric Jeong Please try to ensure that your e-mail address matches the one you use for signoff, this avoids your mail looking like a non-author send

Re: [PATCH] storvsc: fix memory leak on ring buffer busy

On Tue, 29 Aug 2017 21:31:11 -0400 "Martin K. Petersen" wrote: > Long, > > > When storvsc is sending I/O to Hyper-v, it may allocate a bigger > > buffer descriptor for large data payload that can't fit into a > > pre-allocated buffer descriptor. This bigger buffer is

Re: [PATCH] storvsc: fix memory leak on ring buffer busy

On Tue, 29 Aug 2017 21:31:11 -0400 "Martin K. Petersen" wrote: > Long, > > > When storvsc is sending I/O to Hyper-v, it may allocate a bigger > > buffer descriptor for large data payload that can't fit into a > > pre-allocated buffer descriptor. This bigger buffer is freed on return > > path. >

[PATCH 02/16] autofs4: switch autofs4_write to __kernel_write

Instead of playing games with the address limit.. Signed-off-by: Christoph Hellwig --- fs/autofs4/waitq.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c index 24a58bf9ca72..4ac49d038bf3 100644 ---

[PATCH 02/16] autofs4: switch autofs4_write to __kernel_write

Instead of playing games with the address limit.. Signed-off-by: Christoph Hellwig --- fs/autofs4/waitq.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c index 24a58bf9ca72..4ac49d038bf3 100644 --- a/fs/autofs4/waitq.c +++

[PATCH 03/16] 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 03/16] 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 06/16] fs: fix kernel_write prototype

Make the position an in/out argument like all the other read/write helpers. Signed-off-by: Christoph Hellwig --- drivers/mtd/nand/nandsim.c| 2 +- drivers/target/target_core_alua.c | 3 ++- drivers/target/target_core_file.c | 3 +-- drivers/target/target_core_pr.c | 3 ++-

[PATCH 06/16] fs: fix kernel_write prototype

Make the position an in/out argument like all the other read/write helpers. Signed-off-by: Christoph Hellwig --- drivers/mtd/nand/nandsim.c| 2 +- drivers/target/target_core_alua.c | 3 ++- drivers/target/target_core_file.c | 3 +-- drivers/target/target_core_pr.c | 3 ++-

Re: [RESEND PATCH 2/3] regulator: Add support for stm32-vrefbuf

On Wed, Aug 30, 2017 at 11:11:24AM +0200, Fabrice Gasnier wrote: > On 08/29/2017 08:57 PM, Mark Brown wrote: > > On Mon, Aug 28, 2017 at 02:58:52PM +0200, Fabrice Gasnier wrote: > >> +static int __init stm32_vrefbuf_init(void) > >> +{ > >> + return platform_driver_register(_vrefbuf_driver); > >>

Re: [RESEND PATCH 2/3] regulator: Add support for stm32-vrefbuf

On Wed, Aug 30, 2017 at 11:11:24AM +0200, Fabrice Gasnier wrote: > On 08/29/2017 08:57 PM, Mark Brown wrote: > > On Mon, Aug 28, 2017 at 02:58:52PM +0200, Fabrice Gasnier wrote: > >> +static int __init stm32_vrefbuf_init(void) > >> +{ > >> + return platform_driver_register(_vrefbuf_driver); > >>

[PATCH 09/16] net/9p: switch p9_fd_read to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- net/9p/trans_fd.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c index f12815777beb..903a190319b9 100644 --- a/net/9p/trans_fd.c

[PATCH 08/16] mm/nommu: switch do_mmap_private to kernel_read

Instead of playing with the address limit. This also gains us validation of the kvec and proper atime updates. Signed-off-by: Christoph Hellwig --- mm/nommu.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/mm/nommu.c b/mm/nommu.c index

[PATCH 09/16] net/9p: switch p9_fd_read to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- net/9p/trans_fd.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c index f12815777beb..903a190319b9 100644 --- a/net/9p/trans_fd.c +++

[PATCH 08/16] mm/nommu: switch do_mmap_private to kernel_read

Instead of playing with the address limit. This also gains us validation of the kvec and proper atime updates. Signed-off-by: Christoph Hellwig --- mm/nommu.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/mm/nommu.c b/mm/nommu.c index

[PATCH 11/16] mconsole: switch to kernel_read

Instead of playing with address limits. Signed-off-by: Christoph Hellwig --- arch/um/drivers/mconsole_kern.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arch/um/drivers/mconsole_kern.c b/arch/um/drivers/mconsole_kern.c index af326fb6510d..c4d162a94be9

[PATCH 11/16] mconsole: switch to kernel_read

Instead of playing with address limits. Signed-off-by: Christoph Hellwig --- arch/um/drivers/mconsole_kern.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arch/um/drivers/mconsole_kern.c b/arch/um/drivers/mconsole_kern.c index af326fb6510d..c4d162a94be9 100644 ---

[PATCH 13/16] lustre: switch to kernel_write

Signed-off-by: Christoph Hellwig --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 10 ++ drivers/staging/lustre/lustre/obdclass/kernelcomm.c | 7 +-- 2 files changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/staging/lustre/lnet/libcfs/tracefile.c

[PATCH 13/16] lustre: switch to kernel_write

Signed-off-by: Christoph Hellwig --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 10 ++ drivers/staging/lustre/lustre/obdclass/kernelcomm.c | 7 +-- 2 files changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/staging/lustre/lnet/libcfs/tracefile.c

[PATCH 14/16] 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 14/16] 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/16] 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 15/16] 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/16] 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 16/16] 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 10/16] btrfs: switch write_buf to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- fs/btrfs/send.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c index b082210df9c8..24b989fd130c 100644 ---

[PATCH 10/16] btrfs: switch write_buf to kernel_write

Instead of playing with the addressing limits. Signed-off-by: Christoph Hellwig --- fs/btrfs/send.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c index b082210df9c8..24b989fd130c 100644 --- a/fs/btrfs/send.c +++

[PATCH 07/16] serial2002: switch serial2002_tty_write to kernel_{read/write}

Instead of playing games with the address limit. This also gains us proper usage of the write counter, time stamp updates and kvec validation. Signed-off-by: Christoph Hellwig --- drivers/staging/comedi/drivers/serial2002.c | 24 +--- 1 file changed, 5

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

And use the proper VFS helper for using the backing file. Signed-off-by: Christoph Hellwig --- drivers/staging/android/ashmem.c | 23 ++- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/drivers/staging/android/ashmem.c

[PATCH 07/16] serial2002: switch serial2002_tty_write to kernel_{read/write}

Instead of playing games with the address limit. This also gains us proper usage of the write counter, time stamp updates and kvec validation. Signed-off-by: Christoph Hellwig --- drivers/staging/comedi/drivers/serial2002.c | 24 +--- 1 file changed, 5 insertions(+), 19

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

And use the proper VFS helper for using the backing file. Signed-off-by: Christoph Hellwig --- drivers/staging/android/ashmem.c | 23 ++- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c index

[PATCH 12/16] 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 12/16] 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 05/16] fs: fix kernel_read prototype

Use proper ssize_t and size_t types for the return value and count argument, move the offset last and make it an in/out argument like all other read/write helpers. Signed-off-by: Christoph Hellwig --- arch/mips/kernel/elf.c | 12

[PATCH 05/16] fs: fix kernel_read prototype

Use proper ssize_t and size_t types for the return value and count argument, move the offset last and make it an in/out argument like all other read/write helpers. Signed-off-by: Christoph Hellwig --- arch/mips/kernel/elf.c | 12

[PATCH 04/16] fs: move kernel_read to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/exec.c | 17 - fs/read_write.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/exec.c b/fs/exec.c index 62175cbcc801..8adcc5eaa175 100644 --- a/fs/exec.c +++ b/fs/exec.c @@

[PATCH 04/16] fs: move kernel_read to fs/read_write.c

Signed-off-by: Christoph Hellwig --- fs/exec.c | 17 - fs/read_write.c | 16 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/fs/exec.c b/fs/exec.c index 62175cbcc801..8adcc5eaa175 100644 --- a/fs/exec.c +++ b/fs/exec.c @@ -885,23 +885,6 @@

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

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

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

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 v4] ARM: dts: stm32: change pinctrl bindings definition

Initially each pin was declared in "include/dt-bindings/stm32-pinfunc.h" and each definition contained SOC names (ex: STM32F429_PA9_FUNC_USART1_TX). Since this approach was approved, the number of supported MCU has increased (STM32F429/STM32F469/STM32f746/STM32H743). To avoid to add a new file in

[PATCH v4] ARM: dts: stm32: change pinctrl bindings definition

Initially each pin was declared in "include/dt-bindings/stm32-pinfunc.h" and each definition contained SOC names (ex: STM32F429_PA9_FUNC_USART1_TX). Since this approach was approved, the number of supported MCU has increased (STM32F429/STM32F469/STM32f746/STM32H743). To avoid to add a new file in

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

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 read-through this looks fine. But it obviously > > needs testing. > >

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

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 read-through this looks fine. But it obviously > > needs testing. > >

Re: [PATCH v2] iwlwifi: pcie: move rx workqueue initialization to iwl_trans_pcie_alloc()

On Tue, Aug 22, 2017 at 10:37:29AM +0300, Luca Coelho wrote: > From: Luca Coelho > > Work queues cannot be allocated when a mutex is held because the mutex > may be in use and that would make it sleep. Doing so generates the > following splat with 4.13+: > > [

Re: [PATCH v2] iwlwifi: pcie: move rx workqueue initialization to iwl_trans_pcie_alloc()

On Tue, Aug 22, 2017 at 10:37:29AM +0300, Luca Coelho wrote: > From: Luca Coelho > > Work queues cannot be allocated when a mutex is held because the mutex > may be in use and that would make it sleep. Doing so generates the > following splat with 4.13+: > > [ 19.513298]

Re: [PATCH v3 49/59] KVM: arm/arm64: GICv4: Propagate VLPI properties at map time

On 28/08/17 19:18, Christoffer Dall wrote: > On Mon, Jul 31, 2017 at 06:26:27PM +0100, Marc Zyngier wrote: >> When the VLPI gets mapped, it must inherit the configuration of >> LPI configured at the vITS level. FOr that purpose, let's make > > *the LPI > *For that Will fix, thanks. > >>

Re: [PATCH v3 49/59] KVM: arm/arm64: GICv4: Propagate VLPI properties at map time

On 28/08/17 19:18, Christoffer Dall wrote: > On Mon, Jul 31, 2017 at 06:26:27PM +0100, Marc Zyngier wrote: >> When the VLPI gets mapped, it must inherit the configuration of >> LPI configured at the vITS level. FOr that purpose, let's make > > *the LPI > *For that Will fix, thanks. > >>

[PATCH v3] eeprom: idt_89hpesx: Support both ACPI and OF probing

From: Huy Duong Allow the idt_89hpesx driver to get information from child nodes from both OF and ACPI by using more generic fwnode_property_read*() functions. Below is an example of instantiating idt_89hpesx driver via ACPI Table: Device(IDT0) { Name(_HID, "PRP0001")

[PATCH v3] eeprom: idt_89hpesx: Support both ACPI and OF probing

From: Huy Duong Allow the idt_89hpesx driver to get information from child nodes from both OF and ACPI by using more generic fwnode_property_read*() functions. Below is an example of instantiating idt_89hpesx driver via ACPI Table: Device(IDT0) { Name(_HID, "PRP0001") Name(_CID, "PRP0001")

Re: [PATCH 4/7] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on Nanopi M1 Plus

Hi, On Wed, Aug 30, 2017 at 05:01:07AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The WiFi side of the AP6212 WiFi/BT combo module is connected to > mmc1. There are also GPIOs for enable and interrupts. > > Enable WiFi on this board by enabling mmc1 and adding

Re: [PATCH 4/7] ARM: dts: sun8i: h3: Enable AP6212 WiFi on mmc1 on Nanopi M1 Plus

Hi, On Wed, Aug 30, 2017 at 05:01:07AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The WiFi side of the AP6212 WiFi/BT combo module is connected to > mmc1. There are also GPIOs for enable and interrupts. > > Enable WiFi on this board by enabling mmc1 and adding the power >

Re: RGB support prototype

Hi! > > We could even export (read-only) hue/saturation for single-color LEDs... > > Related patches from Heiner Kallweit are still sitting on devel branch > of linux-leds.git: > > https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git/log/?h=devel > > Possibly it can

Re: RGB support prototype

Hi! > > We could even export (read-only) hue/saturation for single-color LEDs... > > Related patches from Heiner Kallweit are still sitting on devel branch > of linux-leds.git: > > https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git/log/?h=devel > > Possibly it can

Re: [PATCH 2/7] ARM: dts: sun8i: h3: nanopi-m1-plus: Enable IR controller

On Wed, Aug 30, 2017 at 05:01:05AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The Nanopi M1 Plus has an onboard IR receiver. > This enables the onboard IR receiver subnode. > > Signed-off-by: Philipp Rossak Queued for 4.15, thanks! Maxime --

Re: [PATCH 2/7] ARM: dts: sun8i: h3: nanopi-m1-plus: Enable IR controller

On Wed, Aug 30, 2017 at 05:01:05AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The Nanopi M1 Plus has an onboard IR receiver. > This enables the onboard IR receiver subnode. > > Signed-off-by: Philipp Rossak Queued for 4.15, thanks! Maxime -- Maxime Ripard, Free Electrons

Re: [PATCH 1/7] ARM: dts: sun8i: h3: nanopi-m1: Enable IR controller

On Wed, Aug 30, 2017 at 05:01:04AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The Nanopi M1 has an onboard IR receiver. > This enables the onboard IR receiver subnode. > > Signed-off-by: Philipp Rossak Queued for 4.15, thanks! Maxime --

Re: [PATCH 1/7] ARM: dts: sun8i: h3: nanopi-m1: Enable IR controller

On Wed, Aug 30, 2017 at 05:01:04AM +0200, Philipp Rossak wrote: > From: Philipp Rossak > > The Nanopi M1 has an onboard IR receiver. > This enables the onboard IR receiver subnode. > > Signed-off-by: Philipp Rossak Queued for 4.15, thanks! Maxime -- Maxime Ripard, Free Electrons Embedded

Re: [PATCH v4 1/3] livepatch: add (un)patch callbacks

On Fri, Aug 25, 2017 at 03:10:00PM -0400, Joe Lawrence wrote: > @@ -871,6 +882,13 @@ int klp_module_coming(struct module *mod) > pr_notice("applying patch '%s' to loading module > '%s'\n", > patch->mod->name, obj->mod->name); > > +

Re: [PATCH v4 1/3] livepatch: add (un)patch callbacks

On Fri, Aug 25, 2017 at 03:10:00PM -0400, Joe Lawrence wrote: > @@ -871,6 +882,13 @@ int klp_module_coming(struct module *mod) > pr_notice("applying patch '%s' to loading module > '%s'\n", > patch->mod->name, obj->mod->name); > > +

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