Re: [PATCH 7/8] LinuxPPS: pps_gen_parport: Add polarity parameter for inverted signal.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov On some devices it may be necessary to transmit inverted data. This commit simply adds polarity parameter to define which state represents presence of signal: it equals 0 if signal is on the low level

Re: [PATCH 7/8] LinuxPPS: pps_gen_parport: Add polarity parameter for inverted signal.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov On some devices it may be necessary to transmit inverted data. This commit simply adds polarity parameter to define which state represents presence of signal: it equals 0 if signal is on the low level (default), or 1 if

Re: [PATCH 6/8] LinuxPPS: pps_parport: Ignore interrupt invoked less than 0.5sec after previous.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov On some devices interrupt may be invoked by parasitic assert event produced while switching from high to low. Such interrupt should be ignored. Signed-off-by: Alexander GQ Gerasiov

Crypto Fixes for 4.11

Hi Linus: This push fixes the following issues: - vmalloc stack regression in CCM. - Build problem in CRC32 on ARM. - Memory leak in cavium. - Missing Kconfig dependencies in atmel and mediatek. - XTS Regression on some platforms (s390 and ppc). - Memory overrun in CCM test vector. Please pull

Re: [PATCH 1/2] pps: add ioctl_compat function to correct ioctl definitions

On 02/24/17 21:23, Matt Ranostay wrote: ioctl definitions use the pointer size of the architecture which is fine when userspace and kernel are the same bitsize. This patchset workarounds an issue with mixed bitsize kernel + userspace by rewriting the cmd to the kernelspace architecture pointer

Re: [PATCH 6/8] LinuxPPS: pps_parport: Ignore interrupt invoked less than 0.5sec after previous.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov On some devices interrupt may be invoked by parasitic assert event produced while switching from high to low. Such interrupt should be ignored. Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo Giometti

Crypto Fixes for 4.11

Hi Linus: This push fixes the following issues: - vmalloc stack regression in CCM. - Build problem in CRC32 on ARM. - Memory leak in cavium. - Missing Kconfig dependencies in atmel and mediatek. - XTS Regression on some platforms (s390 and ppc). - Memory overrun in CCM test vector. Please pull

Re: [PATCH 1/2] pps: add ioctl_compat function to correct ioctl definitions

On 02/24/17 21:23, Matt Ranostay wrote: ioctl definitions use the pointer size of the architecture which is fine when userspace and kernel are the same bitsize. This patchset workarounds an issue with mixed bitsize kernel + userspace by rewriting the cmd to the kernelspace architecture pointer

Re: [PATCH 5/8] LinuxPPS: pps_parport: Do not generate assert in case of lost signal.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Since clear timeout is non-zero, some clear event capture is requested. Therefore, if signal is lost we shouldn't generate assert event alone. Signed-off-by: Alexander GQ Gerasiov

Re: [PATCH 5/8] LinuxPPS: pps_parport: Do not generate assert in case of lost signal.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Since clear timeout is non-zero, some clear event capture is requested. Therefore, if signal is lost we shouldn't generate assert event alone. Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo Giometti

Re: [PATCH 4/8] LinuxPPS: kapi: Unlock before waking up events queue in pps_event().

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Otherwise we get "scheduling while atomic" problem. Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo Giometti

Re: [PATCH 4/8] LinuxPPS: kapi: Unlock before waking up events queue in pps_event().

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Otherwise we get "scheduling while atomic" problem. Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo Giometti

Re: [PATCH 3/8] hardpps: fix some pps_jitter issues.

On 02/15/17 15:31, Andrey Drobyshev wrote: Handle possible overflow, implementation-defined result of signed right shift and replace unsuitable constant. Signed-off-by: Andrey Drobyshev Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo

Re: [PATCH 3/8] hardpps: fix some pps_jitter issues.

On 02/15/17 15:31, Andrey Drobyshev wrote: Handle possible overflow, implementation-defined result of signed right shift and replace unsuitable constant. Signed-off-by: Andrey Drobyshev Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo Giometti

Re: [PATCH 1/8] hardpps: simple fixes replacing clumsy code with abs() macro.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Here are some trivial fixes, including: * simplify comparisons by using abs() macro * remove unnecessary variables * remove duplicate headers * fix typos Signed-off-by: Alexander GQ Gerasiov

