Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

The question is how to provide a similar guarantee if a different way? As a tool to aid distro reviewers, modversions has some value, but the debug info parsing tools that have been mentioned in this thread seem superior (not that I've tested them). On the other hand the big advantage of

Re: [PATCH] pci-error-recover: doc cleanup

On 12/09/2016 02:44 PM, Linas Vepstas wrote: > On Fri, Dec 9, 2016 at 2:37 PM, Cao jin wrote: >> >> >> On 12/09/2016 02:24 PM, Linas Vepstas wrote: >>> I suppose I'm confused, but I recall that link resets are non-fatal. >>> Fatal errors typically require that the the

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

The question is how to provide a similar guarantee if a different way? As a tool to aid distro reviewers, modversions has some value, but the debug info parsing tools that have been mentioned in this thread seem superior (not that I've tested them). On the other hand the big advantage of

Re: [PATCH] pci-error-recover: doc cleanup

On 12/09/2016 02:44 PM, Linas Vepstas wrote: > On Fri, Dec 9, 2016 at 2:37 PM, Cao jin wrote: >> >> >> On 12/09/2016 02:24 PM, Linas Vepstas wrote: >>> I suppose I'm confused, but I recall that link resets are non-fatal. >>> Fatal errors typically require that the the pci adapter be completely

RE: [PATCH v10 1/6] drivers/platform/x86/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

> -Original Message- > From: linux-gpio-ow...@vger.kernel.org [mailto:linux-gpio- > ow...@vger.kernel.org] On Behalf Of Andy Shevchenko > Sent: Friday, November 11, 2016 12:07 AM > To: Tan, Jui Nee ; mika.westerb...@linux.intel.com; >

RE: [PATCH v10 1/6] drivers/platform/x86/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

> -Original Message- > From: linux-gpio-ow...@vger.kernel.org [mailto:linux-gpio- > ow...@vger.kernel.org] On Behalf Of Andy Shevchenko > Sent: Friday, November 11, 2016 12:07 AM > To: Tan, Jui Nee ; mika.westerb...@linux.intel.com; > heikki.kroge...@linux.intel.com; t...@linutronix.de;

[PATCH v2 2/8] power: supply: tps65217: Use 'poll_task' on unloading the module

TPS65217 has two interrupt numbers so checking single IRQ number is not appropriate when the module is removed. Use the task_struct variable for running polling thread. If polling task is activated, then use it to stop running thread. Signed-off-by: Milo Kim ---

[PATCH v2 7/8] power: supply: tps65217: Use generic name for get_property()

Rename it as tps65217_charger_get_property(). Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c b/drivers/power/supply/tps65217_charger.c

[PATCH v2 5/8] power: supply: tps65217: Use generic name for power supply structure

Replace 'ac' of tps65217_charger structure with 'psy'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c

[PATCH v2 2/8] power: supply: tps65217: Use 'poll_task' on unloading the module

TPS65217 has two interrupt numbers so checking single IRQ number is not appropriate when the module is removed. Use the task_struct variable for running polling thread. If polling task is activated, then use it to stop running thread. Signed-off-by: Milo Kim ---

[PATCH v2 7/8] power: supply: tps65217: Use generic name for get_property()

Rename it as tps65217_charger_get_property(). Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c b/drivers/power/supply/tps65217_charger.c index 79afeca..63c5556

[PATCH v2 5/8] power: supply: tps65217: Use generic name for power supply structure

Replace 'ac' of tps65217_charger structure with 'psy'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c b/drivers/power/supply/tps65217_charger.c index

[PATCH v2 0/8] power: supply: tps65217: Support USB charger feature

TPS65217 device supports two charger inputs - AC and USB. Currently, only AC charger is supported. This patch-set adds USB charger feature. Tested on Beaglebone black. Patch 1: Main patch Patch 2, 3: Clean up for charger driver data Patch 4 ~ 8: Naming changes for generic power supply class

[PATCH v2 8/8] power: supply: tps65217: Use generic charger name

"tps65217-charger" is more appropriate name because the driver supports not only AC but also USB charger. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 0/8] power: supply: tps65217: Support USB charger feature

TPS65217 device supports two charger inputs - AC and USB. Currently, only AC charger is supported. This patch-set adds USB charger feature. Tested on Beaglebone black. Patch 1: Main patch Patch 2, 3: Clean up for charger driver data Patch 4 ~ 8: Naming changes for generic power supply class

[PATCH v2 8/8] power: supply: tps65217: Use generic charger name

"tps65217-charger" is more appropriate name because the driver supports not only AC but also USB charger. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/power/supply/tps65217_charger.c

[PATCH v2 1/8] power: supply: tps65217: Support USB charger interrupt

TPS65217 has two charger interrupts - AC or USB power status change. Interrupt handler: Check not only AC but also USB charger status. In both cases, enable charging operation. Interrupt request: If an interrupt number is invalid, then use legacy polling thread. Otherwise, create IRQ

[PATCH v2 4/8] power: supply: tps65217: Use generic name for charger online

This driver supports AC and USB chargers. Generic name is preferred. Replace 'ac_online' with 'online'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH v2 3/8] power: supply: tps65217: Remove IRQ data from driver data

