[PATCH 8/8] writeback: throttle buffered writeback

Test patch that throttles buffered writeback to make it a lot more smooth, and has way less impact on other system activity. Background writeback should be, by definition, background activity. The fact that we flush huge bundles of it at the time means that it potentially has heavy impacts on

[PATCH 7/8] NVMe: inform block layer of write cache state

This isn't quite correct, since the VWC merely states if a potential write back cache is volatile or not. But for the purpose of write absortion, it's good enough. Signed-off-by: Jens Axboe --- drivers/nvme/host/core.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 8/8] writeback: throttle buffered writeback

Test patch that throttles buffered writeback to make it a lot more smooth, and has way less impact on other system activity. Background writeback should be, by definition, background activity. The fact that we flush huge bundles of it at the time means that it potentially has heavy impacts on

[PATCH 7/8] NVMe: inform block layer of write cache state

This isn't quite correct, since the VWC merely states if a potential write back cache is volatile or not. But for the purpose of write absortion, it's good enough. Signed-off-by: Jens Axboe --- drivers/nvme/host/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/nvme/host/core.c

[PATCH] [media] s5p-tv: Fix path in Makefile comment

The path mentioned in the driver's Makefile is not correct, fix it. Signed-off-by: Javier Martinez Canillas --- drivers/media/platform/s5p-tv/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/platform/s5p-tv/Makefile

[PATCH] [media] s5p-tv: Fix path in Makefile comment

The path mentioned in the driver's Makefile is not correct, fix it. Signed-off-by: Javier Martinez Canillas --- drivers/media/platform/s5p-tv/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/platform/s5p-tv/Makefile

Re: [PATCH 1/2 v6] dt/bindings: Add bindings for Layerscape SCFG MSI

On Wed, Mar 23, 2016 at 07:08:19PM +0800, Minghuan Lian wrote: > Some Layerscape SoCs use a simple MSI controller implementation. > It contains only two SCFG register to trigger and describe a > group 32 MSI interrupts. The patch adds bindings to describe > the controller. > > Signed-off-by:

Re: [PATCH 1/2 v6] dt/bindings: Add bindings for Layerscape SCFG MSI

On Wed, Mar 23, 2016 at 07:08:19PM +0800, Minghuan Lian wrote: > Some Layerscape SoCs use a simple MSI controller implementation. > It contains only two SCFG register to trigger and describe a > group 32 MSI interrupts. The patch adds bindings to describe > the controller. > > Signed-off-by:

Re: [PATCH v2] iommu/arm-smmu: Make use of phandle iterators in device-tree device-tree parsing

Hi Joerg, [auto build test ERROR on iommu/next] [also build test ERROR on v4.5 next-20160323] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-arm-smmu-Make-use-of-phandle

Re: [PATCH v2] iommu/arm-smmu: Make use of phandle iterators in device-tree device-tree parsing

Hi Joerg, [auto build test ERROR on iommu/next] [also build test ERROR on v4.5 next-20160323] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-arm-smmu-Make-use-of-phandle

[PATCH] rcu: Remove superfluous versions of rcu_read_lock_sched_held()

Currently, we have four versions of rcu_read_lock_sched_held(), depending on the combined choices on PREEMPT_COUNT and DEBUG_LOCK_ALLOC. But we actually don't need to specialize those for PREEMPT_COUNT=n kernel. Because: 1. For the implementations in DEBUG_LOCK_ALLOC=n kernel, we can use

[PATCH] rcu: Remove superfluous versions of rcu_read_lock_sched_held()

Currently, we have four versions of rcu_read_lock_sched_held(), depending on the combined choices on PREEMPT_COUNT and DEBUG_LOCK_ALLOC. But we actually don't need to specialize those for PREEMPT_COUNT=n kernel. Because: 1. For the implementations in DEBUG_LOCK_ALLOC=n kernel, we can use

[PATCH net-next,2/2] hv_netvsc: Fix the array sizes to be max supported channels

The VRSS_CHANNEL_MAX is the max number of channels supported by Hyper-V hosts. We use it for the related array sizes instead of using NR_CPUS, which may be set to several thousands. This patch reduces possible memory allocation failures. Signed-off-by: Haiyang Zhang

[PATCH net-next,2/2] hv_netvsc: Fix the array sizes to be max supported channels