Re: [PATCH 1/8] hardpps: simple fixes replacing clumsy code with abs() macro.

On 02/15/17 15:31, Andrey Drobyshev wrote: From: Alexander GQ Gerasiov Here are some trivial fixes, including: * simplify comparisons by using abs() macro * remove unnecessary variables * remove duplicate headers * fix typos Signed-off-by: Alexander GQ Gerasiov Acked-by: Rodolfo

Re: [GIT PULL] sched.h split-up

* Linus Torvalds wrote: > Anyway, I fixed the semantic merge error by just including thar > file, but this is just not acceptable. > > Having to have files know that if they use the wait-event functins > (well, _some_ of them), they not only need to include , >

Re: [GIT PULL] sched.h split-up

* Linus Torvalds wrote: > Anyway, I fixed the semantic merge error by just including thar > file, but this is just not acceptable. > > Having to have files know that if they use the wait-event functins > (well, _some_ of them), they not only need to include , > they need to completely

Re: [PATCH] staging: ks7010: clean up code

On Sat, 2017-03-04 at 08:49 +0200, Ernestas Kulik wrote: > On Fri, 2017-03-03 at 22:37-0800, Joe Perches wrote: > > > > struct hostif_hdr.event is declared at uint16_t > > and not as __le16 so I believe this is incorrect > > and actually introduces a sparse error. > > Sure, but I change that in

Re: [PATCH] staging: ks7010: clean up code

On Sat, 2017-03-04 at 08:49 +0200, Ernestas Kulik wrote: > On Fri, 2017-03-03 at 22:37-0800, Joe Perches wrote: > > > > struct hostif_hdr.event is declared at uint16_t > > and not as __le16 so I believe this is incorrect > > and actually introduces a sparse error. > > Sure, but I change that in

[PATCH v2] mmc: mediatek: Fixed bug where clock frequency could be set wrong

yong mao (1): mmc: mediatek: Fixed bug where clock frequency could be set wrong drivers/mmc/host/mtk-sd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- 1.8.1.1.dirty

[PATCH v2] mmc: mediatek: Fixed bug where clock frequency could be set wrong

yong mao (1): mmc: mediatek: Fixed bug where clock frequency could be set wrong drivers/mmc/host/mtk-sd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- 1.8.1.1.dirty

[PATCH] mmc: mediatek: Fixed bug where clock frequency could be set wrong

From: yong mao This patch can fix two issues: Issue 1: In previous code, div may be overflow when setting clock frequency as f_min. We can use DIV_ROUND_UP to fix this boundary related issue. Issue 2: In previous code, we can not set the correct clock frequency when div

[PATCH] mmc: mediatek: Fixed bug where clock frequency could be set wrong

From: yong mao This patch can fix two issues: Issue 1: In previous code, div may be overflow when setting clock frequency as f_min. We can use DIV_ROUND_UP to fix this boundary related issue. Issue 2: In previous code, we can not set the correct clock frequency when div equals 0xff.

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

On Thu, 2017-03-02 at 20:20 +0800, Daniel Kurtz wrote: > On Wed, Mar 1, 2017 at 5:56 PM, Yong Mao wrote: > > On Tue, 2017-02-28 at 14:56 +0800, Daniel Kurtz wrote: > >> On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao wrote: > >> > From: Yong Mao

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

On Thu, 2017-03-02 at 20:20 +0800, Daniel Kurtz wrote: > On Wed, Mar 1, 2017 at 5:56 PM, Yong Mao wrote: > > On Tue, 2017-02-28 at 14:56 +0800, Daniel Kurtz wrote: > >> On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao wrote: > >> > From: Yong Mao > >> > To: Daniel Kurtz > >> > Subject:

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 22:37-0800, Joe Perches wrote: > > struct hostif_hdr.event is declared at uint16_t > and not as __le16 so I believe this is incorrect > and actually introduces a sparse error. Sure, but I change that in the patch. :) On Sat, 2017-03-04 at 08:28 +0200, Ernestas Kulik wrote:

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 22:37-0800, Joe Perches wrote: > > struct hostif_hdr.event is declared at uint16_t > and not as __le16 so I believe this is incorrect > and actually introduces a sparse error. Sure, but I change that in the patch. :) On Sat, 2017-03-04 at 08:28 +0200, Ernestas Kulik wrote:

