Re: [PATCH v2] perf/sdt: Show proper hint

* Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 03, 2017 at 03:56:42PM +0530, Ravi Bangoria escreveu: > > After patch: > > $ perf record -a -e sdt_glib:idle__add > > event syntax error: 'sdt_glib:idle__add' > > \___ unknown tracepoint > > > >

Re: [PATCH v2] perf/sdt: Show proper hint

* Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 03, 2017 at 03:56:42PM +0530, Ravi Bangoria escreveu: > > After patch: > > $ perf record -a -e sdt_glib:idle__add > > event syntax error: 'sdt_glib:idle__add' > > \___ unknown tracepoint > > > > Error: File

Re: [PATCH 3/7] efi: Add SHIM and image security database GUID definitions

* Ard Biesheuvel wrote: > From: David Howells > > Add the definitions for shim and image security database, both of which > are used widely in various Linux distros. > > Signed-off-by: Josh Boyer > Signed-off-by:

Re: [PATCH 3/7] efi: Add SHIM and image security database GUID definitions

* Ard Biesheuvel wrote: > From: David Howells > > Add the definitions for shim and image security database, both of which > are used widely in various Linux distros. > > Signed-off-by: Josh Boyer > Signed-off-by: David Howells > Cc: Matt Fleming > Signed-off-by: Ard Biesheuvel That's

Re: [PATCH V3 3/4] arch/powerpc: Implement Optprobes

On 2017/02/07 10:05AM, Masami Hiramatsu wrote: > On Sat, 4 Feb 2017 01:09:49 +0530 > "Naveen N. Rao" wrote: > > > Hi Michael, > > Thanks for the review! I'll defer to Anju on most of the aspects, but... > > > > On 2017/02/01 09:53PM, Michael Ellerman wrote: > >

Re: [PATCH V3 3/4] arch/powerpc: Implement Optprobes

On 2017/02/07 10:05AM, Masami Hiramatsu wrote: > On Sat, 4 Feb 2017 01:09:49 +0530 > "Naveen N. Rao" wrote: > > > Hi Michael, > > Thanks for the review! I'll defer to Anju on most of the aspects, but... > > > > On 2017/02/01 09:53PM, Michael Ellerman wrote: > > > Anju T Sudhakar writes: > > >

[PATCH] vhost: try avoiding avail index access when getting descriptor

If last avail idx is not equal to cached avail idx, we're sure there's still available buffers in the virtqueue so there's no need to re-read avail idx. So let's skip this to avoid unnecessary userspace memory access and memory barrier. Pktgen test show about 3% improvement on rx pps.

[PATCH] vhost: try avoiding avail index access when getting descriptor

If last avail idx is not equal to cached avail idx, we're sure there's still available buffers in the virtqueue so there's no need to re-read avail idx. So let's skip this to avoid unnecessary userspace memory access and memory barrier. Pktgen test show about 3% improvement on rx pps.

Re: [PATCH tip/master] tracing/probes: Fix a warning message to show correct maximum length