IRQ number is only used on requesting the interrupt, so no need to keep it inside the driver data. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c

[PATCH v2 6/8] power: supply: tps65217: Use generic name for power supply property

Replace 'ac_props' with 'charger_props'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c b/drivers/power/supply/tps65217_charger.c index

[PATCH v2 1/8] power: supply: tps65217: Support USB charger interrupt

TPS65217 has two charger interrupts - AC or USB power status change. Interrupt handler: Check not only AC but also USB charger status. In both cases, enable charging operation. Interrupt request: If an interrupt number is invalid, then use legacy polling thread. Otherwise, create IRQ

[PATCH v2 4/8] power: supply: tps65217: Use generic name for charger online

This driver supports AC and USB chargers. Generic name is preferred. Replace 'ac_online' with 'online'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH v2 3/8] power: supply: tps65217: Remove IRQ data from driver data

IRQ number is only used on requesting the interrupt, so no need to keep it inside the driver data. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c

[PATCH v2 6/8] power: supply: tps65217: Use generic name for power supply property

Replace 'ac_props' with 'charger_props'. Signed-off-by: Milo Kim --- drivers/power/supply/tps65217_charger.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/power/supply/tps65217_charger.c b/drivers/power/supply/tps65217_charger.c index 5daf361..79afeca 100644

Re: [PATCH] vfio/pci: Support error recovery

On 12/09/2016 12:30 AM, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 10:46:59PM +0800, Cao jin wrote: >> >> >> On 12/06/2016 11:35 PM, Alex Williamson wrote: >>> On Tue, 6 Dec 2016 18:46:04 +0800 >>> Cao jin wrote: >>> On 12/06/2016 12:59 PM, Alex

Re: [PATCH] vfio/pci: Support error recovery

On 12/09/2016 12:30 AM, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 10:46:59PM +0800, Cao jin wrote: >> >> >> On 12/06/2016 11:35 PM, Alex Williamson wrote: >>> On Tue, 6 Dec 2016 18:46:04 +0800 >>> Cao jin wrote: >>> On 12/06/2016 12:59 PM, Alex Williamson wrote: > On Tue, 6

Re: [PATCH] vfio/pci: Support error recovery

On 12/08/2016 10:46 PM, Cao jin wrote: > > > On 12/06/2016 11:35 PM, Alex Williamson wrote: >> On Tue, 6 Dec 2016 18:46:04 +0800 >> Cao jin wrote: >> >>> On 12/06/2016 12:59 PM, Alex Williamson wrote: On Tue, 6 Dec 2016 05:55:28 +0200 "Michael S. Tsirkin"

Re: [PATCH] pci-error-recover: doc cleanup

On 12/09/2016 02:24 PM, Linas Vepstas wrote: > I suppose I'm confused, but I recall that link resets are non-fatal. > Fatal errors typically require that the the pci adapter be completely > reset, any adapter firmware to be reloaded from scratch, the device > driver has to kill all device state

Re: [PATCH] pci-error-recover: doc cleanup