Re: Is it really safe to use workqueues to drive expedited grace periods?

On Fri, Mar 03, 2017 at 11:30:49AM -0800, Tejun Heo wrote: > Hello, Paul. > > Sorry about the long delay. Travel + sickness. Just starting to > catch up with things now. No problem, I have been distracted by other projects in any case. ;-) > On Mon, Feb 13, 2017 at 04:16:00PM -0800, Paul E.

Re: Is it really safe to use workqueues to drive expedited grace periods?

On Fri, Mar 03, 2017 at 11:30:49AM -0800, Tejun Heo wrote: > Hello, Paul. > > Sorry about the long delay. Travel + sickness. Just starting to > catch up with things now. No problem, I have been distracted by other projects in any case. ;-) > On Mon, Feb 13, 2017 at 04:16:00PM -0800, Paul E.

Re: [PATCH] staging: ks7010: clean up code

On Sat, 2017-03-04 at 08:28 +0200, Ernestas Kulik wrote: > On Fri, 2017-03-03 at 17:23-0800, Joe Perches wrote: > > > On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > > > > > This fixes type warnings generated by sparse, replaces instances of > > > ntohs() with be16_to_cpu() and

Re: [PATCH] staging: ks7010: clean up code

On Sat, 2017-03-04 at 08:28 +0200, Ernestas Kulik wrote: > On Fri, 2017-03-03 at 17:23-0800, Joe Perches wrote: > > > On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > > > > > This fixes type warnings generated by sparse, replaces instances of > > > ntohs() with be16_to_cpu() and

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 17:23-0800, Joe Perches wrote: > On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > > > This fixes type warnings generated by sparse, replaces instances of > > ntohs() with be16_to_cpu() and removes unused fields in structs. > > There's no real need to convert ntohs

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 17:23-0800, Joe Perches wrote: > On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > > > This fixes type warnings generated by sparse, replaces instances of > > ntohs() with be16_to_cpu() and removes unused fields in structs. > > There's no real need to convert ntohs

Re: [PATCH v5 3/4] iio: accel: adxl345: Split driver into core and I2C

On Fri, Mar 03, 2017 at 06:51:28PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Move I2C-specific code into its own file and rely on regmap to access > > registers. The core code provides access to x, y, z and scale

Re: [PATCH v5 3/4] iio: accel: adxl345: Split driver into core and I2C

On Fri, Mar 03, 2017 at 06:51:28PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Move I2C-specific code into its own file and rely on regmap to access > > registers. The core code provides access to x, y, z and scale readings. > > Portion of

Re: [RFC] arm64: support HAVE_ARCH_RARE_WRITE