* Masami Hiramatsu wrote: > Since tracing/*probe_events will accept a probe definition > up to 4096 - 2 ('\n' and '\0') bytes, it must show 4094 instead > of 4096 in warning message. > > Signed-off-by: Masami Hiramatsu > --- >

Re: [PATCH tip/master] tracing/probes: Fix a warning message to show correct maximum length

* Masami Hiramatsu wrote: > Since tracing/*probe_events will accept a probe definition > up to 4096 - 2 ('\n' and '\0') bytes, it must show 4094 instead > of 4096 in warning message. > > Signed-off-by: Masami Hiramatsu > --- > kernel/trace/trace_probe.c |3 ++- > 1 file changed, 2

[PATCH] [media] mtk-vcodec: fix build errors without DEBUG

Fix build errors after removing DEBUG definition. Signed-off-by: Minghsiu Tsai --- drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 9 - drivers/media/platform/mtk-vcodec/vdec_vpu_if.c| 5 ++--- drivers/media/platform/mtk-vcodec/venc_vpu_if.c| 4

[PATCH] [media] mtk-vcodec: fix build errors without DEBUG

Fix build errors after removing DEBUG definition. Signed-off-by: Minghsiu Tsai --- drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 9 - drivers/media/platform/mtk-vcodec/vdec_vpu_if.c| 5 ++--- drivers/media/platform/mtk-vcodec/venc_vpu_if.c| 4 +--- 3 files changed, 7

Re: [PATCHv2 1/2] arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common

On Mon 2017-02-06 10:47:45, Laura Abbott wrote: > On 02/03/2017 01:08 PM, Kees Cook wrote: > > On Fri, Feb 3, 2017 at 12:29 PM, Russell King - ARM Linux > > wrote: > >> On Fri, Feb 03, 2017 at 11:45:56AM -0800, Kees Cook wrote: > >>> On Fri, Feb 3, 2017 at 9:52 AM, Laura

Re: [PATCHv2 1/2] arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common

On Mon 2017-02-06 10:47:45, Laura Abbott wrote: > On 02/03/2017 01:08 PM, Kees Cook wrote: > > On Fri, Feb 3, 2017 at 12:29 PM, Russell King - ARM Linux > > wrote: > >> On Fri, Feb 03, 2017 at 11:45:56AM -0800, Kees Cook wrote: > >>> On Fri, Feb 3, 2017 at 9:52 AM, Laura Abbott wrote: >

[PATCH v4 2/2] perf tools: Add missing newline in debug messages

These two debug messages are missing the trailing newline. Signed-off-by: He Kuang --- tools/perf/util/bpf-loader.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c index 36c8611..bc6bc70

[PATCH v4 2/2] perf tools: Add missing newline in debug messages

These two debug messages are missing the trailing newline. Signed-off-by: He Kuang --- tools/perf/util/bpf-loader.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c index 36c8611..bc6bc70 100644 ---

[PATCH v4 1/2] perf tools arm64: Add support for generating bpf prologue

Since HAVE_KPROBES can be enabled in arm64, this patch introduces regs_query_register_offset() to convert register name to offset for arm64, so the BPF prologue feature is ready to use. Signed-off-by: He Kuang --- tools/perf/arch/arm64/Makefile | 1 +

[PATCH v4 1/2] perf tools arm64: Add support for generating bpf prologue

Since HAVE_KPROBES can be enabled in arm64, this patch introduces regs_query_register_offset() to convert register name to offset for arm64, so the BPF prologue feature is ready to use. Signed-off-by: He Kuang --- tools/perf/arch/arm64/Makefile | 1 +

Re: [PATCH 18/89] sched/core: Move task->mm handling methods to

* Ingo Molnar wrote: > > * Christoph Hellwig wrote: > > > On Mon, Feb 06, 2017 at 02:28:21PM +0100, Ingo Molnar wrote: > > > Move the following task->mm helper APIs into a new header file, > > > , to further reduce the size and complexity > > > of : > >

Re: [PATCH 18/89] sched/core: Move task->mm handling methods to

* Ingo Molnar wrote: > > * Christoph Hellwig wrote: > > > On Mon, Feb 06, 2017 at 02:28:21PM +0100, Ingo Molnar wrote: > > > Move the following task->mm helper APIs into a new header file, > > > , to further reduce the size and complexity > > > of : > > > > Is there any good reason why they

Re: [PATCH] f2fs: enhance lookup xattr

Hi Jaegeuk, On 2017/1/29 11:58, Jaegeuk Kim wrote: > Hi Chao, > > On 01/24, Chao Yu wrote: > > ... > >> >> -error = read_all_xattrs(inode, ipage, _addr); >> +error = lookup_all_xattrs(inode, ipage, index, len, name, >> +, _addr); >> if (error) >>

Re: [PATCH] f2fs: enhance lookup xattr

Hi Jaegeuk, On 2017/1/29 11:58, Jaegeuk Kim wrote: > Hi Chao, > > On 01/24, Chao Yu wrote: > > ... > >> >> -error = read_all_xattrs(inode, ipage, _addr); >> +error = lookup_all_xattrs(inode, ipage, index, len, name, >> +, _addr); >> if (error) >>

Re: [RFC PATCH] perf/stat: Add --disable-hwdt

* Borislav Petkov wrote: > On Mon, Feb 06, 2017 at 02:18:32PM +0100, Robert Richter wrote: > > > Isn't there the danger the previous watchdog state is never restored if for > > some reason perf got killed? So maybe have some other task running that > > restores it once perf is

Re: [RFC PATCH] perf/stat: Add --disable-hwdt

* Borislav Petkov wrote: > On Mon, Feb 06, 2017 at 02:18:32PM +0100, Robert Richter wrote: > > > Isn't there the danger the previous watchdog state is never restored if for > > some reason perf got killed? So maybe have some other task running that > > restores it once perf is gone. > >

Re: [PATCH] f2fs: introduce nid cache

Hi Jaegeuk, Happy Chinese New Year! :) On 2017/1/24 12:35, Jaegeuk Kim wrote: > Hi Chao, > > On 01/22, Chao Yu wrote: >> In scenario of intensively node allocation, free nids will be ran out >> soon, then it needs to stop to load free nids by traversing NAT blocks, >> in worse case, if NAT

Re: [PATCH] f2fs: introduce nid cache

Hi Jaegeuk, Happy Chinese New Year! :) On 2017/1/24 12:35, Jaegeuk Kim wrote: > Hi Chao, > > On 01/22, Chao Yu wrote: >> In scenario of intensively node allocation, free nids will be ran out >> soon, then it needs to stop to load free nids by traversing NAT blocks, >> in worse case, if NAT

Re: [PATCH 1/9] virtio_pci: remove struct virtio_pci_vq_info

On 2017年02月06日 01:15, Christoph Hellwig wrote: We don't really need struct virtio_pci_vq_info, as most field in there are redundant: - the vq backpointer is not strictly neede to start with - the entry in the vqs list is not needed - the generic virtqueue already has list, we only

Re: [PATCH 1/9] virtio_pci: remove struct virtio_pci_vq_info

On 2017年02月06日 01:15, Christoph Hellwig wrote: We don't really need struct virtio_pci_vq_info, as most field in there are redundant: - the vq backpointer is not strictly neede to start with - the entry in the vqs list is not needed - the generic virtqueue already has list, we only

Re: [PATCH 4/6] xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio*

On Tue 07-02-17 09:51:50, Dave Chinner wrote: > On Mon, Feb 06, 2017 at 07:47:43PM +0100, Michal Hocko wrote: > > On Mon 06-02-17 10:32:37, Darrick J. Wong wrote: [...] > > > I prefer to keep the "...yet we are likely to be under GFP_NOFS..." > > > wording of the old comment because it captures

Re: [PATCH 4/6] xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio*

On Tue 07-02-17 09:51:50, Dave Chinner wrote: > On Mon, Feb 06, 2017 at 07:47:43PM +0100, Michal Hocko wrote: > > On Mon 06-02-17 10:32:37, Darrick J. Wong wrote: [...] > > > I prefer to keep the "...yet we are likely to be under GFP_NOFS..." > > > wording of the old comment because it captures

Re: [PATCH 2/9] virtio_pci: use shared interrupts for virtqueues

On 2017年02月06日 01:15, Christoph Hellwig wrote: This lets IRQ layer handle dispatching IRQs to separate handlers for the case where we don't have per-VQ MSI-X vectors, and allows us to greatly simplify the code based on the assumption that we always have interrupt vector 0 (legacy INTx or

Re: [PATCH 2/9] virtio_pci: use shared interrupts for virtqueues

On 2017年02月06日 01:15, Christoph Hellwig wrote: This lets IRQ layer handle dispatching IRQs to separate handlers for the case where we don't have per-VQ MSI-X vectors, and allows us to greatly simplify the code based on the assumption that we always have interrupt vector 0 (legacy INTx or

Re: [PATCH v3 0/2] iov_iter: allow iov_iter_get_pages_alloc to allocate more pages per call

On Mon, Feb 06, 2017 at 03:18:42PM +0100, Miklos Szeredi wrote: > But I think it's breakable in the same way: if the deadlocked request > is aborted, the fault will release the page lock as well as mmap_sem, > and from there things will resolve themselves. Right you are - original holder of

Re: [PATCH v3 0/2] iov_iter: allow iov_iter_get_pages_alloc to allocate more pages per call

On Mon, Feb 06, 2017 at 03:18:42PM +0100, Miklos Szeredi wrote: > But I think it's breakable in the same way: if the deadlocked request > is aborted, the fault will release the page lock as well as mmap_sem, > and from there things will resolve themselves. Right you are - original holder of

Re: [PATCHv3 1/2] arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common

* Laura Abbott wrote: > > There are multiple architectures that support CONFIG_DEBUG_RODATA and > CONFIG_SET_MODULE_RONX. These options also now have the ability to be > turned off at runtime. Move these to an architecture independent > location and make these options

Re: [PATCHv3 1/2] arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common

* Laura Abbott wrote: > > There are multiple architectures that support CONFIG_DEBUG_RODATA and > CONFIG_SET_MODULE_RONX. These options also now have the ability to be > turned off at runtime. Move these to an architecture independent > location and make these options def_bool y for almost all

Re: [PATCH v4 3/3] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family

On Mon, Feb 06, 2017 at 11:28:20AM +0800, Baoyou Xie wrote: > + Shawn > > On 6 February 2017 at 11:26, Baoyou Xie wrote: > > > This patch adds i2c controller driver for ZTE's zx2967 family. > > > > Signed-off-by: Baoyou Xie Reviewed-by: Shawn Guo

Re: [PATCH v4 3/3] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family

On Mon, Feb 06, 2017 at 11:28:20AM +0800, Baoyou Xie wrote: > + Shawn > > On 6 February 2017 at 11:26, Baoyou Xie wrote: > > > This patch adds i2c controller driver for ZTE's zx2967 family. > > > > Signed-off-by: Baoyou Xie Reviewed-by: Shawn Guo

Re: [PATCH v3 2/7] drm/tinydrm: Add helper functions

On Mon, Feb 06, 2017 at 04:55:55PM -0600, Rob Herring wrote: > On Mon, Feb 6, 2017 at 5:08 AM, Thierry Reding > wrote: > > On Mon, Feb 06, 2017 at 11:07:42AM +0100, Daniel Vetter wrote: > >> On Mon, Feb 6, 2017 at 10:35 AM, Thierry Reding > >>

Re: [PATCH v3 2/7] drm/tinydrm: Add helper functions

On Mon, Feb 06, 2017 at 04:55:55PM -0600, Rob Herring wrote: > On Mon, Feb 6, 2017 at 5:08 AM, Thierry Reding > wrote: > > On Mon, Feb 06, 2017 at 11:07:42AM +0100, Daniel Vetter wrote: > >> On Mon, Feb 6, 2017 at 10:35 AM, Thierry Reding > >> wrote: > >> > >> > > > >

Re: [PATCH v3 2/7] drm/tinydrm: Add helper functions

On Tue, Feb 07, 2017 at 08:28:16AM +1000, Dave Airlie wrote: > > > > I definitely don't want that we don't attempt this. But brought from years > > of experience, I recommend to merge first (with pre-refactoring already > > applied, but helpers only extracted, not yet at the right spot), and then

Re: [PATCH v3 2/7] drm/tinydrm: Add helper functions

On Tue, Feb 07, 2017 at 08:28:16AM +1000, Dave Airlie wrote: > > > > I definitely don't want that we don't attempt this. But brought from years > > of experience, I recommend to merge first (with pre-refactoring already > > applied, but helpers only extracted, not yet at the right spot), and then

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

Hi James, On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: (...) > > We don't have the referenced commit above in 3.10 so we should be > > safe. Additionally I checked that neither 4.4 nor 3.12 have them > > either, so

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

Hi James, On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: (...) > > We don't have the referenced commit above in 3.10 so we should be > > safe. Additionally I checked that neither 4.4 nor 3.12 have them > > either, so

Re: [PATCH v3 1/7] drm: Add DRM support for tiny LCD displays

On Mon, Feb 06, 2017 at 08:23:36PM +0100, Noralf Trønnes wrote: > > Den 06.02.2017 10.17, skrev Thierry Reding: > > On Tue, Jan 31, 2017 at 05:03:13PM +0100, Noralf Trønnes wrote: > > > tinydrm provides helpers for very simple displays that can use > > > CMA backed framebuffers and need flushing

Re: [PATCH v3 1/7] drm: Add DRM support for tiny LCD displays

On Mon, Feb 06, 2017 at 08:23:36PM +0100, Noralf Trønnes wrote: > > Den 06.02.2017 10.17, skrev Thierry Reding: > > On Tue, Jan 31, 2017 at 05:03:13PM +0100, Noralf Trønnes wrote: > > > tinydrm provides helpers for very simple displays that can use > > > CMA backed framebuffers and need flushing

Re: [PATCH v4] zram: extend zero pages to same element pages

Hi Andrew, On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote: > From: zhouxianrong > > the idea is that without doing more calculations we extend zero pages > to same element pages for zram. zero page is special case of > same element page with zero element. >

Re: [PATCH v4] zram: extend zero pages to same element pages

Hi Andrew, On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote: > From: zhouxianrong > > the idea is that without doing more calculations we extend zero pages > to same element pages for zram. zero page is special case of > same element page with zero element. > > 1. the test is done

Re: [PATCH 1/4] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

Hi Mark, Thanks for reviving this series and sorry for not taking care of it myself. Please see some comments inline. On Tue, Feb 7, 2017 at 3:09 PM, Mark Yao wrote: > From: Tomasz Figa > > The API is not suitable for subsystems consisting of

Re: [PATCH 1/4] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

Hi Mark, Thanks for reviving this series and sorry for not taking care of it myself. Please see some comments inline. On Tue, Feb 7, 2017 at 3:09 PM, Mark Yao wrote: > From: Tomasz Figa > > The API is not suitable for subsystems consisting of multiple devices > and requires severe hacks to use

Re: [PATCH 3.10 000/319] 3.10.105-stable review

On Mon, Feb 06, 2017 at 08:56:25PM -0800, Guenter Roeck wrote: > On 02/06/2017 02:48 PM, Willy Tarreau wrote: > > On Mon, Feb 06, 2017 at 06:46:39AM -0800, Guenter Roeck wrote: > > > > An updated patch was pushed here : > > > > > > > > > > > >

Re: [PATCH 3.10 000/319] 3.10.105-stable review

On Mon, Feb 06, 2017 at 08:56:25PM -0800, Guenter Roeck wrote: > On 02/06/2017 02:48 PM, Willy Tarreau wrote: > > On Mon, Feb 06, 2017 at 06:46:39AM -0800, Guenter Roeck wrote: > > > > An updated patch was pushed here : > > > > > > > > > > > >

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > Hi Sathya, > > On Mon, Feb 06, 2017 at 09:21:44AM -0700, Sathya Prakash Veerichetty > wrote: > > Willy, > > I think this patch had a problem and later modified to a different > > blocking mechanism. Could you please pull in the latest

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote: > Hi Sathya, > > On Mon, Feb 06, 2017 at 09:21:44AM -0700, Sathya Prakash Veerichetty > wrote: > > Willy, > > I think this patch had a problem and later modified to a different > > blocking mechanism. Could you please pull in the latest

Re: [PATCH v2, 6/6] dt-bindings: phy-mt65xx-usb: add support for new version phy

On Fri, 2017-01-27 at 14:07 -0600, Rob Herring wrote: > On Fri, Jan 20, 2017 at 04:18:41PM +0800, Chunfeng Yun wrote: > > add a new compatible string for "mt2712", and move reference clock > > into each port node; > > > > Signed-off-by: Chunfeng Yun > > --- > >

Re: [PATCH v2, 6/6] dt-bindings: phy-mt65xx-usb: add support for new version phy

On Fri, 2017-01-27 at 14:07 -0600, Rob Herring wrote: > On Fri, Jan 20, 2017 at 04:18:41PM +0800, Chunfeng Yun wrote: > > add a new compatible string for "mt2712", and move reference clock > > into each port node; > > > > Signed-off-by: Chunfeng Yun > > --- > >

RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements

booting the guest. > > With next-20170203 (mentioned in my mail last Friday), I got the same > calltrace as Hannes. > > With today's linux-next (next-20170206), actually the calltrace changed to > the below. > [ 122.023036] ? remove_wait_queue+0x70/0x70 > [ 122.051383] async_

RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements

booting the guest. > > With next-20170203 (mentioned in my mail last Friday), I got the same > calltrace as Hannes. > > With today's linux-next (next-20170206), actually the calltrace changed to > the below. > [ 122.023036] ? remove_wait_queue+0x70/0x70 > [ 122.051383] async_

Re: [RFC v2] [ALSA][CONTROL] 1. Added 2 ioctls for reading/writing values of multiple controls in one go (at once) 2. Restructured the code for read/write of a single control

On Tue, 07 Feb 2017 05:33:05 +0100, Takashi Sakamoto wrote: > > On Feb 3 2017 16:24, Takashi Iwai wrote: > > On Thu, 02 Feb 2017 04:45:48 +0100, > > Takashi Sakamoto wrote: > >> > >> I'm _strongly_ interested in your two patches, because it has a > >> potentiality to purge ASoC abuse of TLV

Re: [PATCH v2] PCI: pciehp: Don't enable PME on runtime suspend

On Mon, Feb 06, 2017 at 10:52:12PM +0100, Rafael J. Wysocki wrote: > On Monday, February 06, 2017 10:20:41 PM Lukas Wunner wrote: > > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote: > > > On Mon, Feb 06, 2017 at 06:54:37AM +0100, Lukas Wunner wrote: > > > > Since commit 68db9bc81436

Re: [RFC v2] [ALSA][CONTROL] 1. Added 2 ioctls for reading/writing values of multiple controls in one go (at once) 2. Restructured the code for read/write of a single control

On Tue, 07 Feb 2017 05:33:05 +0100, Takashi Sakamoto wrote: > > On Feb 3 2017 16:24, Takashi Iwai wrote: > > On Thu, 02 Feb 2017 04:45:48 +0100, > > Takashi Sakamoto wrote: > >> > >> I'm _strongly_ interested in your two patches, because it has a > >> potentiality to purge ASoC abuse of TLV

Re: [PATCH v2] PCI: pciehp: Don't enable PME on runtime suspend

On Mon, Feb 06, 2017 at 10:52:12PM +0100, Rafael J. Wysocki wrote: > On Monday, February 06, 2017 10:20:41 PM Lukas Wunner wrote: > > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote: > > > On Mon, Feb 06, 2017 at 06:54:37AM +0100, Lukas Wunner wrote: > > > > Since commit 68db9bc81436

Re: [PATCH v2] PCI: pciehp: Don't enable PME on runtime suspend

On Mon, Feb 06, 2017 at 04:15:02PM -0600, Bjorn Helgaas wrote: > On Mon, Feb 06, 2017 at 10:20:41PM +0100, Lukas Wunner wrote: > > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote: > > > What is the hotplug event that causes generation of this wakeup event? > > > > If you had read

Re: [PATCH v2] PCI: pciehp: Don't enable PME on runtime suspend

On Mon, Feb 06, 2017 at 04:15:02PM -0600, Bjorn Helgaas wrote: > On Mon, Feb 06, 2017 at 10:20:41PM +0100, Lukas Wunner wrote: > > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote: > > > What is the hotplug event that causes generation of this wakeup event? > > > > If you had read

[PATCH -next 1/3] arm64: dts: mt8173: add reference clock for usb

Due to the reference clock comes from 26M oscillator directly on mt8173, and it is a fixed-clock in DTS which always turned on, we ignore it before. But on some platforms, it comes from PLL, and need be controlled, so here add it, no matter it is a fixed-clock or not. Signed-off-by: Chunfeng Yun

[PATCH -next 1/3] arm64: dts: mt8173: add reference clock for usb

Due to the reference clock comes from 26M oscillator directly on mt8173, and it is a fixed-clock in DTS which always turned on, we ignore it before. But on some platforms, it comes from PLL, and need be controlled, so here add it, no matter it is a fixed-clock or not. Signed-off-by: Chunfeng Yun

[PATCH -next 3/3] usb: xhci-mtk: make the reference clock optional

Make the reference clock optional for DTS backward compatibility and ignore the error if it does not exist. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

[PATCH -next 2/3] usb: mtu3: make the reference clock optional

Make the reference clock optional for DTS backward compatibility and ignore the error if it does not exist. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_plat.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

[PATCH -next 3/3] usb: xhci-mtk: make the reference clock optional

Make the reference clock optional for DTS backward compatibility and ignore the error if it does not exist. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/usb/host/xhci-mtk.c

[PATCH -next 2/3] usb: mtu3: make the reference clock optional

Make the reference clock optional for DTS backward compatibility and ignore the error if it does not exist. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_plat.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/usb/mtu3/mtu3_plat.c

[PATCH 3/4] drm/rockchip: gem: add mutex lock for drm mm

drm_mm_insert_node_generic and drm_mm_remove_node may access same resource with list ops, it's not threads safe, so protect this context with mutex lock. Fix bug: [49451.856244] == [49451.856350] BUG: KASAN: wild-memory-access on

[PATCH 1/4] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

From: Tomasz Figa The API is not suitable for subsystems consisting of multiple devices and requires severe hacks to use it. To mitigate this, this patch implements allocation and address space management locally by using helpers provided by DRM framework, like other DRM

[PATCH 2/4] drm/rockchip: Use common IOMMU API to attach devices

From: Shunqian Zheng Rockchip DRM used the arm special API, arm_iommu_*(), to attach iommu for ARM32 SoCs. This patch convert to common iommu API so it would support ARM64 like RK3399. Since previous patch added support for direct IOMMU address space management, there is

[PATCH 3/4] drm/rockchip: gem: add mutex lock for drm mm

drm_mm_insert_node_generic and drm_mm_remove_node may access same resource with list ops, it's not threads safe, so protect this context with mutex lock. Fix bug: [49451.856244] == [49451.856350] BUG: KASAN: wild-memory-access on

[PATCH 1/4] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

From: Tomasz Figa The API is not suitable for subsystems consisting of multiple devices and requires severe hacks to use it. To mitigate this, this patch implements allocation and address space management locally by using helpers provided by DRM framework, like other DRM drivers do, e.g. Tegra.

[PATCH 2/4] drm/rockchip: Use common IOMMU API to attach devices

From: Shunqian Zheng Rockchip DRM used the arm special API, arm_iommu_*(), to attach iommu for ARM32 SoCs. This patch convert to common iommu API so it would support ARM64 like RK3399. Since previous patch added support for direct IOMMU address space management, there is no need to use DMA API

[PATCH 0/4] drm/rockchip: switch to drm_mm for support arm64 iommu

Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and enable on ARM64" already landed, So drm/rockchip related patches [1] and [2] ready to landed, this series just rebase them to lastest drm-next. And fix some bugs for drm/rockchip drm_mm [0]:

[PATCH 0/4] drm/rockchip: switch to drm_mm for support arm64 iommu

Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and enable on ARM64" already landed, So drm/rockchip related patches [1] and [2] ready to landed, this series just rebase them to lastest drm-next. And fix some bugs for drm/rockchip drm_mm [0]:

[PATCH 4/4] drm/rockchip: gem: fixup iommu_map_sg error path

The return value of iommu_map_sg is size_t, it's unsigned, So check ret < 0 is wrong. And if iommu_map_sg is error, it's return value is zero, but rockchip_gem_iommu_map feel the zero return value is success, bug happen: [5.227458] [drm:rockchip_gem_iommu_map] *ERROR* failed to map buffer: 0

[PATCH 4/4] drm/rockchip: gem: fixup iommu_map_sg error path

The return value of iommu_map_sg is size_t, it's unsigned, So check ret < 0 is wrong. And if iommu_map_sg is error, it's return value is zero, but rockchip_gem_iommu_map feel the zero return value is success, bug happen: [5.227458] [drm:rockchip_gem_iommu_map] *ERROR* failed to map buffer: 0

Re: [PATCH v2 6/6] dt-bindings: mt8173-mtu3: add reference clock

Please ignore this series of patches, due to the first version have been merged into usb-next branch except DTS's one[PACH 4/6]. This will cause mtu3 probe failure, so I will send new patches based on usb-next branch. sorry On Mon, 2017-02-06 at 17:29 +0800, Chunfeng Yun wrote: > Due to the

Re: [PATCH v2 6/6] dt-bindings: mt8173-mtu3: add reference clock

Please ignore this series of patches, due to the first version have been merged into usb-next branch except DTS's one[PACH 4/6]. This will cause mtu3 probe failure, so I will send new patches based on usb-next branch. sorry On Mon, 2017-02-06 at 17:29 +0800, Chunfeng Yun wrote: > Due to the

Re: [PATCH 5/6] dmaengine: Add Broadcom SBA RAID driver

On Mon, Feb 6, 2017 at 10:24 PM, Vinod Koul wrote: > On Mon, Feb 06, 2017 at 05:31:15PM +0530, Anup Patel wrote: > >> >> + >> >> +/* SBA C_MDATA helper macros */ >> >> +#define SBA_C_MDATA_LOAD_VAL(__bnum0)((__bnum0) & 0x3) >> >> +#define