On 12/09/2016 02:24 PM, Linas Vepstas wrote: > I suppose I'm confused, but I recall that link resets are non-fatal. > Fatal errors typically require that the the pci adapter be completely > reset, any adapter firmware to be reloaded from scratch, the device > driver has to kill all device state

Re: [PATCH] vfio/pci: Support error recovery

On 12/08/2016 10:46 PM, Cao jin wrote: > > > On 12/06/2016 11:35 PM, Alex Williamson wrote: >> On Tue, 6 Dec 2016 18:46:04 +0800 >> Cao jin wrote: >> >>> On 12/06/2016 12:59 PM, Alex Williamson wrote: On Tue, 6 Dec 2016 05:55:28 +0200 "Michael S. Tsirkin" wrote: > On

[git pull] single drm fix

Hi Linus, Just a single fix for amdgpu to just suspend the gpu on "shutdown" instead of shutting it down fully, as for some reason the hw was getting upset in some situations. Dave. The following changes since commit 3e5de27e940d00d8d504dfb96625fb654f641509: Linux 4.9-rc8 (2016-12-04

[git pull] single drm fix

Hi Linus, Just a single fix for amdgpu to just suspend the gpu on "shutdown" instead of shutting it down fully, as for some reason the hw was getting upset in some situations. Dave. The following changes since commit 3e5de27e940d00d8d504dfb96625fb654f641509: Linux 4.9-rc8 (2016-12-04

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On Thu, Dec 8, 2016 at 11:09 PM, Chen Yu wrote: > On 2016/12/9 7:29, John Youn wrote: >> On 12/8/2016 2:43 PM, John Stultz wrote: >>> On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote: On 12/6/2016 5:48 PM, John Stultz wrote: > This patch works

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On Thu, Dec 8, 2016 at 11:09 PM, Chen Yu wrote: > On 2016/12/9 7:29, John Youn wrote: >> On 12/8/2016 2:43 PM, John Stultz wrote: >>> On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote: On 12/6/2016 5:48 PM, John Stultz wrote: > This patch works around the issue by re-reading the GOTGCTL

Re: [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers

On Fri, Dec 09, 2016 at 12:05:53AM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Thursday, December 8, 2016 7:56 AM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org;

Re: [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers

On Fri, Dec 09, 2016 at 12:05:53AM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Thursday, December 8, 2016 7:56 AM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > >

Re: [V9fs-developer] [PATCH 2/5] 9p: store req details and callback in struct p9_req_t

Nice. I like the idea of async I/Os :) Stefano Stabellini wrote on Thu, Dec 08, 2016: > Add a few fields to struct p9_req_t. Callback is the function which will > be called upon requestion completion. offset, rsize, pagevec and kiocb > store important information regarding the read or write

Re: [V9fs-developer] [PATCH 2/5] 9p: store req details and callback in struct p9_req_t

Nice. I like the idea of async I/Os :) Stefano Stabellini wrote on Thu, Dec 08, 2016: > Add a few fields to struct p9_req_t. Callback is the function which will > be called upon requestion completion. offset, rsize, pagevec and kiocb > store important information regarding the read or write

Re: [V9fs-developer] [PATCH 4/5] 9p: introduce async read requests

Stefano Stabellini wrote on Thu, Dec 08, 2016: > If the read is an async operation, send a 9p request and return > EIOCBQUEUED. Do not wait for completion. > > Complete the read operation from a callback instead. > > Signed-off-by: Stefano Stabellini > --- >

Re: [V9fs-developer] [PATCH 4/5] 9p: introduce async read requests

Stefano Stabellini wrote on Thu, Dec 08, 2016: > If the read is an async operation, send a 9p request and return > EIOCBQUEUED. Do not wait for completion. > > Complete the read operation from a callback instead. > > Signed-off-by: Stefano Stabellini > --- > net/9p/client.c | 88 >

Re: uvcvideo logging kernel warnings on device disconnect

On Fri, Dec 09, 2016 at 01:09:21AM +0200, Laurent Pinchart wrote: > Hi Dave, > > (CC'ing LKML and Greg KH) > > On Thursday 08 Dec 2016 12:31:55 Dave Stevenson wrote: > > Hi All. > > > > I'm working with a USB webcam which has been seen to spontaneously > > disconnect when in use. That's a

Re: uvcvideo logging kernel warnings on device disconnect

On Fri, Dec 09, 2016 at 01:09:21AM +0200, Laurent Pinchart wrote: > Hi Dave, > > (CC'ing LKML and Greg KH) > > On Thursday 08 Dec 2016 12:31:55 Dave Stevenson wrote: > > Hi All. > > > > I'm working with a USB webcam which has been seen to spontaneously > > disconnect when in use. That's a

Re: [PATCH] tracing: (backport) Replace kmap with copy_from_user() in trace_marker

On Fri, Dec 09, 2016 at 07:34:04AM +0100, Henrik Austad wrote: > Instead of using get_user_pages_fast() and kmap_atomic() when writing > to the trace_marker file, just allocate enough space on the ring buffer > directly, and write into it via copy_from_user(). > > Writing into the trace_marker

Re: [PATCH] tracing: (backport) Replace kmap with copy_from_user() in trace_marker

On Fri, Dec 09, 2016 at 07:34:04AM +0100, Henrik Austad wrote: > Instead of using get_user_pages_fast() and kmap_atomic() when writing > to the trace_marker file, just allocate enough space on the ring buffer > directly, and write into it via copy_from_user(). > > Writing into the trace_marker

Re: [PATCH v2] USB: OHCI: pxa27x:fix warnings and error

On Thu, Dec 08, 2016 at 10:30:35PM +, manju goudar wrote: > > > On Thu, Dec 8, 2016 at 4:49 PM, Greg Kroah-Hartman > > wrote: > > On Wed, Dec 07, 2016 at 11:37:45PM +, csmanjuvi...@gmail.com wrote: > > From: Manjunath Goudar

Re: [PATCH v2] USB: OHCI: pxa27x:fix warnings and error

On Thu, Dec 08, 2016 at 10:30:35PM +, manju goudar wrote: > > > On Thu, Dec 8, 2016 at 4:49 PM, Greg Kroah-Hartman > > wrote: > > On Wed, Dec 07, 2016 at 11:37:45PM +, csmanjuvi...@gmail.com wrote: > > From: Manjunath Goudar > > > > This patch will fix the

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/2016 at 01:13 PM, zhong jiang wrote: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> >>> A soft lookup will occur when I run trinity in syscall kexec_load. >>> the corresponding stack information is

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/2016 at 01:13 PM, zhong jiang wrote: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> >>> A soft lookup will occur when I run trinity in syscall kexec_load. >>> the corresponding stack information is as follows. >>> >>> [

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On 2016/12/9 7:29, John Youn wrote: > On 12/8/2016 2:43 PM, John Stultz wrote: >> On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote: >>> On 12/6/2016 5:48 PM, John Stultz wrote: Hey John, Just wanted to send this by you, as it seems something is slightly

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On 2016/12/9 7:29, John Youn wrote: > On 12/8/2016 2:43 PM, John Stultz wrote: >> On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote: >>> On 12/6/2016 5:48 PM, John Stultz wrote: Hey John, Just wanted to send this by you, as it seems something is slightly off with the GOTGCTL

Re: [PATCH v3 1/9] staging: fsl-mc: move bus driver out of staging

On Fri, Dec 09, 2016 at 12:36:26AM +, Stuart Yoder wrote: > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Thursday, December 08, 2016 10:05 AM > > To: Stuart Yoder > > Cc: de...@driverdev.osuosl.org; ag...@suse.de;

Re: [PATCH v3 1/9] staging: fsl-mc: move bus driver out of staging

On Fri, Dec 09, 2016 at 12:36:26AM +, Stuart Yoder wrote: > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Thursday, December 08, 2016 10:05 AM > > To: Stuart Yoder > > Cc: de...@driverdev.osuosl.org; ag...@suse.de; a...@arndb.de; > >

Re: Still OOM problems with 4.9er kernels

Hello, same with latest kernel rc, dnf still killed with OOM (but sometimes better). ./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS} (does dnf clean all;dnf update) Linux database.intern 4.9.0-0.rc8.git2.1.fc26.x86_64 #1 SMP Wed Dec 7 17:53:29 UTC 2016 x86_64

Re: Still OOM problems with 4.9er kernels

Hello, same with latest kernel rc, dnf still killed with OOM (but sometimes better). ./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS} (does dnf clean all;dnf update) Linux database.intern 4.9.0-0.rc8.git2.1.fc26.x86_64 #1 SMP Wed Dec 7 17:53:29 UTC 2016 x86_64

Re: [PATCH] Staging: ks7010: ks7010_sdio.h: Fixed coding style errors

On Fri, Dec 09, 2016 at 12:29:21PM +, Manoj Sawai wrote: > Errors - Complex macro not a parentheses and trailing whitespace > Also fixed other small checkpatch warnings and checks. If you ever say "also" in a changelog, that's a huge hint that the patch needs to be broken up into multiple

Re: [PATCH] Staging: ks7010: ks7010_sdio.h: Fixed coding style errors

On Fri, Dec 09, 2016 at 12:29:21PM +, Manoj Sawai wrote: > Errors - Complex macro not a parentheses and trailing whitespace > Also fixed other small checkpatch warnings and checks. If you ever say "also" in a changelog, that's a huge hint that the patch needs to be broken up into multiple

Re: Tearing down DMA transfer setup after DMA client has finished

On Thu, Dec 08, 2016 at 04:48:18PM +, Måns Rullgård wrote: > Vinod Koul writes: > > > To make it efficient, disregarding your Sbox HW issue, the solution is > > virtual channels. You can delink physical channels and virtual channels. If > > one has SW controlled MUX

Re: Tearing down DMA transfer setup after DMA client has finished

On Thu, Dec 08, 2016 at 04:48:18PM +, Måns Rullgård wrote: > Vinod Koul writes: > > > To make it efficient, disregarding your Sbox HW issue, the solution is > > virtual channels. You can delink physical channels and virtual channels. If > > one has SW controlled MUX then a channel can

[PATCH] Staging: ks7010: ks7010_sdio.h: Fixed coding style errors

Errors - Complex macro not a parentheses and trailing whitespace Also fixed other small checkpatch warnings and checks. Signed-off-by: Manoj Sawai --- drivers/staging/ks7010/ks7010_sdio.h | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git

[PATCH] Staging: ks7010: ks7010_sdio.h: Fixed coding style errors

Errors - Complex macro not a parentheses and trailing whitespace Also fixed other small checkpatch warnings and checks. Signed-off-by: Manoj Sawai --- drivers/staging/ks7010/ks7010_sdio.h | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git

Re: netlink: GPF in sock_sndtimeo

On Thu, Dec 8, 2016 at 10:02 PM, Richard Guy Briggs wrote: > I also tried to extend Cong Wang's idea to attempt to proactively respond to a > NETLINK_URELEASE on the audit_sock and reset it, but ran into a locking error > stack dump using mutex_lock(_cmd_mutex) in the notifier

Re: netlink: GPF in sock_sndtimeo

On Thu, Dec 8, 2016 at 10:02 PM, Richard Guy Briggs wrote: > I also tried to extend Cong Wang's idea to attempt to proactively respond to a > NETLINK_URELEASE on the audit_sock and reset it, but ran into a locking error > stack dump using mutex_lock(_cmd_mutex) in the notifier callback. >

[PATCH] firmware: dmi_scan: Always show system identification string

Let's keep consistent when print dmi_ids_string between SMBIOS 2.x and SMBIOS 3.x, and always show the system identification string, like Vendor, Product/Board name and BIOS infos. Signed-off-by: Kefeng Wang --- drivers/firmware/dmi_scan.c | 4 ++-- 1 file changed, 2

[PATCH] firmware: dmi_scan: Always show system identification string

Let's keep consistent when print dmi_ids_string between SMBIOS 2.x and SMBIOS 3.x, and always show the system identification string, like Vendor, Product/Board name and BIOS infos. Signed-off-by: Kefeng Wang --- drivers/firmware/dmi_scan.c | 4 ++-- 1 file changed, 2 insertions(+), 2

RE: ATH9 driver issues on ARM64

Sorry, Forgot to add kernel version, we are using 4.6 kernel. > Hi, > Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. > It might help us to debug issue further. > > Thanks & Regards, > Bharat > > > > > [+cc Kalle, ath9k list] > > > > Thanks, but please also CC

RE: ATH9 driver issues on ARM64

Sorry, Forgot to add kernel version, we are using 4.6 kernel. > Hi, > Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. > It might help us to debug issue further. > > Thanks & Regards, > Bharat > > > > > [+cc Kalle, ath9k list] > > > > Thanks, but please also CC

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

On Fri 09-12-16 06:38:04, Al Viro wrote: > On Fri, Dec 09, 2016 at 07:22:25AM +0100, Michal Hocko wrote: > > > > Easier to handle those in vmalloc() itself. > > > > I think there were some attempts in the past but some of the code paths > > are burried too deep and adding gfp_mask all the way

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

On Fri 09-12-16 06:38:04, Al Viro wrote: > On Fri, Dec 09, 2016 at 07:22:25AM +0100, Michal Hocko wrote: > > > > Easier to handle those in vmalloc() itself. > > > > I think there were some attempts in the past but some of the code paths > > are burried too deep and adding gfp_mask all the way

Re: [PATCH] pci-error-recover: doc cleanup

On 09/12/16 17:24, Linas Vepstas wrote: I suppose I'm confused, but I recall that link resets are non-fatal. Fatal errors typically require that the the pci adapter be completely reset, any adapter firmware to be reloaded from scratch, the device driver has to kill all device state and start

Re: [PATCH] pci-error-recover: doc cleanup

On 09/12/16 17:24, Linas Vepstas wrote: I suppose I'm confused, but I recall that link resets are non-fatal. Fatal errors typically require that the the pci adapter be completely reset, any adapter firmware to be reloaded from scratch, the device driver has to kill all device state and start

Re: [PATCH 4/7] blk-flush: run the queue when inserting blk-mq flush

On 12/08/2016 09:13 PM, Jens Axboe wrote: Currently we pass in to run the queue async, but don't flag the queue to be run. We don't need to run it async here, but we should run it. So fixup the parameters. Signed-off-by: Jens Axboe --- block/blk-flush.c | 2 +- 1 file changed, 1

Re: [PATCH 4/7] blk-flush: run the queue when inserting blk-mq flush

On 12/08/2016 09:13 PM, Jens Axboe wrote: Currently we pass in to run the queue async, but don't flag the queue to be run. We don't need to run it async here, but we should run it. So fixup the parameters. Signed-off-by: Jens Axboe --- block/blk-flush.c | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH 2/7] blk-mq: abstract out blk_mq_dispatch_rq_list() helper

On 12/08/2016 09:13 PM, Jens Axboe wrote: Takes a list of requests, and dispatches it. Moves any residual requests to the dispatch list. Signed-off-by: Jens Axboe --- block/blk-mq.c | 85 -- block/blk-mq.h | 1 + 2 files

Re: [PATCH 2/7] blk-mq: abstract out blk_mq_dispatch_rq_list() helper

On 12/08/2016 09:13 PM, Jens Axboe wrote: Takes a list of requests, and dispatches it. Moves any residual requests to the dispatch list. Signed-off-by: Jens Axboe --- block/blk-mq.c | 85 -- block/blk-mq.h | 1 + 2 files changed, 48

Re: [PATCH 3/7] elevator: make the rqhash helpers exported

On 12/08/2016 09:13 PM, Jens Axboe wrote: Signed-off-by: Jens Axboe --- block/elevator.c | 8 include/linux/elevator.h | 5 + 2 files changed, 9 insertions(+), 4 deletions(-) Reviewed-by: Hannes Reinecke Cheers, Hannes -- Dr. Hannes

Re: [PATCH] pci-error-recover: doc cleanup

On Fri, Dec 9, 2016 at 2:37 PM, Cao jin wrote: > > > On 12/09/2016 02:24 PM, Linas Vepstas wrote: >> I suppose I'm confused, but I recall that link resets are non-fatal. >> Fatal errors typically require that the the pci adapter be completely >> reset, any adapter

Re: [PATCH 3/7] elevator: make the rqhash helpers exported

On 12/08/2016 09:13 PM, Jens Axboe wrote: Signed-off-by: Jens Axboe --- block/elevator.c | 8 include/linux/elevator.h | 5 + 2 files changed, 9 insertions(+), 4 deletions(-) Reviewed-by: Hannes Reinecke Cheers, Hannes -- Dr. Hannes ReineckeTeamlead

Re: [PATCH] pci-error-recover: doc cleanup

On Fri, Dec 9, 2016 at 2:37 PM, Cao jin wrote: > > > On 12/09/2016 02:24 PM, Linas Vepstas wrote: >> I suppose I'm confused, but I recall that link resets are non-fatal. >> Fatal errors typically require that the the pci adapter be completely >> reset, any adapter firmware to be reloaded from

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Dec 08, 2016 at 10:32:00PM -0800, Cong Wang wrote: > > Why do we do autobind there, anyway, and why is it conditional on > > SOCK_PASSCRED? Note that e.g. for SOCK_STREAM we can bloody well get > > to sending stuff without autobind ever done - just use socketpair() > > to create that

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Dec 08, 2016 at 10:32:00PM -0800, Cong Wang wrote: > > Why do we do autobind there, anyway, and why is it conditional on > > SOCK_PASSCRED? Note that e.g. for SOCK_STREAM we can bloody well get > > to sending stuff without autobind ever done - just use socketpair() > > to create that

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

Hi Mike/Bart, On 12/8/16, 8:17 AM, "virtualization-boun...@lists.linux-foundation.org on behalf of Michael S. Tsirkin" wrote: >On Thu, Dec 08, 2016 at 06:38:11AM +, Bart Van Assche wrote: >> On

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

Hi Mike/Bart, On 12/8/16, 8:17 AM, "virtualization-boun...@lists.linux-foundation.org on behalf of Michael S. Tsirkin" wrote: >On Thu, Dec 08, 2016 at 06:38:11AM +, Bart Van Assche wrote: >> On 12/07/16 21:54, Michael S. Tsirkin wrote: >> > On Thu, Dec 08, 2016 at 05:21:47AM +,

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

On Fri, Dec 09, 2016 at 06:26:38AM +0100, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 08:49:39PM -, Thomas Gleixner wrote: > > > +static inline u64 timekeeping_delta_to_ns(struct tk_read_base *tkr, u64 > > delta) > > +{ > > + u32 dh, dl; > > + u64 nsec; > > + > > + dl = delta; > >

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

On Fri, Dec 09, 2016 at 06:26:38AM +0100, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 08:49:39PM -, Thomas Gleixner wrote: > > > +static inline u64 timekeeping_delta_to_ns(struct tk_read_base *tkr, u64 > > delta) > > +{ > > + u32 dh, dl; > > + u64 nsec; > > + > > + dl = delta; > >

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

On Fri, Dec 09, 2016 at 07:22:25AM +0100, Michal Hocko wrote: > > Easier to handle those in vmalloc() itself. > > I think there were some attempts in the past but some of the code paths > are burried too deep and adding gfp_mask all the way down there seemed > like a major surgery. No need to

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

On Fri, Dec 09, 2016 at 07:22:25AM +0100, Michal Hocko wrote: > > Easier to handle those in vmalloc() itself. > > I think there were some attempts in the past but some of the code paths > are burried too deep and adding gfp_mask all the way down there seemed > like a major surgery. No need to

[PATCH] tracing: (backport) Replace kmap with copy_from_user() in trace_marker

Instead of using get_user_pages_fast() and kmap_atomic() when writing to the trace_marker file, just allocate enough space on the ring buffer directly, and write into it via copy_from_user(). Writing into the trace_marker file use to allocate a temporary buffer to perform the copy_from_user(), as

[PATCH] tracing: (backport) Replace kmap with copy_from_user() in trace_marker

Instead of using get_user_pages_fast() and kmap_atomic() when writing to the trace_marker file, just allocate enough space on the ring buffer directly, and write into it via copy_from_user(). Writing into the trace_marker file use to allocate a temporary buffer to perform the copy_from_user(), as

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Dec 8, 2016 at 5:32 PM, Al Viro wrote: > On Thu, Dec 08, 2016 at 04:08:27PM -0800, Cong Wang wrote: >> On Thu, Dec 8, 2016 at 8:30 AM, Dmitry Vyukov wrote: >> > Chain exists of: >> > Possible unsafe locking scenario: >> > >> >CPU0

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Dec 8, 2016 at 5:32 PM, Al Viro wrote: > On Thu, Dec 08, 2016 at 04:08:27PM -0800, Cong Wang wrote: >> On Thu, Dec 8, 2016 at 8:30 AM, Dmitry Vyukov wrote: >> > Chain exists of: >> > Possible unsafe locking scenario: >> > >> >CPU0CPU1 >> >

[PATCH 4/4] dt-bindings: input: Specify the interrupt number of TPS65217 power button

Specify the power button interrupt number which is from the datasheet. Signed-off-by: Milo Kim --- Documentation/devicetree/bindings/input/tps65218-pwrbutton.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH 3/4] dt-bindings: power/supply: Update TPS65217 properties

Add interrupt specifiers for USB and AC charger input. Interrupt numbers are from the datasheet. Fix wrong property for compatible string. Signed-off-by: Milo Kim --- .../devicetree/bindings/power/supply/tps65217_charger.txt | 7 ++- 1 file changed, 6

[PATCH 4/4] dt-bindings: input: Specify the interrupt number of TPS65217 power button

Specify the power button interrupt number which is from the datasheet. Signed-off-by: Milo Kim --- Documentation/devicetree/bindings/input/tps65218-pwrbutton.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/input/tps65218-pwrbutton.txt

[PATCH 3/4] dt-bindings: power/supply: Update TPS65217 properties

Add interrupt specifiers for USB and AC charger input. Interrupt numbers are from the datasheet. Fix wrong property for compatible string. Signed-off-by: Milo Kim --- .../devicetree/bindings/power/supply/tps65217_charger.txt | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-)

[PATCH 2/4] dt-bindings: mfd: Remove TPS65217 interrupts

Interrupt numbers are from the datasheet, so no need to keep them in the ABI. Use the number in the DT file. Signed-off-by: Milo Kim --- arch/arm/boot/dts/am335x-bone-common.dtsi | 8 +++- include/dt-bindings/mfd/tps65217.h| 26 -- 2

[PATCH 1/4] ARM: dts: am335x: Fix the interrupt name of TPS65217

Use 'interrupt-names' for getting the charger interrupt number. Fixes: 1934e89a769b ("ARM: dts: am335x: Add the charger interrupt") Signed-off-by: Milo Kim --- arch/arm/boot/dts/am335x-bone-common.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 0/4] dt-bindings: mfd: Update TPS65217 interrupts

This patch-set fixes wrong property name and uses TPS65217 HW interrupt number from the datasheet instead of the DT ABI. DT bindings are also updated. Milo Kim (4): ARM: dts: am335x: Fix the interrupt name of TPS65217 dt-bindings: mfd: Remove TPS65217 interrupts dt-bindings: power/supply:

[PATCH 2/4] dt-bindings: mfd: Remove TPS65217 interrupts

Interrupt numbers are from the datasheet, so no need to keep them in the ABI. Use the number in the DT file. Signed-off-by: Milo Kim --- arch/arm/boot/dts/am335x-bone-common.dtsi | 8 +++- include/dt-bindings/mfd/tps65217.h| 26 -- 2 files changed, 3

[PATCH 1/4] ARM: dts: am335x: Fix the interrupt name of TPS65217

Use 'interrupt-names' for getting the charger interrupt number. Fixes: 1934e89a769b ("ARM: dts: am335x: Add the charger interrupt") Signed-off-by: Milo Kim --- arch/arm/boot/dts/am335x-bone-common.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 0/4] dt-bindings: mfd: Update TPS65217 interrupts

This patch-set fixes wrong property name and uses TPS65217 HW interrupt number from the datasheet instead of the DT ABI. DT bindings are also updated. Milo Kim (4): ARM: dts: am335x: Fix the interrupt name of TPS65217 dt-bindings: mfd: Remove TPS65217 interrupts dt-bindings: power/supply:

  1   2   3   4   5   6   7   8   9   10   >