The VRSS_CHANNEL_MAX is the max number of channels supported by Hyper-V hosts. We use it for the related array sizes instead of using NR_CPUS, which may be set to several thousands. This patch reduces possible memory allocation failures. Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan

[PATCH RESEND] crypto: sun4i-ss: Replace spinlock_bh by spin_lock_irq{save|restore}

The current sun4i-ss driver could generate data corruption when ciphering/deciphering. It occurs randomly on end of handled data. No root cause have been found and the only way to remove it is to replace all spin_lock_bh by their irq counterparts. Fixes: 6298e948215f ("crypto: sunxi-ss - Add

[PATCH RESEND] crypto: sun4i-ss: Replace spinlock_bh by spin_lock_irq{save|restore}

The current sun4i-ss driver could generate data corruption when ciphering/deciphering. It occurs randomly on end of handled data. No root cause have been found and the only way to remove it is to replace all spin_lock_bh by their irq counterparts. Fixes: 6298e948215f ("crypto: sunxi-ss - Add

Re: [PATCH next 1/2] PCI: keystone: add pci error irq handler

On Tue, Mar 22, 2016 at 03:52:57PM -0400, Murali Karicheri wrote: > Keystone PCI hardware generates error interrupts at RC using platform > irq instead of standard msi/legacy irq. Add a simple error handler that > logs the fatal interrupt status to the console. > > Signed-off-by: Murali Karicheri

Re: [PATCH next 1/2] PCI: keystone: add pci error irq handler

On Tue, Mar 22, 2016 at 03:52:57PM -0400, Murali Karicheri wrote: > Keystone PCI hardware generates error interrupts at RC using platform > irq instead of standard msi/legacy irq. Add a simple error handler that > logs the fatal interrupt status to the console. > > Signed-off-by: Murali Karicheri

Re: [PATCH v2 2/2] doc: dt: mtd: add a DT property to enable the use of 4byte-address op codes

Hi Rob, sorry I've sent v3 at the same time as you answered to v2. I'll take your comments into account for v4. Brian, any preference between 4byte-opcodes or m25p-4byte-opcodes? Best regards, Cyrille Le 23/03/2016 13:49, Rob Herring a écrit : > On Tue, Mar 22, 2016 at 10:13 AM, Cyrille

Re: [PATCH v2 2/2] doc: dt: mtd: add a DT property to enable the use of 4byte-address op codes

Hi Rob, sorry I've sent v3 at the same time as you answered to v2. I'll take your comments into account for v4. Brian, any preference between 4byte-opcodes or m25p-4byte-opcodes? Best regards, Cyrille Le 23/03/2016 13:49, Rob Herring a écrit : > On Tue, Mar 22, 2016 at 10:13 AM, Cyrille

Re: [PATCH 2/2] dmaengine: qcom_bam_dma: Bypass BAM init if not managed locally

On Tue, Mar 22, 2016 at 03:19:11PM +0530, Pramod Gurav wrote: > On some QOCM platforms BAM control registers are managed remotely s/QOCM/QCOM/ > hence can not be accessed by application processor for writes. Pass > a DT property qcom,bam_ctrl_remote to declare the same to skip bam_init. Is this

Re: [PATCH 2/2] dmaengine: qcom_bam_dma: Bypass BAM init if not managed locally

On Tue, Mar 22, 2016 at 03:19:11PM +0530, Pramod Gurav wrote: > On some QOCM platforms BAM control registers are managed remotely s/QOCM/QCOM/ > hence can not be accessed by application processor for writes. Pass > a DT property qcom,bam_ctrl_remote to declare the same to skip bam_init. Is this

Re: [RFC 00/29] De-stage android's sync framework

On 19 January 2016 at 17:12, John Harrison wrote: > On 19/01/2016 15:23, Gustavo Padovan wrote: >> >> Hi Daniel, >> >> 2016-01-19 Daniel Vetter : >> >>> On Fri, Jan 15, 2016 at 12:55:10PM -0200, Gustavo Padovan wrote: From: Gustavo Padovan

Re: [PATCH] dt-bindings: input: add Raydium I2C touch driver bindings

On Tue, Mar 22, 2016 at 02:38:53PM +0800, jeffrey.lin wrote: > Document the device tree binfings of Raydium I2C touch driver. Is there a driver too? > Signed-off-by: jeffrey.lin > --- > .../devicetree/bindings/input/raydium_i2c_ts.txt| 21 > + >

Re: [RFC 00/29] De-stage android's sync framework

On 19 January 2016 at 17:12, John Harrison wrote: > On 19/01/2016 15:23, Gustavo Padovan wrote: >> >> Hi Daniel, >> >> 2016-01-19 Daniel Vetter : >> >>> On Fri, Jan 15, 2016 at 12:55:10PM -0200, Gustavo Padovan wrote: From: Gustavo Padovan This patch series de-stage the sync

Re: [PATCH] dt-bindings: input: add Raydium I2C touch driver bindings

On Tue, Mar 22, 2016 at 02:38:53PM +0800, jeffrey.lin wrote: > Document the device tree binfings of Raydium I2C touch driver. Is there a driver too? > Signed-off-by: jeffrey.lin > --- > .../devicetree/bindings/input/raydium_i2c_ts.txt| 21 > + >

[PATCH net-next,1/2] hv_netvsc: Fix accessing freed memory in netvsc_change_mtu()

struct netvsc_device is freed in rndis_filter_device_remove(). So we save the nvdev->num_chn into a temp variable for later usage. (Please also include this patch into stable branch.) Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan ---

[PATCH net-next,1/2] hv_netvsc: Fix accessing freed memory in netvsc_change_mtu()

struct netvsc_device is freed in rndis_filter_device_remove(). So we save the nvdev->num_chn into a temp variable for later usage. (Please also include this patch into stable branch.) Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan --- drivers/net/hyperv/netvsc_drv.c |5 -

Re: [PATCH v2 3/6] x86/mtrr: Fix Xorg crashes in Qemu sessions

On Wed, 2016-03-23 at 09:44 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 03:53:30PM -0600, Toshi Kani wrote: > > Yes. I had to remove this number since checkpatch complained that I > > needed to quote the whole patch tile again.  I will ignore this > > checkpatch error and add this

Re: [PATCH v2 3/6] x86/mtrr: Fix Xorg crashes in Qemu sessions

On Wed, 2016-03-23 at 09:44 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 03:53:30PM -0600, Toshi Kani wrote: > > Yes. I had to remove this number since checkpatch complained that I > > needed to quote the whole patch tile again.  I will ignore this > > checkpatch error and add this

[RFC PATCH] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

There are a bunch of media platform drivers under drivers/media/platform/ that are for Samsung SoCs but are not being built with exynos_defconfig. This patch enables them as a module to improve build coverage for these drivers and also to allow people use them with proper hardware if modules are

[RFC PATCH] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

There are a bunch of media platform drivers under drivers/media/platform/ that are for Samsung SoCs but are not being built with exynos_defconfig. This patch enables them as a module to improve build coverage for these drivers and also to allow people use them with proper hardware if modules are

Re: [PATCH] dma-buf/sync_file: de-stage sync_file

Hi Sumit, 2016-03-21 Sumit Semwal : > Thanks for the patch, Gustavo! > > On 18 March 2016 at 19:49, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > sync_file is useful to connect one or more fences to the

Re: [PATCH] dma-buf/sync_file: de-stage sync_file

Hi Sumit, 2016-03-21 Sumit Semwal : > Thanks for the patch, Gustavo! > > On 18 March 2016 at 19:49, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > sync_file is useful to connect one or more fences to the file. The file is > > used by userspace to track fences. > > > I think it is

Re: [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface

On Wed, 2016-03-23 at 09:51 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 03:40:45PM -0600, Toshi Kani wrote: > > Will change to "Prevent the OS from initializing the PAT MSR". > > > > I wanted to clarify that "disable" does not mean to disable PAT MSR. > > How do you "disable PAT MSR"

Re: [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface

On Wed, 2016-03-23 at 09:51 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 03:40:45PM -0600, Toshi Kani wrote: > > Will change to "Prevent the OS from initializing the PAT MSR". > > > > I wanted to clarify that "disable" does not mean to disable PAT MSR. > > How do you "disable PAT MSR"

Re: [PATCH v2 1/2] ASoC: codecs: add TA5720 digital amplifier DT bindings

On Mon, Mar 21, 2016 at 12:08:26PM -0500, Andreas Dannenberg wrote: > The Texas Instruments TAS5720L/M device is a high-efficiency mono > Class-D audio power amplifier optimized for high transient power > capability to use the dynamic power headroom of small loudspeakers. > Its digital time

Re: [PATCH v2 1/2] ASoC: codecs: add TA5720 digital amplifier DT bindings

On Mon, Mar 21, 2016 at 12:08:26PM -0500, Andreas Dannenberg wrote: > The Texas Instruments TAS5720L/M device is a high-efficiency mono > Class-D audio power amplifier optimized for high transient power > capability to use the dynamic power headroom of small loudspeakers. > Its digital time

Re: [PATCH v2 1/6] x86/mm/pat: Change PAT to support non-default PAT MSR

On Wed, 2016-03-23 at 09:43 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 12:35:19PM -0600, Toshi Kani wrote: > > Right.  Will change to "Add support of non-default PAT MSR setting at > > handoff". > > Please remove this "handoff" notion from the text. Every hw register is > being

Re: [PATCH v2 1/6] x86/mm/pat: Change PAT to support non-default PAT MSR

On Wed, 2016-03-23 at 09:43 +0100, Borislav Petkov wrote: > On Tue, Mar 22, 2016 at 12:35:19PM -0600, Toshi Kani wrote: > > Right.  Will change to "Add support of non-default PAT MSR setting at > > handoff". > > Please remove this "handoff" notion from the text. Every hw register is > being

Re: [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

On Wed, 2016-03-23 at 17:36 +0300, Maxim Zhukov wrote: > This commit fixed spacing errors and warnings. This commit log should show that you've tested this by stating something like: "git diff -w shows no difference" and "objdiff shows no changes" If objdiff shows changes, you

Re: [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

On Wed, 2016-03-23 at 17:36 +0300, Maxim Zhukov wrote: > This commit fixed spacing errors and warnings. This commit log should show that you've tested this by stating something like: "git diff -w shows no difference" and "objdiff shows no changes" If objdiff shows changes, you

Re: [PATCH 4/6] mm/vmstat: add zone range overlapping check

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim There is a system that node's pfn are overlapped like as following. -pfn> N0 N1 N2 N0 N1 N2 Therefore, we need to care this overlapping when iterating pfn range. There are two places in

Re: [PATCH 4/6] mm/vmstat: add zone range overlapping check

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim There is a system that node's pfn are overlapped like as following. -pfn> N0 N1 N2 N0 N1 N2 Therefore, we need to care this overlapping when iterating pfn range. There are two places in vmstat.c that iterates pfn

[PATCH v2 5/5] mailbox: Stop using ENOSYS for anything other than unimplemented syscalls

In accordance with e15f431fe2d5 ("errno.h: Improve ENOSYS's comment") and 91c9afaf97ee ("checkpatch.pl: new instances of ENOSYS are errors") we're converting from the old meaning of: ENOSYS "Function not implemented" to a more standard EINVAL. Reported-by: Seraphin Bonnaffe

[PATCH v2 5/5] mailbox: Stop using ENOSYS for anything other than unimplemented syscalls

In accordance with e15f431fe2d5 ("errno.h: Improve ENOSYS's comment") and 91c9afaf97ee ("checkpatch.pl: new instances of ENOSYS are errors") we're converting from the old meaning of: ENOSYS "Function not implemented" to a more standard EINVAL. Reported-by: Seraphin Bonnaffe Signed-off-by: Lee

[PATCH v2 3/5] mailbox: mailbox-test: Use more consistent format for calling copy_from_user()

While we're at it, ensure copy-to location is NULL'ed in the error path. Suggested-by: Dan Carpenter Signed-off-by: Lee Jones --- drivers/mailbox/mailbox-test.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

[PATCH v2 4/5] mailbox: mailbox-test: Prevent memory leak

If we set the Signal twice or more, without using it as part of a message, memory will be re-allocated and the pointer over-written. Prevent this potential leak by only allocating memory when there isn't any already. Reported-by: Dan Carpenter Signed-off-by: Lee Jones

[PATCH v2 3/5] mailbox: mailbox-test: Use more consistent format for calling copy_from_user()

While we're at it, ensure copy-to location is NULL'ed in the error path. Suggested-by: Dan Carpenter Signed-off-by: Lee Jones --- drivers/mailbox/mailbox-test.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/mailbox/mailbox-test.c

[PATCH v2 4/5] mailbox: mailbox-test: Prevent memory leak

If we set the Signal twice or more, without using it as part of a message, memory will be re-allocated and the pointer over-written. Prevent this potential leak by only allocating memory when there isn't any already. Reported-by: Dan Carpenter Signed-off-by: Lee Jones ---

[PATCH v2 1/5] ARM: STi: stih407-family: Add nodes for Mailbox

This patch supplies the Mailbox Controller nodes. In order to request channels, these nodes will be referenced by Mailbox Client nodes. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih407-family.dtsi | 33 + 1 file changed, 33

[PATCH v2 1/5] ARM: STi: stih407-family: Add nodes for Mailbox

This patch supplies the Mailbox Controller nodes. In order to request channels, these nodes will be referenced by Mailbox Client nodes. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih407-family.dtsi | 33 + 1 file changed, 33 insertions(+) diff --git

[PATCH v2 2/5] ARM: STi: DT: STiH407: Enable Mailbox testing facility

This patch supplies a Client node to enable the Mailbox testing facility. It will be used to send and receive messages from any given co-processor in order to test the STi Mailbox Controller driver. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih407-family.dtsi | 6

[PATCH v2 2/5] ARM: STi: DT: STiH407: Enable Mailbox testing facility

This patch supplies a Client node to enable the Mailbox testing facility. It will be used to send and receive messages from any given co-processor in order to test the STi Mailbox Controller driver. Signed-off-by: Lee Jones --- arch/arm/boot/dts/stih407-family.dtsi | 6 ++ 1 file changed,

[PATCH v2 0/5] mailbox: A few fixes due for the v4.6 -rcs

Hi Jassi, Resending these with patches 1 and 2 merged, as requested. Kind regards, Lee v1 => v2: - Patch 2 merged into patch - No functional changes Lee Jones (5): ARM: STi: stih407-family: Add nodes for Mailbox ARM: STi: DT: STiH407: Enable Mailbox testing facility mailbox:

[PATCH v2 0/5] mailbox: A few fixes due for the v4.6 -rcs

Hi Jassi, Resending these with patches 1 and 2 merged, as requested. Kind regards, Lee v1 => v2: - Patch 2 merged into patch - No functional changes Lee Jones (5): ARM: STi: stih407-family: Add nodes for Mailbox ARM: STi: DT: STiH407: Enable Mailbox testing facility mailbox:

Re: [RFC][PATCH v6 1/2] printk: Make printk() completely async

On Wed 23-03-16 23:30:20, Sergey Senozhatsky wrote: > Hello, > > On (03/23/16 14:20), Jan Kara wrote: > [..] > > > I though that it actually could be an advantage. console_verbore() is > > > called also by oops_begin() and it does not need to be fatal. But you > > > are right that it does not

Re: [RFC][PATCH v6 1/2] printk: Make printk() completely async

On Wed 23-03-16 23:30:20, Sergey Senozhatsky wrote: > Hello, > > On (03/23/16 14:20), Jan Kara wrote: > [..] > > > I though that it actually could be an advantage. console_verbore() is > > > called also by oops_begin() and it does not need to be fatal. But you > > > are right that it does not

Re: [PATCH 3/6] mm/memory_hotplug: add comment to some functions related to memory hotplug

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim __offline_isolated_pages() and test_pages_isolated() are used by memory hotplug. These functions require that range is in a single zone but there is no code about it because memory hotplug checks it

Re: [PATCH 3/6] mm/memory_hotplug: add comment to some functions related to memory hotplug

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim __offline_isolated_pages() and test_pages_isolated() are used by memory hotplug. These functions require that range is in a single zone but there is no code about it because memory hotplug checks it before calling these

[PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

This commit fixed spacing errors and warnings. Signed-off-by: Maxim Zhukov --- drivers/net/ethernet/dlink/dl2k.c | 491 +++--- 1 file changed, 245 insertions(+), 246 deletions(-) diff --git a/drivers/net/ethernet/dlink/dl2k.c

Re: [PATCH 2/6] mm/hugetlb: add same zone check in pfn_range_valid_gigantic()

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim alloc_gigantic_page() uses alloc_contig_range() and this requires that requested range is in a single zone. To satisfy that requirement, add this check to pfn_range_valid_gigantic(). Signed-off-by:

[PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

This commit fixed spacing errors and warnings. Signed-off-by: Maxim Zhukov --- drivers/net/ethernet/dlink/dl2k.c | 491 +++--- 1 file changed, 245 insertions(+), 246 deletions(-) diff --git a/drivers/net/ethernet/dlink/dl2k.c b/drivers/net/ethernet/dlink/dl2k.c

Re: [PATCH 2/6] mm/hugetlb: add same zone check in pfn_range_valid_gigantic()

On 03/14/2016 08:31 AM, js1...@gmail.com wrote: From: Joonsoo Kim alloc_gigantic_page() uses alloc_contig_range() and this requires that requested range is in a single zone. To satisfy that requirement, add this check to pfn_range_valid_gigantic(). Signed-off-by: Joonsoo Kim Acked-by:

[PATCH 2/2] drivers: net: ethernet: dlink: dl2k: fix indent

This commit fixed indent in file. Labels must be start of the line Signed-off-by: Maxim Zhukov --- drivers/net/ethernet/dlink/dl2k.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/net/ethernet/dlink/dl2k.c

[PATCH 2/2] drivers: net: ethernet: dlink: dl2k: fix indent

This commit fixed indent in file. Labels must be start of the line Signed-off-by: Maxim Zhukov --- drivers/net/ethernet/dlink/dl2k.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/net/ethernet/dlink/dl2k.c b/drivers/net/ethernet/dlink/dl2k.c index

Re: N900 sleep mode (in 4.5-rc0, if that matters)

On Wed 2016-02-10 17:08:18, Tony Lindgren wrote: > * Tony Lindgren [160209 09:26]: > > * Pavel Machek [160207 13:24]: > > > > > ffdffebd 48004a20 (fa004a20) cm_idlest1_core blocking bits: 00200042 > > > 000d 48004a28 (fa004a28) cm_idlest3_core > > > > Bit 21

Re: N900 sleep mode (in 4.5-rc0, if that matters)

On Wed 2016-02-10 17:08:18, Tony Lindgren wrote: > * Tony Lindgren [160209 09:26]: > > * Pavel Machek [160207 13:24]: > > > > > ffdffebd 48004a20 (fa004a20) cm_idlest1_core blocking bits: 00200042 > > > 000d 48004a28 (fa004a28) cm_idlest3_core > > > > Bit 21 in cm_idlest1_core is for

Re: [RFC][PATCH v6 1/2] printk: Make printk() completely async

Hello, On (03/23/16 14:20), Jan Kara wrote: [..] > > I though that it actually could be an advantage. console_verbore() is > > called also by oops_begin() and it does not need to be fatal. But you > > are right that it does not need to be the righ approach. > > If we oops, I want printk to be

Re: [RFC][PATCH v6 1/2] printk: Make printk() completely async

Hello, On (03/23/16 14:20), Jan Kara wrote: [..] > > I though that it actually could be an advantage. console_verbore() is > > called also by oops_begin() and it does not need to be fatal. But you > > are right that it does not need to be the righ approach. > > If we oops, I want printk to be

[PATCH] regmap: cache: Fix typo in cache_bypass parameter description

Setting the flag 'cache_bypass' will bypass the cache not the hardware. Fix this comment here. Fixes: 0eef6b0415f5 ("regmap: Fix doc comment") Signed-off-by: Andrew F. Davis --- drivers/base/regmap/regcache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] regmap: cache: Fix typo in cache_bypass parameter description

Setting the flag 'cache_bypass' will bypass the cache not the hardware. Fix this comment here. Fixes: 0eef6b0415f5 ("regmap: Fix doc comment") Signed-off-by: Andrew F. Davis --- drivers/base/regmap/regcache.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 3/5] ftrace perf: Use ftrace_ops::private to store event pointer

On Wed, Mar 16, 2016 at 03:34:31PM +0100, Jiri Olsa wrote: > Fixing this by using ftrace_ops::private value to keep > the perf_event pointer. This way we don't need to search > for triggered event (as tracepoint handler does) and > directly store sample. container_of(ops, struct perf_event,

Re: [PATCH 3/5] ftrace perf: Use ftrace_ops::private to store event pointer

On Wed, Mar 16, 2016 at 03:34:31PM +0100, Jiri Olsa wrote: > Fixing this by using ftrace_ops::private value to keep > the perf_event pointer. This way we don't need to search > for triggered event (as tracepoint handler does) and > directly store sample. container_of(ops, struct perf_event,

Re: [PATCH v2] fs: add file_dentry()

On Wed, Mar 23, 2016 at 3:14 PM, Miklos Szeredi wrote: > Use "--contains", otherwise "git describe" will just say which kernel > the patch has been committed to, not which release it appears in. > > git describe --contains 4bacc9c9234c > v4.2-rc1~2^2~27 Indeed; I saw the patch

Re: [PATCH v2] fs: add file_dentry()

On Wed, Mar 23, 2016 at 3:14 PM, Miklos Szeredi wrote: > Use "--contains", otherwise "git describe" will just say which kernel > the patch has been committed to, not which release it appears in. > > git describe --contains 4bacc9c9234c > v4.2-rc1~2^2~27 Indeed; I saw the patch in v4.1.x stable

Re: [PATCHv3 6/9] Documentation: dt: socfpga: Add Altera Arria10 L2 cache binding

On Mon, Mar 21, 2016 at 11:01:43AM -0500, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > Add the device tree bindings needed to support the Altera L2 > cache on the Arria10 chip. Since all the peripherals share > IRQs, the IRQ fields are now in the

Re: [PATCHv3 6/9] Documentation: dt: socfpga: Add Altera Arria10 L2 cache binding

On Mon, Mar 21, 2016 at 11:01:43AM -0500, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > Add the device tree bindings needed to support the Altera L2 > cache on the Arria10 chip. Since all the peripherals share > IRQs, the IRQ fields are now in the ecc_manager. > > Signed-off-by:

Re: [PATCH] regmap: mmio: Fix value endianness selection

On Wednesday 23 March 2016 13:17:59, Mark Brown wrote: > Currently when selecting value endianness we check the register > endiannes, not the value endianness. > > Reported-by: Alexander Stein > Signed-off-by: Mark Brown Mh, while this

Re: [PATCH] regmap: mmio: Fix value endianness selection

On Wednesday 23 March 2016 13:17:59, Mark Brown wrote: > Currently when selecting value endianness we check the register > endiannes, not the value endianness. > > Reported-by: Alexander Stein > Signed-off-by: Mark Brown Mh, while this _does_ fix the problem regarding accessing SCFG peripheral

[Patch V3 0/4] Code refine for Intel IOMMU

These four patches try to refine the Intel IOMMU. Patch 1/2 tries to make it

[Patch V3 0/4] Code refine for Intel IOMMU

These four patches try to refine the Intel IOMMU. Patch 1/2 tries to make it

Re: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

On 23.03.2016 05:53, Rajesh Bhagat wrote: IMO, The assumption that "xhci_abort_cmd_ring would always generate an event and handle_cmd_completion would be called" will not be always be true if HW is in bad state. Please share your opinion. writing the CA (command abort) bit in CRCR

Re: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout

On 23.03.2016 05:53, Rajesh Bhagat wrote: IMO, The assumption that "xhci_abort_cmd_ring would always generate an event and handle_cmd_completion would be called" will not be always be true if HW is in bad state. Please share your opinion. writing the CA (command abort) bit in CRCR

[Patch V3 2/4] iommu/vt-d: use zero-sized array in DMAR related ACPI structures

1. DMAR table has variable number of remapping entries 2. DMAR hardware unit has variable number of device scope 3. DMAR device scope has variable number of pci path In current implementation, we use (head + 1) to access these variable number elements, which may not be obvious for audience.

[Patch V3 3/4] iommu/vt-d: check Register Base Address at the beginning of dmar_parse_one_drhd()

A NULL value of Register Base Address in a Hardware Unit Definition means it is an invalid dmar. Current implementation checks this value in alloc_iommu(), by when it has already allocated memory to store itself and device scope. This patch moves the check at the beginning of

[Patch V3 3/4] iommu/vt-d: check Register Base Address at the beginning of dmar_parse_one_drhd()

A NULL value of Register Base Address in a Hardware Unit Definition means it is an invalid dmar. Current implementation checks this value in alloc_iommu(), by when it has already allocated memory to store itself and device scope. This patch moves the check at the beginning of

[Patch V3 2/4] iommu/vt-d: use zero-sized array in DMAR related ACPI structures

1. DMAR table has variable number of remapping entries 2. DMAR hardware unit has variable number of device scope 3. DMAR device scope has variable number of pci path In current implementation, we use (head + 1) to access these variable number elements, which may not be obvious for audience.

[Patch V3 1/4] iommu/vt-d: replace *hdr with drhd[0] in struct dmar_drhd_unit

Before commit <6b1972493a84> ("iommu/vt-d: Implement DMAR unit hotplug framework"),dmaru->hdr just points to the memory region of DMA remapping hardware definition. In this case, it would have no difference to where we put hdr. After this commit, DMA remapping hardware definition is copied and

tools lib traceevent: Remove redundant CPU output

Commit a6745330789f "tools lib traceevent: Split pevent_print_event() into specific functionality functions" Broke apart the function pevent_print_event() into three functions. The first function prints the comm, pid and CPU, the second prints the timestamp. But that commit added the printing of

tools lib traceevent: Remove redundant CPU output

Commit a6745330789f "tools lib traceevent: Split pevent_print_event() into specific functionality functions" Broke apart the function pevent_print_event() into three functions. The first function prints the comm, pid and CPU, the second prints the timestamp. But that commit added the printing of

[Patch V3 1/4] iommu/vt-d: replace *hdr with drhd[0] in struct dmar_drhd_unit

Before commit <6b1972493a84> ("iommu/vt-d: Implement DMAR unit hotplug framework"),dmaru->hdr just points to the memory region of DMA remapping hardware definition. In this case, it would have no difference to where we put hdr. After this commit, DMA remapping hardware definition is copied and

[Patch V3 4/4] iommu/vt-d: refine dmar_acpi_dev_scope_init() with dmar_walk_dmar_table()

dmar_acpi_dev_scope_init() iterates on the remapping structure and just do proper job for ANDD structure. This is the what dmar_walk_dmar_table() does. This patch improves the code with dmar_walk_dmar_table(). Signed-off-by: Wei Yang --- drivers/iommu/dmar.c | 56

[Patch V3 4/4] iommu/vt-d: refine dmar_acpi_dev_scope_init() with dmar_walk_dmar_table()

dmar_acpi_dev_scope_init() iterates on the remapping structure and just do proper job for ANDD structure. This is the what dmar_walk_dmar_table() does. This patch improves the code with dmar_walk_dmar_table(). Signed-off-by: Wei Yang --- drivers/iommu/dmar.c | 56

Re: [PATCH v2] fs: add file_dentry()

On Wed, Mar 23, 2016 at 3:06 PM, William Dauchy wrote: > 4bacc9c9234c ("overlayfs: Make f_path always point to the overlay and > f_inode to the underlay"). > This commit is from v4.1 if I am not wrong. So the stable tag might be wrong. > > Am I missing something? Use

Re: [PATCH v2] fs: add file_dentry()

On Wed, Mar 23, 2016 at 3:06 PM, William Dauchy wrote: > 4bacc9c9234c ("overlayfs: Make f_path always point to the overlay and > f_inode to the underlay"). > This commit is from v4.1 if I am not wrong. So the stable tag might be wrong. > > Am I missing something? Use "--contains", otherwise "git

Re: [for-next][PATCH 1/2] tracing: Fix trace_printk() to print when not using bprintk()

On 03/23/2016 01:24 PM, Steven Rostedt wrote: From: "Steven Rostedt (Red Hat)" The trace_printk() code will allocate extra buffers if the compile detects that a trace_printk() is used. To do this, the format of the trace_printk() is saved to the __trace_printk_fmt section,

Re: [for-next][PATCH 1/2] tracing: Fix trace_printk() to print when not using bprintk()

On 03/23/2016 01:24 PM, Steven Rostedt wrote: From: "Steven Rostedt (Red Hat)" The trace_printk() code will allocate extra buffers if the compile detects that a trace_printk() is used. To do this, the format of the trace_printk() is saved to the __trace_printk_fmt section, and if that section

Re: Question regarding ptrace work for LInux v3.1

On Mon, Mar 21, 2016 at 3:35 PM, Oleg Nesterov wrote: > On 03/21, Patrick Donnelly wrote: >> On Mon, Mar 21, 2016 at 3:07 PM, Oleg Nesterov wrote: >> > case SIGSTOP: >> > /* Black magic to get threads working on old Linux kernels... */ >> > >> >

Re: Question regarding ptrace work for LInux v3.1

On Mon, Mar 21, 2016 at 3:35 PM, Oleg Nesterov wrote: > On 03/21, Patrick Donnelly wrote: >> On Mon, Mar 21, 2016 at 3:07 PM, Oleg Nesterov wrote: >> > case SIGSTOP: >> > /* Black magic to get threads working on old Linux kernels... */ >> > >> > if(p->nsyscalls == 0) { /*

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