> On Mar 4, 2017, at 5:50 AM, Andy Lutomirski wrote: > >> On Thu, Mar 2, 2017 at 7:00 AM, Hoeun Ryu wrote: >> +unsigned long __rare_write_rw_alias_start = TASK_SIZE_64 / 4; >> + >> +__always_inline unsigned long __arch_rare_write_map(void) >> +{ >> +

Re: [RFC] arm64: support HAVE_ARCH_RARE_WRITE

> On Mar 4, 2017, at 5:50 AM, Andy Lutomirski wrote: > >> On Thu, Mar 2, 2017 at 7:00 AM, Hoeun Ryu wrote: >> +unsigned long __rare_write_rw_alias_start = TASK_SIZE_64 / 4; >> + >> +__always_inline unsigned long __arch_rare_write_map(void) >> +{ >> + struct mm_struct *mm = _write_mm; >>

Re: [PATCH v5 4/4] iio: accel: adxl345: Add SPI support

On Fri, Mar 03, 2017 at 06:55:26PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Add SPI driver that initializes SPI regmap for the adxl345 core driver. > > The driver supports the same functionality as I2C namely the x, y, z

Re: [PATCH v5 4/4] iio: accel: adxl345: Add SPI support

On Fri, Mar 03, 2017 at 06:55:26PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Add SPI driver that initializes SPI regmap for the adxl345 core driver. > > The driver supports the same functionality as I2C namely the x, y, z and > > scale

Re: [PATCH 1/4] net: thunderx: Fix IOMMU translation faults

On Fri, Mar 3, 2017 at 11:26 PM, David Miller wrote: > From: sunil.kovv...@gmail.com > Date: Fri, 3 Mar 2017 16:17:47 +0530 > >> @@ -1643,6 +1650,9 @@ static int nicvf_probe(struct pci_dev *pdev, const >> struct pci_device_id *ent) >> if (!pass1_silicon(nic->pdev)) >>

Re: [PATCH 1/4] net: thunderx: Fix IOMMU translation faults

On Fri, Mar 3, 2017 at 11:26 PM, David Miller wrote: > From: sunil.kovv...@gmail.com > Date: Fri, 3 Mar 2017 16:17:47 +0530 > >> @@ -1643,6 +1650,9 @@ static int nicvf_probe(struct pci_dev *pdev, const >> struct pci_device_id *ent) >> if (!pass1_silicon(nic->pdev)) >>

Re: [RFC] arm64: support HAVE_ARCH_RARE_WRITE

> On Mar 3, 2017, at 1:02 PM, Kees Cook wrote: > >> On Thu, Mar 2, 2017 at 7:00 AM, Hoeun Ryu wrote: >> This RFC is a quick and dirty arm64 implementation for Kees Cook's RFC for >> rare_write infrastructure [1]. > > Awesome! :) > >> This

Re: [RFC] arm64: support HAVE_ARCH_RARE_WRITE

> On Mar 3, 2017, at 1:02 PM, Kees Cook wrote: > >> On Thu, Mar 2, 2017 at 7:00 AM, Hoeun Ryu wrote: >> This RFC is a quick and dirty arm64 implementation for Kees Cook's RFC for >> rare_write infrastructure [1]. > > Awesome! :) > >> This implementation is based on Mark Rutland's

Re: [PATCH v5 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

On Fri, Mar 03, 2017 at 06:44:27PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Convert the driver to use regmap instead of I2C-specific functions. This > > is done in preparation for splitting this driver into core and > >

Re: [PATCH v5 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

On Fri, Mar 03, 2017 at 06:44:27PM +0200, Andy Shevchenko wrote: > On Tue, Feb 28, 2017 at 4:37 AM, Eva Rachel Retuya > wrote: > > Convert the driver to use regmap instead of I2C-specific functions. This > > is done in preparation for splitting this driver into core and > > I2C-specific code as

[PATCH] KVM: nVMX: Reset nested_run_pending if the CPU is going to be reset

Reported by syzkaller: WARNING: CPU: 1 PID: 27742 at arch/x86/kvm/vmx.c:11029 nested_vmx_vmexit+0x5c35/0x74d0 arch/x86/kvm/vmx.c:11029 CPU: 1 PID: 27742 Comm: a.out Not tainted 4.10.0+ #229 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs

[PATCH] KVM: nVMX: Reset nested_run_pending if the CPU is going to be reset

Reported by syzkaller: WARNING: CPU: 1 PID: 27742 at arch/x86/kvm/vmx.c:11029 nested_vmx_vmexit+0x5c35/0x74d0 arch/x86/kvm/vmx.c:11029 CPU: 1 PID: 27742 Comm: a.out Not tainted 4.10.0+ #229 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

On Fri, Mar 03, 2017 at 03:19:12PM -0800, Darrick J. Wong wrote: > On Sat, Mar 04, 2017 at 09:54:44AM +1100, Dave Chinner wrote: > > On Thu, Mar 02, 2017 at 04:45:40PM +0100, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > Even though kmem_zalloc_greedy is documented it

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

On Fri, Mar 03, 2017 at 03:19:12PM -0800, Darrick J. Wong wrote: > On Sat, Mar 04, 2017 at 09:54:44AM +1100, Dave Chinner wrote: > > On Thu, Mar 02, 2017 at 04:45:40PM +0100, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > Even though kmem_zalloc_greedy is documented it might fail the

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 11:35:51 +0900 Masami Hiramatsu wrote: > On Sat, 4 Mar 2017 09:49:11 +0900 > Masami Hiramatsu wrote: > > > On Thu, 2 Mar 2017 23:25:06 +0530 > > "Naveen N. Rao" wrote: > > > > > We indicate support

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 11:35:51 +0900 Masami Hiramatsu wrote: > On Sat, 4 Mar 2017 09:49:11 +0900 > Masami Hiramatsu wrote: > > > On Thu, 2 Mar 2017 23:25:06 +0530 > > "Naveen N. Rao" wrote: > > > > > We indicate support for accepting sym+offset with kretprobes through a > > > line in ftrace

Re: [v2] mmc: sdhci-cadence: add HS400 enhanced strobe support

Hi Piotr, 2017-03-03 17:31 GMT+09:00 Piotr Sroka : > Add support for HS400ES mode to Cadence SDHCI driver. > > Signed-off-by: Piotr Sroka Thanks for your patch. It looks almost good to me. My comments are about some coding style issues only. Please see

Re: [v2] mmc: sdhci-cadence: add HS400 enhanced strobe support

Hi Piotr, 2017-03-03 17:31 GMT+09:00 Piotr Sroka : > Add support for HS400ES mode to Cadence SDHCI driver. > > Signed-off-by: Piotr Sroka Thanks for your patch. It looks almost good to me. My comments are about some coding style issues only. Please see below. > +static void

Re: [PATCH v10 1/2] usb: dwc2: assert phy reset when waking up in rk3288 platform

What is wrong with this patch? I have not seen it is merged in next-20170303. On 12/11/2016 11:36 PM, Randy Li wrote: On the rk3288 USB host-only port (the one that's not the OTG-enabled port) the PHY can get into a bad state when a wakeup is asserted (not just a wakeup from full system

Re: [PATCH v10 1/2] usb: dwc2: assert phy reset when waking up in rk3288 platform

What is wrong with this patch? I have not seen it is merged in next-20170303. On 12/11/2016 11:36 PM, Randy Li wrote: On the rk3288 USB host-only port (the one that's not the OTG-enabled port) the PHY can get into a bad state when a wakeup is asserted (not just a wakeup from full system

[git pull] vfs.git final bits and pieces

A few unrelated patches that got beating in -next. Everything else will have to go into the next window ;-/ The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) are available in the git repository at:

[git pull] vfs.git final bits and pieces

A few unrelated patches that got beating in -next. Everything else will have to go into the next window ;-/ The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) are available in the git repository at:

[PATCH] mm: do not call mem_cgroup_free() from within mem_cgroup_alloc()

mem_cgroup_free() indirectly calls wb_domain_exit() which is not prepared to deal with a struct wb_domain object that hasn't executed wb_domain_init(). For instance, the following warning message is printed by lockdep if alloc_percpu() fails in mem_cgroup_alloc(): INFO: trying to register

[PATCH] mm: do not call mem_cgroup_free() from within mem_cgroup_alloc()

mem_cgroup_free() indirectly calls wb_domain_exit() which is not prepared to deal with a struct wb_domain object that hasn't executed wb_domain_init(). For instance, the following warning message is printed by lockdep if alloc_percpu() fails in mem_cgroup_alloc(): INFO: trying to register

Re: [PATCH v2 1/1] serial: 8250_dw: Allow hardware flow control to be used

On Sat, Mar 4, 2017 at 1:23 AM, James Hogan wrote: > On Fri, Mar 03, 2017 at 03:31:06PM +0200, Andy Shevchenko wrote: >> On Fri, 2017-03-03 at 00:21 +, James Hogan wrote: >> > The CONFIG_HAVE_CLK=n implementation of devm_clk_get() in particular >> > seems highly

Re: [PATCH v2 1/1] serial: 8250_dw: Allow hardware flow control to be used

On Sat, Mar 4, 2017 at 1:23 AM, James Hogan wrote: > On Fri, Mar 03, 2017 at 03:31:06PM +0200, Andy Shevchenko wrote: >> On Fri, 2017-03-03 at 00:21 +, James Hogan wrote: >> > The CONFIG_HAVE_CLK=n implementation of devm_clk_get() in particular >> > seems highly questionable to me, given that

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 09:49:11 +0900 Masami Hiramatsu wrote: > On Thu, 2 Mar 2017 23:25:06 +0530 > "Naveen N. Rao" wrote: > > > We indicate support for accepting sym+offset with kretprobes through a > > line in ftrace README. Parse the same

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 09:49:11 +0900 Masami Hiramatsu wrote: > On Thu, 2 Mar 2017 23:25:06 +0530 > "Naveen N. Rao" wrote: > > > We indicate support for accepting sym+offset with kretprobes through a > > line in ftrace README. Parse the same to identify support and choose the > > appropriate

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 11:35:51 +0900 Masami Hiramatsu wrote: > On Sat, 4 Mar 2017 09:49:11 +0900 > Masami Hiramatsu wrote: > > > On Thu, 2 Mar 2017 23:25:06 +0530 > > "Naveen N. Rao" wrote: > > > > > We indicate support

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Sat, 4 Mar 2017 11:35:51 +0900 Masami Hiramatsu wrote: > On Sat, 4 Mar 2017 09:49:11 +0900 > Masami Hiramatsu wrote: > > > On Thu, 2 Mar 2017 23:25:06 +0530 > > "Naveen N. Rao" wrote: > > > > > We indicate support for accepting sym+offset with kretprobes through a > > > line in ftrace

[PATCH 1/3] USB: misc: ldusb: fixed decimal permission coding issue

Fixed ERROR: Use 4 digit octal (0777) not decimal permissions to fulfill the current coding-style. Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/usb/misc/ldusb.c

[PATCH 1/3] USB: misc: ldusb: fixed decimal permission coding issue

Fixed ERROR: Use 4 digit octal (0777) not decimal permissions to fulfill the current coding-style. Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/usb/misc/ldusb.c b/drivers/usb/misc/ldusb.c index

[PATCH 3/3] USB: misc: ldusb: Added Space after ',' to fit the coding style

Added a Space after ',' to get rid of an error message in checkpatch.pl and improve readability Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/misc/ldusb.c

[PATCH 3/3] USB: misc: ldusb: Added Space after ',' to fit the coding style

Added a Space after ',' to get rid of an error message in checkpatch.pl and improve readability Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/misc/ldusb.c b/drivers/usb/misc/ldusb.c index

[PATCH 0/3] fixed errors from checkpatch.pl

Changed multiple errors output from checkpatch.pl to enhance readability Milian Reichardt (3): USB: misc: ldusb: fixed decimal permission coding issue USB: misc: ldusb: changed '*' location to fit coding Style USB: misc: ldusb: Added Space after ',' to fit the coding style

[PATCH 2/3] USB: misc: ldusb: changed '*' location to fit coding Style

Changed the location of '*' to fit the current coding style and easy readability. Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/usb/misc/ldusb.c

[PATCH 0/3] fixed errors from checkpatch.pl

Changed multiple errors output from checkpatch.pl to enhance readability Milian Reichardt (3): USB: misc: ldusb: fixed decimal permission coding issue USB: misc: ldusb: changed '*' location to fit coding Style USB: misc: ldusb: Added Space after ',' to fit the coding style

[PATCH 2/3] USB: misc: ldusb: changed '*' location to fit coding Style

Changed the location of '*' to fit the current coding style and easy readability. Signed-of-by: Milian Reichardt --- drivers/usb/misc/ldusb.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/usb/misc/ldusb.c b/drivers/usb/misc/ldusb.c index

Re: [PATCH] staging, android: remove lowmemory killer from the tree

Hi all, I mentioned before that I had some ideas to overhaul lowmemorykiller, which would have the side effect of getting it out of the kernel. I've been working through some prototypes over the past few weeks (actually started before Michal sent his patch out), and I'd appreciate some feedback

Re: [PATCH] staging, android: remove lowmemory killer from the tree

Hi all, I mentioned before that I had some ideas to overhaul lowmemorykiller, which would have the side effect of getting it out of the kernel. I've been working through some prototypes over the past few weeks (actually started before Michal sent his patch out), and I'd appreciate some feedback

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

Hi Michael On Wed, Mar 01, 2017 at 09:10:40AM +0100, Micha?? K??pie?? wrote: > These patches should make fujitsu_init() a bit more palatable. No > changes are made to platform device code yet, for clarity these will be > posted in a separate series after this one gets applied. I have a

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

Hi Michael On Wed, Mar 01, 2017 at 09:10:40AM +0100, Micha?? K??pie?? wrote: > These patches should make fujitsu_init() a bit more palatable. No > changes are made to platform device code yet, for clarity these will be > posted in a separate series after this one gets applied. I have a

Re: [RFC PATCH v1 11/30] fs: new API for handling i_version

On Sat, 2017-03-04 at 10:55 +1100, NeilBrown wrote: > On Wed, Dec 21 2016, Jeff Layton wrote: > > > We already have inode_inc_iversion. Add inode_set_iversion, > > inode_get_iversion, inode_cmp_iversion and inode_iversion_need_inc. > > This list of added interfaces is incomplete. > And some of

Re: [RFC PATCH v1 11/30] fs: new API for handling i_version

On Sat, 2017-03-04 at 10:55 +1100, NeilBrown wrote: > On Wed, Dec 21 2016, Jeff Layton wrote: > > > We already have inode_inc_iversion. Add inode_set_iversion, > > inode_get_iversion, inode_cmp_iversion and inode_iversion_need_inc. > > This list of added interfaces is incomplete. > And some of

[PATCH] Staging: media: platform: bcm2835 - Style fix

Fixed style of block comments across whole driver Found using checkpatch Signed-off-by: Derek Robson --- .../media/platform/bcm2835/bcm2835-camera.c| 24 ++ drivers/staging/media/platform/bcm2835/controls.c | 22 +++-

[PATCH] Staging: media: platform: bcm2835 - Style fix

Fixed style of block comments across whole driver Found using checkpatch Signed-off-by: Derek Robson --- .../media/platform/bcm2835/bcm2835-camera.c| 24 ++ drivers/staging/media/platform/bcm2835/controls.c | 22 +++-

[PATCH v3] blkcg: allocate struct blkcg_gq outside request queue spinlock

blkg_conf_prep() currently calls blkg_lookup_create() while holding request queue spinlock. This means allocating memory for struct blkcg_gq has to be made non-blocking. This causes occasional -ENOMEM failures in call paths like below: pcpu_alloc+0x68f/0x710 __alloc_percpu_gfp+0xd/0x10

[PATCH v3] blkcg: allocate struct blkcg_gq outside request queue spinlock

blkg_conf_prep() currently calls blkg_lookup_create() while holding request queue spinlock. This means allocating memory for struct blkcg_gq has to be made non-blocking. This causes occasional -ENOMEM failures in call paths like below: pcpu_alloc+0x68f/0x710 __alloc_percpu_gfp+0xd/0x10

Re: [PATCH v3 0/3] Locality support for tpm_crb

Jarkko Sakkinen @ 2017-02-08 11:11 GMT: > The tpm_crb driver should follow the policy of reserving and > relinquishing the locality it uses when multiple localities are used, > like when TXT is another locality. > > [This is a resend of v3 as this has been asked from me for a few times > now

Re: [PATCH v3 0/3] Locality support for tpm_crb

Jarkko Sakkinen @ 2017-02-08 11:11 GMT: > The tpm_crb driver should follow the policy of reserving and > relinquishing the locality it uses when multiple localities are used, > like when TXT is another locality. > > [This is a resend of v3 as this has been asked from me for a few times > now

Re: [PATCH v3 0/3] Add support for MyGica T230C DVB-T2 stick

On 03/03/2017 08:35 PM, Brüns, Stefan wrote: On Fr, 2017-02-17 at 01:55 +0100, Stefan Brüns wrote: The required command sequence for the new tuner (Si2141) was traced from the current Windows driver and verified with a small python script/libusb. The changes to the Si2168 and dvbsky driver are

Re: [PATCH v3 0/3] Add support for MyGica T230C DVB-T2 stick

On 03/03/2017 08:35 PM, Brüns, Stefan wrote: On Fr, 2017-02-17 at 01:55 +0100, Stefan Brüns wrote: The required command sequence for the new tuner (Si2141) was traced from the current Windows driver and verified with a small python script/libusb. The changes to the Si2168 and dvbsky driver are

Re: [PATCH] uapi: fix asm/signal.h userspace compilation errors

On Thu, Mar 2, 2017 at 10:48 AM, Dmitry V. Levin wrote: > On Thu, Mar 02, 2017 at 10:22:18AM -0500, Carlos O'Donell wrote: >> On Wed, Mar 1, 2017 at 11:20 AM, Arnd Bergmann wrote: >> > On Sun, Feb 26, 2017 at 2:01 AM, Dmitry V. Levin wrote:

Re: [PATCH] uapi: fix asm/signal.h userspace compilation errors

On Thu, Mar 2, 2017 at 10:48 AM, Dmitry V. Levin wrote: > On Thu, Mar 02, 2017 at 10:22:18AM -0500, Carlos O'Donell wrote: >> On Wed, Mar 1, 2017 at 11:20 AM, Arnd Bergmann wrote: >> > On Sun, Feb 26, 2017 at 2:01 AM, Dmitry V. Levin wrote: >> >> Include (guarded by #ifndef __KERNEL__) to fix

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > This fixes type warnings generated by sparse, replaces instances of > ntohs() with be16_to_cpu() and removes unused fields in structs. There's no real need to convert ntohs to be16_to_cpu > diff --git

Re: [PATCH] staging: ks7010: clean up code

On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote: > This fixes type warnings generated by sparse, replaces instances of > ntohs() with be16_to_cpu() and removes unused fields in structs. There's no real need to convert ntohs to be16_to_cpu > diff --git

[GIT PULL] final round of SCSI updates for the 4.10+ merge window

This is the set of stuff that didn't quite make the initial pull and a set of fixes for stuff which did. The new stuff is basically lpfc (nvme), qedi and aacraid. The fixes cover a lot of previously submitted stuff, the most important of which probably covers some of the failing irq vectors

[GIT PULL] final round of SCSI updates for the 4.10+ merge window

This is the set of stuff that didn't quite make the initial pull and a set of fixes for stuff which did. The new stuff is basically lpfc (nvme), qedi and aacraid. The fixes cover a lot of previously submitted stuff, the most important of which probably covers some of the failing irq vectors

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Fri, 2017-03-03 at 18:00 -0500, J. Bruce Fields wrote: > On Wed, Dec 21, 2016 at 12:03:17PM -0500, Jeff Layton wrote: > > tl;dr: I think we can greatly reduce the cost of the inode->i_version > > counter, by exploiting the fact that we don't need to increment it > > if no one is looking at it.

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Fri, 2017-03-03 at 18:00 -0500, J. Bruce Fields wrote: > On Wed, Dec 21, 2016 at 12:03:17PM -0500, Jeff Layton wrote: > > tl;dr: I think we can greatly reduce the cost of the inode->i_version > > counter, by exploiting the fact that we don't need to increment it > > if no one is looking at it.

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Thu, 2 Mar 2017 23:25:06 +0530 "Naveen N. Rao" wrote: > We indicate support for accepting sym+offset with kretprobes through a > line in ftrace README. Parse the same to identify support and choose the > appropriate format for kprobe_events. Could you give

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel supports it

On Thu, 2 Mar 2017 23:25:06 +0530 "Naveen N. Rao" wrote: > We indicate support for accepting sym+offset with kretprobes through a > line in ftrace README. Parse the same to identify support and choose the > appropriate format for kprobe_events. Could you give us an example of this change here?

Re: [RFC PATCH v1 29/30] fs: track whether the i_version has been queried with an i_state flag

On Sat, 2017-03-04 at 11:03 +1100, NeilBrown wrote: > On Wed, Dec 21 2016, Jeff Layton wrote: > > > @@ -2072,7 +2093,12 @@ inode_cmp_iversion(const struct inode *inode, const > > u64 old) > > static inline bool > > inode_iversion_need_inc(struct inode *inode) > > { > > - return true; > > +

Re: [RFC PATCH v1 29/30] fs: track whether the i_version has been queried with an i_state flag

On Sat, 2017-03-04 at 11:03 +1100, NeilBrown wrote: > On Wed, Dec 21 2016, Jeff Layton wrote: > > > @@ -2072,7 +2093,12 @@ inode_cmp_iversion(const struct inode *inode, const > > u64 old) > > static inline bool > > inode_iversion_need_inc(struct inode *inode) > > { > > - return true; > > +

  1   2   3   4   5   6   7   8   9   10   >