Re: [PATCH 5/6] dmaengine: Add Broadcom SBA RAID driver

On Mon, Feb 6, 2017 at 10:24 PM, Vinod Koul wrote: > On Mon, Feb 06, 2017 at 05:31:15PM +0530, Anup Patel wrote: > >> >> + >> >> +/* SBA C_MDATA helper macros */ >> >> +#define SBA_C_MDATA_LOAD_VAL(__bnum0)((__bnum0) & 0x3) >> >> +#define SBA_C_MDATA_WRITE_VAL(__bnum0)

linux-next: Tree for Feb 7

Hi all, Changes since 20170206: The tty tree lost its build failure. The akpm tree gained a conflict against the net-next tree. Non-merge commits (relative to Linus' tree): 7711 8737 files changed, 327880 insertions(+), 163014 deletions

linux-next: Tree for Feb 7

Hi all, Changes since 20170206: The tty tree lost its build failure. The akpm tree gained a conflict against the net-next tree. Non-merge commits (relative to Linus' tree): 7711 8737 files changed, 327880 insertions(+), 163014 deletions

[PATCH v2] perf/probe: Change MAX_CMDLEN

There are many SDT markers in powerpc whose uprobe definition goes beyond current MAX_CMDLEN, especially when target filename is long and sdt marker has long list of arguments. For example, definition of sdt marker method__compile__end: 8@17 8@9 8@10 -4@8 8@7 -4@6 8@5 -4@4 1@37(28) from file

[PATCH v2] perf/probe: Change MAX_CMDLEN

There are many SDT markers in powerpc whose uprobe definition goes beyond current MAX_CMDLEN, especially when target filename is long and sdt marker has long list of arguments. For example, definition of sdt marker method__compile__end: 8@17 8@9 8@10 -4@8 8@7 -4@6 8@5 -4@4 1@37(28) from file

Re: [lkp-robot] [scsi, block] 0dba1314d4: WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup

On Mon, Feb 6, 2017 at 8:09 PM, Jens Axboe wrote: > On 02/06/2017 05:14 PM, James Bottomley wrote: >> On Sun, 2017-02-05 at 21:13 -0800, Dan Williams wrote: >>> On Sun, Feb 5, 2017 at 1:13 AM, Christoph Hellwig wrote: Dan, can you please quote your

Re: [lkp-robot] [scsi, block] 0dba1314d4: WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup

On Mon, Feb 6, 2017 at 8:09 PM, Jens Axboe wrote: > On 02/06/2017 05:14 PM, James Bottomley wrote: >> On Sun, 2017-02-05 at 21:13 -0800, Dan Williams wrote: >>> On Sun, Feb 5, 2017 at 1:13 AM, Christoph Hellwig wrote: Dan, can you please quote your emails? I can't find any

Re: [PATCH 1/2] arm: dts: qcom: msm8974: Add RPMCC DT node

On Fri 03 Feb 10:36 PST 2017, Georgi Djakov wrote: > Add the RPM Clock Controller DT node for msm8974-based platforms, so that > drivers can use the clocks provided by the RPM processor. > > Signed-off-by: Georgi Djakov Reviewed-by: Bjorn Andersson

Re: [PATCH 1/2] arm: dts: qcom: msm8974: Add RPMCC DT node

On Fri 03 Feb 10:36 PST 2017, Georgi Djakov wrote: > Add the RPM Clock Controller DT node for msm8974-based platforms, so that > drivers can use the clocks provided by the RPM processor. > > Signed-off-by: Georgi Djakov Reviewed-by: Bjorn Andersson Regards, Bjorn > --- >

[PATCH] arm64: dts: mediatek: add mt8176 device tree

The core configuration is the only difference between mt8173 and mt8176. Like what arm/juno and marvell/armada-ap806 did, this change splits mt8173.dtsi into mt817x.dtsi and mt8173.dtsi. mt817x.dtsi defines the common blocks for mt8173 and mt8176. mt8173.dtsi and mt8176.dtsi describe mt8173 and

[PATCH] arm64: dts: mediatek: add mt8176 device tree

The core configuration is the only difference between mt8173 and mt8176. Like what arm/juno and marvell/armada-ap806 did, this change splits mt8173.dtsi into mt817x.dtsi and mt8173.dtsi. mt817x.dtsi defines the common blocks for mt8173 and mt8176. mt8173.dtsi and mt8176.dtsi describe mt8173 and

linux-next: manual merge of the akpm tree with the net-next tree

Hi Andrew, Today's linux-next merge of the akpm tree got a conflict in: drivers/net/can/flexcan.c between commits: 9eb7aa891101 ("can: flexcan: add quirk FLEXCAN_QUIRK_ENABLE_EACEN_RRS") b3cf53e988ce ("can: flexcan: add support for timestamp based rx-offload") from the net-next tree and

linux-next: manual merge of the akpm tree with the net-next tree

Hi Andrew, Today's linux-next merge of the akpm tree got a conflict in: drivers/net/can/flexcan.c between commits: 9eb7aa891101 ("can: flexcan: add quirk FLEXCAN_QUIRK_ENABLE_EACEN_RRS") b3cf53e988ce ("can: flexcan: add support for timestamp based rx-offload") from the net-next tree and

Re: [PATCH 3/5] perf/sdt/x86: Move OP parser to tools/perf/arch/x86/

Thanks Masami for the review. On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote: > On Thu, 2 Feb 2017 16:41:41 +0530 > Ravi Bangoria wrote: > >> SDT marker argument is in N@OP format. N is the size of argument and >> OP is the actual assembly

[PATCH] Make EN2 pin optional in the TRF7970A driver

From: Guan Ben Make the EN2 pin optional. This is useful for boards, which have this pin fix wired, for example to ground. Signed-off-by: Guan Ben Signed-off-by: Mark Jonas Signed-off-by: Heiko Schocher ---

Re: [PATCH 3/5] perf/sdt/x86: Move OP parser to tools/perf/arch/x86/

Thanks Masami for the review. On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote: > On Thu, 2 Feb 2017 16:41:41 +0530 > Ravi Bangoria wrote: > >> SDT marker argument is in N@OP format. N is the size of argument and >> OP is the actual assembly operand. OP is arch dependent component

[PATCH] Make EN2 pin optional in the TRF7970A driver

From: Guan Ben Make the EN2 pin optional. This is useful for boards, which have this pin fix wired, for example to ground. Signed-off-by: Guan Ben Signed-off-by: Mark Jonas Signed-off-by: Heiko Schocher --- .../devicetree/bindings/net/nfc/trf7970a.txt | 4 ++--

  1   2   3   4   5   6   7   8   9   10   >