Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On 29 January 2018 at 08:38, Chen-Yu Tsai wrote: > On Mon, Jan 29, 2018 at 3:34 PM, Code Kipper wrote: >> On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: >>> On Wed, Jan 24, 2018 at 10:10 PM, wrote: From: Marcus

Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On 29 January 2018 at 08:38, Chen-Yu Tsai wrote: > On Mon, Jan 29, 2018 at 3:34 PM, Code Kipper wrote: >> On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: >>> On Wed, Jan 24, 2018 at 10:10 PM, wrote: From: Marcus Cooper Some codecs require a different amount of a bit clocks

Re: [f2fs-dev] [PATCH 1/3] f2fs: support passing down write hints given by users to block layer

On 2018/1/29 9:49, Hyunchul Lee wrote: > > On 01/26/2018 11:10 AM, Chao Yu wrote: >> On 2018/1/26 7:46, Hyunchul Lee wrote: >>> On 01/25/2018 05:01 PM, Chao Yu wrote: Hi Hyunchul, On 2018/1/25 10:47, Hyunchul Lee wrote: > Hi Chao, > > On 01/25/2018 12:32 AM, Chao Yu

Re: [f2fs-dev] [PATCH 1/3] f2fs: support passing down write hints given by users to block layer

On 2018/1/29 9:49, Hyunchul Lee wrote: > > On 01/26/2018 11:10 AM, Chao Yu wrote: >> On 2018/1/26 7:46, Hyunchul Lee wrote: >>> On 01/25/2018 05:01 PM, Chao Yu wrote: Hi Hyunchul, On 2018/1/25 10:47, Hyunchul Lee wrote: > Hi Chao, > > On 01/25/2018 12:32 AM, Chao Yu

Re: [PATCH 3/3] Revert "e1000e: Do not read ICR in Other interrupt"

On 2018/01/26 13:01, Alexander Duyck wrote: > On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote: > > This reverts commit 16ecba59bc333d6282ee057fb02339f77a880beb. > > > > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > > 7526125 do not link up

Re: [PATCH 3/3] Revert "e1000e: Do not read ICR in Other interrupt"

On 2018/01/26 13:01, Alexander Duyck wrote: > On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote: > > This reverts commit 16ecba59bc333d6282ee057fb02339f77a880beb. > > > > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > > 7526125 do not link up after commit

Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On Mon, Jan 29, 2018 at 3:34 PM, Code Kipper wrote: > On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: >> On Wed, Jan 24, 2018 at 10:10 PM, wrote: >>> From: Marcus Cooper >>> >>> Some codecs require a different

Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On Mon, Jan 29, 2018 at 3:34 PM, Code Kipper wrote: > On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: >> On Wed, Jan 24, 2018 at 10:10 PM, wrote: >>> From: Marcus Cooper >>> >>> Some codecs require a different amount of a bit clocks per frame than >>> what is calculated by the sample width.

Re: [PATCH v2] of: use hash based search in of_find_node_by_phandle

I was curious, so I implemented it. It ends up being similar to Rasmus's 1st suggestion. The difference is we don't try to store all entries, but rather implement a hash table that doesn't handle collisions. Relying on the fact that phandles are just linearly allocated from 0, we just mask the

Re: [PATCH v2] of: use hash based search in of_find_node_by_phandle

I was curious, so I implemented it. It ends up being similar to Rasmus's 1st suggestion. The difference is we don't try to store all entries, but rather implement a hash table that doesn't handle collisions. Relying on the fact that phandles are just linearly allocated from 0, we just mask the

Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: > On Wed, Jan 24, 2018 at 10:10 PM, wrote: >> From: Marcus Cooper >> >> Some codecs require a different amount of a bit clocks per frame than >> what is calculated by the sample width.

Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality

On 29 January 2018 at 02:50, Chen-Yu Tsai wrote: > On Wed, Jan 24, 2018 at 10:10 PM, wrote: >> From: Marcus Cooper >> >> Some codecs require a different amount of a bit clocks per frame than >> what is calculated by the sample width. Use the tdm slot bindings to >> provide this mechanism. >>

Re: [PATCH v3 1/2] perf stat: Add support to print counts for fixed times

On Fri, Jan 26, 2018 at 10:06:56AM +0100, ufo19890607 wrote: SNIP > @@ -1891,6 +1902,8 @@ static const struct option stat_options[] = { > "command to run after to the measured command"), > OPT_UINTEGER('I', "interval-print", _config.interval, >

Re: [PATCH v3 1/2] perf stat: Add support to print counts for fixed times

On Fri, Jan 26, 2018 at 10:06:56AM +0100, ufo19890607 wrote: SNIP > @@ -1891,6 +1902,8 @@ static const struct option stat_options[] = { > "command to run after to the measured command"), > OPT_UINTEGER('I', "interval-print", _config.interval, >

Re: [PATCH v3 1/2] perf stat: Add support to print counts for fixed times

On Fri, Jan 26, 2018 at 10:06:56AM +0100, ufo19890607 wrote: SNIP > --- a/tools/perf/builtin-stat.c > +++ b/tools/perf/builtin-stat.c > @@ -168,6 +168,7 @@ static struct timespecref_time; > static struct cpu_map*aggr_map; > static aggr_get_id_t aggr_get_id;

Re: [PATCH 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

On 2018/01/26 08:50, Alexander Duyck wrote: > On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote: > > This reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d. > > > > We keep the fix for the first part of the problem (1) described in the log > > of that commit however

Re: [PATCH 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

On 2018/01/26 08:50, Alexander Duyck wrote: > On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote: > > This reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d. > > > > We keep the fix for the first part of the problem (1) described in the log > > of that commit however we use the

Re: [PATCH v3 1/2] perf stat: Add support to print counts for fixed times

On Fri, Jan 26, 2018 at 10:06:56AM +0100, ufo19890607 wrote: SNIP > --- a/tools/perf/builtin-stat.c > +++ b/tools/perf/builtin-stat.c > @@ -168,6 +168,7 @@ static struct timespecref_time; > static struct cpu_map*aggr_map; > static aggr_get_id_t aggr_get_id;

Re: [RFC PATCH V5 5/5] workqueue: introduce a way to set workqueue's scheduler

On Mon, 2018-01-29 at 14:33 +0800, Lai Jiangshan wrote: > On Mon, Jan 29, 2018 at 12:41 PM, Mike Galbraith wrote: > > On Mon, 2018-01-29 at 12:15 +0800, Lai Jiangshan wrote: > >> I think adding priority boost to workqueue(flush_work()) is the best > >> way to fix the problem. > > >

Re: [RFC PATCH V5 5/5] workqueue: introduce a way to set workqueue's scheduler

On Mon, 2018-01-29 at 14:33 +0800, Lai Jiangshan wrote: > On Mon, Jan 29, 2018 at 12:41 PM, Mike Galbraith wrote: > > On Mon, 2018-01-29 at 12:15 +0800, Lai Jiangshan wrote: > >> I think adding priority boost to workqueue(flush_work()) is the best > >> way to fix the problem. > > > > I disagree,

Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)

Tetsuo Handa wrote: > syzbot wrote: > > syzbot hit the following crash on net-next commit > > 6bb46bc57c8e9ce947cc605e555b7204b44d2b10 (Fri Jan 26 16:00:23 2018 +) > > Merge branch 'cxgb4-fix-dump-collection-when-firmware-crashed' > > > > C reproducer is

Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)

Tetsuo Handa wrote: > syzbot wrote: > > syzbot hit the following crash on net-next commit > > 6bb46bc57c8e9ce947cc605e555b7204b44d2b10 (Fri Jan 26 16:00:23 2018 +) > > Merge branch 'cxgb4-fix-dump-collection-when-firmware-crashed' > > > > C reproducer is attached. > > syzkaller reproducer is

RE: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver

Hi Guenter, We try to use the TCPCI driver on RT1711H and here are some questions. Q1. Is current TCPCI driver written according to TypeC Port Controller Interface Specification Revision 1.0 & Version 1.2? Q2. Because 0x80~0xFF are vendor defined registers. Some of them are needed to be

RE: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver

Hi Guenter, We try to use the TCPCI driver on RT1711H and here are some questions. Q1. Is current TCPCI driver written according to TypeC Port Controller Interface Specification Revision 1.0 & Version 1.2? Q2. Because 0x80~0xFF are vendor defined registers. Some of them are needed to be

Re: [PATCH v3 char-misc 1/1] Drivers: hv: vmbus: Implement Direct Mode for stimer0

On Sun, Jan 28, 2018 at 09:06:48PM +, Michael Kelley (EOSG) wrote: > From: Michael Kelley > > The 2016 version of Hyper-V offers the option to operate the guest VM > per-vcpu stimer's in Direct Mode, which means the timer interupts on its > own vector rather than

Re: [PATCH v3 char-misc 1/1] Drivers: hv: vmbus: Implement Direct Mode for stimer0

On Sun, Jan 28, 2018 at 09:06:48PM +, Michael Kelley (EOSG) wrote: > From: Michael Kelley > > The 2016 version of Hyper-V offers the option to operate the guest VM > per-vcpu stimer's in Direct Mode, which means the timer interupts on its > own vector rather than queueing a VMbus message.

Re: [PATCH 1/2] tools lib symbol: Use strtoul instead of hex2u64 in kallsyms__parse

On Fri, Jan 26, 2018 at 07:27:06PM +0200, Andy Shevchenko wrote: > On Fri, Jan 26, 2018 at 7:22 PM, Andy Shevchenko > wrote: > > On Fri, Jan 19, 2018 at 6:11 PM, Jiri Olsa wrote: > >> Current kallsyms__parse uses hex2u64, which gives > >> no

Re: [PATCH 1/2] tools lib symbol: Use strtoul instead of hex2u64 in kallsyms__parse

On Fri, Jan 26, 2018 at 07:27:06PM +0200, Andy Shevchenko wrote: > On Fri, Jan 26, 2018 at 7:22 PM, Andy Shevchenko > wrote: > > On Fri, Jan 19, 2018 at 6:11 PM, Jiri Olsa wrote: > >> Current kallsyms__parse uses hex2u64, which gives > >> no indication of error. Using strtoul to checkup > >> on

Re: [PATCH net-next 00/12] ptr_ring fixes

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: This fixes a bunch of issues around ptr_ring use in net core. One of these: "tap: fix use-after-free" is also needed on net, but can't be backported cleanly. I will post a net patch separately. Lightly tested - Jason, could you pls confirm this

Re: [PATCH net-next 00/12] ptr_ring fixes

On 2018年01月26日 07:36, Michael S. Tsirkin wrote: This fixes a bunch of issues around ptr_ring use in net core. One of these: "tap: fix use-after-free" is also needed on net, but can't be backported cleanly. I will post a net patch separately. Lightly tested - Jason, could you pls confirm this

Re: [PATCH net-next 05/12] ptr_ring: disallow lockless __ptr_ring_full

On 2018年01月29日 12:41, Michael S. Tsirkin wrote: On Mon, Jan 29, 2018 at 11:36:09AM +0800, Jason Wang wrote: On 2018年01月26日 10:46, Michael S. Tsirkin wrote: On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can overrun array

Re: [PATCH net-next 05/12] ptr_ring: disallow lockless __ptr_ring_full

On 2018年01月29日 12:41, Michael S. Tsirkin wrote: On Mon, Jan 29, 2018 at 11:36:09AM +0800, Jason Wang wrote: On 2018年01月26日 10:46, Michael S. Tsirkin wrote: On 2018年01月26日 07:36, Michael S. Tsirkin wrote: Similar to bcecb4bbf88a ("net: ptr_ring: otherwise safe empty checks can overrun array

Re: [GIT PULL tools] Linux kernel memory model

hi Paul, * Paul E. McKenney wrote: > Hello, Ingo, > > This pull request contains a single commit that adds a memory model to > the tools directory. This memory model can (roughly speaking) be thought > of as an automated version of memory-barriers.txt. It is

Re: [GIT PULL tools] Linux kernel memory model

hi Paul, * Paul E. McKenney wrote: > Hello, Ingo, > > This pull request contains a single commit that adds a memory model to > the tools directory. This memory model can (roughly speaking) be thought > of as an automated version of memory-barriers.txt. It is written in the > "cat" language,

Re: [PATCH] auxdisplay: charlcd: delete mdelay in long_sleep

Hi, On Fri, Jan 26, 2018 at 11:19:15PM +0800, Jia-Ju Bai wrote: > The function long_sleep() calls mdelay() when in an interrupt handler. > But only charlcd_clear_display() and charlcd_init_display calls > long_sleep(), and my tool finds that the two functions > are never called in an interrupt

Re: [PATCH] auxdisplay: charlcd: delete mdelay in long_sleep

Hi, On Fri, Jan 26, 2018 at 11:19:15PM +0800, Jia-Ju Bai wrote: > The function long_sleep() calls mdelay() when in an interrupt handler. > But only charlcd_clear_display() and charlcd_init_display calls > long_sleep(), and my tool finds that the two functions > are never called in an interrupt

[PATCH v2] dmaengine: dmatest: fix container_of member in dmatest_callback

The type of arg passed to dmatest_callback is struct dmatest_done. It refers to test_done in struct dmatest_thread, not done_wait. Fixes: 6f6a23a213be ("dmaengine: dmatest: move callback wait ...") Signed-off-by: Yang Shunyong Signed-off-by: Vinod Koul

[PATCH v2] dmaengine: dmatest: fix container_of member in dmatest_callback

The type of arg passed to dmatest_callback is struct dmatest_done. It refers to test_done in struct dmatest_thread, not done_wait. Fixes: 6f6a23a213be ("dmaengine: dmatest: move callback wait ...") Signed-off-by: Yang Shunyong Signed-off-by: Vinod Koul --- v2: change arg to done in

Re: [PATCH v1] mm: hwpoison: disable memory error handling on 1GB hugepage

My apology, I forgot to CC to the mailing lists. On Mon, Jan 29, 2018 at 03:28:03PM +0900, Naoya Horiguchi wrote: > Recently the following BUG was reported: > > Injecting memory failure for pfn 0x3c at process virtual address > 0x7fe3 > Memory failure: 0x3c: recovery

Re: [PATCH v1] mm: hwpoison: disable memory error handling on 1GB hugepage

My apology, I forgot to CC to the mailing lists. On Mon, Jan 29, 2018 at 03:28:03PM +0900, Naoya Horiguchi wrote: > Recently the following BUG was reported: > > Injecting memory failure for pfn 0x3c at process virtual address > 0x7fe3 > Memory failure: 0x3c: recovery

Re: [RFC 04/10] x86/mm: Only flush indirect branches when switching into non dumpable process

Hi Peter, David, all, First a quick note on David's earlier comment, about this optimization being still up for debate. The problem with this optimization as-is is that it doesn't protect userspace-to-userspace unless applications are rebuilt and we get the infrastructure to handle that (ELF,

Re: [RFC 04/10] x86/mm: Only flush indirect branches when switching into non dumpable process

Hi Peter, David, all, First a quick note on David's earlier comment, about this optimization being still up for debate. The problem with this optimization as-is is that it doesn't protect userspace-to-userspace unless applications are rebuilt and we get the infrastructure to handle that (ELF,

Re: [RFC PATCH V5 5/5] workqueue: introduce a way to set workqueue's scheduler

On Mon, Jan 29, 2018 at 12:41 PM, Mike Galbraith wrote: > On Mon, 2018-01-29 at 12:15 +0800, Lai Jiangshan wrote: >> I think adding priority boost to workqueue(flush_work()) is the best >> way to fix the problem. > > I disagree, priority boosting is needlessly invasive, takes

Re: [RFC PATCH V5 5/5] workqueue: introduce a way to set workqueue's scheduler

On Mon, Jan 29, 2018 at 12:41 PM, Mike Galbraith wrote: > On Mon, 2018-01-29 at 12:15 +0800, Lai Jiangshan wrote: >> I think adding priority boost to workqueue(flush_work()) is the best >> way to fix the problem. > > I disagree, priority boosting is needlessly invasive, takes control out > of

Re: 答复: Re: [RFC PATCH V5 5/5] workqueue: introduce a way to setworkqueue's scheduler

On Mon, 2018-01-29 at 13:50 +0800, wen.yan...@zte.com.cn wrote: > > > What happens when a new kworker needs to be spawned? > create_worker -> worker_attach_to_pool, in the function > worker_attach_to_pool，  we add this chunk: > > --- a/kernel/workqueue.c > +++ b/kernel/workqueue.c > @@ -1699,6

Re: 答复: Re: [RFC PATCH V5 5/5] workqueue: introduce a way to setworkqueue's scheduler

On Mon, 2018-01-29 at 13:50 +0800, wen.yan...@zte.com.cn wrote: > > > What happens when a new kworker needs to be spawned? > create_worker -> worker_attach_to_pool, in the function > worker_attach_to_pool，  we add this chunk: > > --- a/kernel/workqueue.c > +++ b/kernel/workqueue.c > @@ -1699,6

Re: [PATCH v3 4/5] powerpc/mm: Allow up to 64 low slices

Christophe Leroy writes: > While the implementation of the "slices" address space allows > a significant amount of high slices, it limits the number of > low slices to 16 due to the use of a single u64 low_slices_psize > element in struct mm_context_t > > On the 8xx, the

Re: [PATCH v3 4/5] powerpc/mm: Allow up to 64 low slices

Christophe Leroy writes: > While the implementation of the "slices" address space allows > a significant amount of high slices, it limits the number of > low slices to 16 due to the use of a single u64 low_slices_psize > element in struct mm_context_t > > On the 8xx, the minimum slice size is

Re: Re: [PATCH 1/2] dmaengine: dmatest: change symbolic permissions to octal values

Hi, Vinod On Mon, 2018-01-29 at 10:18 +0530, Vinod Koul wrote: > On Mon, Jan 22, 2018 at 06:44:40PM +0800, Yang Shunyong wrote: > > > > Current coding style prefers octal permissions values. This patch > > changes symbolic permissions to octal values. > Is this preference documented anywhere? >

Re: Re: [PATCH 1/2] dmaengine: dmatest: change symbolic permissions to octal values

Hi, Vinod On Mon, 2018-01-29 at 10:18 +0530, Vinod Koul wrote: > On Mon, Jan 22, 2018 at 06:44:40PM +0800, Yang Shunyong wrote: > > > > Current coding style prefers octal permissions values. This patch > > changes symbolic permissions to octal values. > Is this preference documented anywhere? >

Re: [PATCH 3/3] syscalls: Add a bit of documentation to __SYSCALL_DEFINE

On Sun, Jan 28, 2018 at 10:50:31PM +, Al Viro wrote: > On Sun, Jan 28, 2018 at 12:42:24PM -0800, Linus Torvalds wrote: > > > The 64-bit argument for 32-bit case would end up having to have a few > > more of those architecture-specific oddities. So not just > > "argument1(ptregs)", but

Re: [PATCH 3/3] syscalls: Add a bit of documentation to __SYSCALL_DEFINE

On Sun, Jan 28, 2018 at 10:50:31PM +, Al Viro wrote: > On Sun, Jan 28, 2018 at 12:42:24PM -0800, Linus Torvalds wrote: > > > The 64-bit argument for 32-bit case would end up having to have a few > > more of those architecture-specific oddities. So not just > > "argument1(ptregs)", but

Re: [PATCH] dmaengine: dmatest: fix container_of member in dmatest_callback

Hi, Vinod, On Mon, 2018-01-29 at 10:15 +0530, Vinod Koul wrote: > On Mon, Jan 22, 2018 at 03:28:28PM +0800, Yang Shunyong wrote: > > > > The type of arg passed to dmatest_callback is struct dmatest_done. > > It refers to test_done in struct dmatest_thread, not done_wait. > > > > Fixes:

Re: [PATCH] dmaengine: dmatest: fix container_of member in dmatest_callback

Hi, Vinod, On Mon, 2018-01-29 at 10:15 +0530, Vinod Koul wrote: > On Mon, Jan 22, 2018 at 03:28:28PM +0800, Yang Shunyong wrote: > > > > The type of arg passed to dmatest_callback is struct dmatest_done. > > It refers to test_done in struct dmatest_thread, not done_wait. > > > > Fixes:

Re: [PATCH v3 1/5] powerpc/mm: Remove intermediate bitmap copy in 'slices'

Christophe Leroy writes: > bitmap_or() and bitmap_andnot() can work properly with dst identical > to src1 or src2. There is no need of an intermediate result bitmap > that is copied back to dst in a second step. > Reviewed-by: Aneesh Kumar K.V

Re: [PATCH v3 1/5] powerpc/mm: Remove intermediate bitmap copy in 'slices'

Christophe Leroy writes: > bitmap_or() and bitmap_andnot() can work properly with dst identical > to src1 or src2. There is no need of an intermediate result bitmap > that is copied back to dst in a second step. > Reviewed-by: Aneesh Kumar K.V > Signed-off-by: Christophe Leroy > --- > v2: New

[PATCH] ACPI: Parse entire table as a term_list for Dell XPS 9570 and Precision M5530

The i2c touchpad on Dell XPS 9570 and Precision M5530 doesn't work out of box. The touchpad relies on its _INI method to update its _HID value from to SYNA2393. Also, the _STA relies on value of I2CN to report correct status. Set acpi_gbl_parse_table_as_term_list so the value of I2CN

[PATCH] ACPI: Parse entire table as a term_list for Dell XPS 9570 and Precision M5530

The i2c touchpad on Dell XPS 9570 and Precision M5530 doesn't work out of box. The touchpad relies on its _INI method to update its _HID value from to SYNA2393. Also, the _STA relies on value of I2CN to report correct status. Set acpi_gbl_parse_table_as_term_list so the value of I2CN

linux-next: manual merge of the nvdimm tree with the powerpc tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/powerpc/sysdev/axonram.c between commit: 1d65b1c886be ("powerpc/cell: Remove axonram driver") from the powerpc tree and commit: 785a3fab4adb ("mm, dax: introduce pfn_t_special()") from the nvdimm tree. I

linux-next: manual merge of the nvdimm tree with the powerpc tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/powerpc/sysdev/axonram.c between commit: 1d65b1c886be ("powerpc/cell: Remove axonram driver") from the powerpc tree and commit: 785a3fab4adb ("mm, dax: introduce pfn_t_special()") from the nvdimm tree. I

linux-next: manual merge of the nvdimm tree with the powerpc tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/powerpc/platforms/Kconfig between commit: 1d65b1c886be ("powerpc/cell: Remove axonram driver") from the powerpc tree and commit: 569d0365f571 ("dax: require 'struct page' by default for filesystem dax") from

linux-next: manual merge of the nvdimm tree with the powerpc tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/powerpc/platforms/Kconfig between commit: 1d65b1c886be ("powerpc/cell: Remove axonram driver") from the powerpc tree and commit: 569d0365f571 ("dax: require 'struct page' by default for filesystem dax") from

Re: [2/3] i2c: piix4: fix number of ports on Family 16h Model 30h

On Mon, Jan 29, 2018 at 01:54:19PM +1000, Andrew Cooks wrote: > Prevent bus timeouts and resets on Family 16h Model 30h), by not > probing reserved Ports 3 and 4. > > According to the AMD BIOS and Kernel Developer's Guides (BKDG), Port 3 > and Port 4 are reserved on the following devices: > -

Re: [2/3] i2c: piix4: fix number of ports on Family 16h Model 30h

On Mon, Jan 29, 2018 at 01:54:19PM +1000, Andrew Cooks wrote: > Prevent bus timeouts and resets on Family 16h Model 30h), by not > probing reserved Ports 3 and 4. > > According to the AMD BIOS and Kernel Developer's Guides (BKDG), Port 3 > and Port 4 are reserved on the following devices: > -

[PATCH] ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

Same issue as other Asus laptops, ACPI incorrectly reports discharging when battery is full and AC is plugged. Use the same battery quirk can workaround the issue. BugLink: https://bugs.launchpad.net/bugs/1661876 BugLink: https://bugs.launchpad.net/bugs/1745032 Signed-off-by: Kai-Heng Feng

[PATCH] ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

Same issue as other Asus laptops, ACPI incorrectly reports discharging when battery is full and AC is plugged. Use the same battery quirk can workaround the issue. BugLink: https://bugs.launchpad.net/bugs/1661876 BugLink: https://bugs.launchpad.net/bugs/1745032 Signed-off-by: Kai-Heng Feng ---

[PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

The layout of the UAC2 Control request and response varies depending on the request type. With the current implementation, only the Layout 2 Parameter Block (with the 2-byte sized RANGE attribute) is handled properly. For the Control requests with the 1-byte sized RANGE attribute (Bass Control,

[PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

The layout of the UAC2 Control request and response varies depending on the request type. With the current implementation, only the Layout 2 Parameter Block (with the 2-byte sized RANGE attribute) is handled properly. For the Control requests with the 1-byte sized RANGE attribute (Bass Control,

Re: ppc elf_map breakage with MAP_FIXED_NOREPLACE

On 01/29/2018 08:17 AM, Anshuman Khandual wrote: > On 01/26/2018 07:34 PM, Michal Hocko wrote: >> On Fri 26-01-18 18:04:27, Anshuman Khandual wrote: >> [...] >>> I tried to instrument mmap_region() for a single instance of 'sed' >>> binary and traced all it's VMA creation. But there is no trace

Re: ppc elf_map breakage with MAP_FIXED_NOREPLACE

On 01/29/2018 08:17 AM, Anshuman Khandual wrote: > On 01/26/2018 07:34 PM, Michal Hocko wrote: >> On Fri 26-01-18 18:04:27, Anshuman Khandual wrote: >> [...] >>> I tried to instrument mmap_region() for a single instance of 'sed' >>> binary and traced all it's VMA creation. But there is no trace

Re: [patch V2 1/2] sysfs/cpu: Add vulnerability folder

On 01/07/2018 04:48 PM, Thomas Gleixner wrote: > +#ifdef CONFIG_GENERIC_CPU_VULNERABILITIES > + > +ssize_t __weak cpu_show_meltdown(struct device *dev, > + struct device_attribute *attr, char *buf) > +{ > + return sprintf(buf, "Not affected\n"); > +} > + >

Re: [patch V2 1/2] sysfs/cpu: Add vulnerability folder

On 01/07/2018 04:48 PM, Thomas Gleixner wrote: > +#ifdef CONFIG_GENERIC_CPU_VULNERABILITIES > + > +ssize_t __weak cpu_show_meltdown(struct device *dev, > + struct device_attribute *attr, char *buf) > +{ > + return sprintf(buf, "Not affected\n"); > +} > + >

Re: KASAN: use-after-free Write in irq_bypass_register_consumer

On 1/27/2018 7:27 AM, Eric Biggers wrote: On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu wrote: The root cause is that kvm_irqfd_assign() and kvm_irqfd_deassign() can't be run in parallel. Some data structure(e.g, irqfd->consumer) will be crashed because irqfd may be freed in deassign

Re: KASAN: use-after-free Write in irq_bypass_register_consumer

On 1/27/2018 7:27 AM, Eric Biggers wrote: On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu wrote: The root cause is that kvm_irqfd_assign() and kvm_irqfd_deassign() can't be run in parallel. Some data structure(e.g, irqfd->consumer) will be crashed because irqfd may be freed in deassign

[PATCH 02/15] ARM: dts: ipq4019: Add a few peripheral nodes

Now with the driver updates for some peripherals being there, add i2c, spi, pcie, bam, qpic-nand, scm nodes to enhance the available peripheral support. Signed-off-by: Sricharan R --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 134 1

[PATCH 02/15] ARM: dts: ipq4019: Add a few peripheral nodes

Now with the driver updates for some peripherals being there, add i2c, spi, pcie, bam, qpic-nand, scm nodes to enhance the available peripheral support. Signed-off-by: Sricharan R --- arch/arm/boot/dts/qcom-ipq4019.dtsi | 134 1 file changed, 134

Re: [PATCH] mm/swap.c: fix kernel-doc functions and parameters

On Sun, Jan 28, 2018 at 08:01:08PM -0800, Randy Dunlap wrote: > @@ -400,6 +400,10 @@ void mark_page_accessed(struct page *pag > } > EXPORT_SYMBOL(mark_page_accessed); > > +/** > + * __lru_cache_add: add a page to the page lists > + * @page: the page to add > + */ > static void

[PATCH 01/15] firmware: qcom: scm: Add ipq4019 soc compatible

Add the compatible for ipq4019. This does not need clocks to do scm calls. Signed-off-by: Sricharan R --- Documentation/devicetree/bindings/firmware/qcom,scm.txt | 3 ++- drivers/firmware/qcom_scm.c | 3 +++ 2 files changed, 5 insertions(+),

Re: [PATCH] mm/swap.c: fix kernel-doc functions and parameters

On Sun, Jan 28, 2018 at 08:01:08PM -0800, Randy Dunlap wrote: > @@ -400,6 +400,10 @@ void mark_page_accessed(struct page *pag > } > EXPORT_SYMBOL(mark_page_accessed); > > +/** > + * __lru_cache_add: add a page to the page lists > + * @page: the page to add > + */ > static void

[PATCH 01/15] firmware: qcom: scm: Add ipq4019 soc compatible

Add the compatible for ipq4019. This does not need clocks to do scm calls. Signed-off-by: Sricharan R --- Documentation/devicetree/bindings/firmware/qcom,scm.txt | 3 ++- drivers/firmware/qcom_scm.c | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH 08/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk04.1-c5 board file

dk04.1-c5 has a spinand connected to spi bus0 chipselect 1. Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c5.dts | 23 +++ 2 files changed, 24 insertions(+) create

[PATCH 08/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk04.1-c5 board file

dk04.1-c5 has a spinand connected to spi bus0 chipselect 1. Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c5.dts | 23 +++ 2 files changed, 24 insertions(+) create mode 100644

[PATCH 05/15] ARM: dts: ipq4019: Add ipq4019-ap-dk01-c2 board file

The board has a spi-nand interface on spi0 bus chipselect1. Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1-c2.dts | 25 + 2 files changed, 26 insertions(+) create

[PATCH 05/15] ARM: dts: ipq4019: Add ipq4019-ap-dk01-c2 board file

The board has a spi-nand interface on spi0 bus chipselect1. Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1-c2.dts | 25 + 2 files changed, 26 insertions(+) create mode 100644

[PATCH 13/15] ARM: dts: ipq8074: Add peripheral nodes

Add serial, i2c, bam, spi, qpic peripheral nodes. Signed-off-by: Sricharan R --- arch/arm64/boot/dts/qcom/ipq8074.dtsi | 103 ++ 1 file changed, 103 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi

[PATCH 10/15] ARM: dts: ipq4019: Add ipq4019-ap.dk07.1 common data

Add the common data for all dk07 based boards. Signed-off-by: Sricharan R --- arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi | 128 ++ 1 file changed, 128 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi diff --git

[PATCH 13/15] ARM: dts: ipq8074: Add peripheral nodes

Add serial, i2c, bam, spi, qpic peripheral nodes. Signed-off-by: Sricharan R --- arch/arm64/boot/dts/qcom/ipq8074.dtsi | 103 ++ 1 file changed, 103 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi index

[PATCH 10/15] ARM: dts: ipq4019: Add ipq4019-ap.dk07.1 common data

Add the common data for all dk07 based boards. Signed-off-by: Sricharan R --- arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi | 128 ++ 1 file changed, 128 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi diff --git

[PATCH 12/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk07.1-c2 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c2.dts | 78 + 2 files changed, 79 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c2.dts

[PATCH 12/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk07.1-c2 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c2.dts | 78 + 2 files changed, 79 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c2.dts diff --git

[PATCH 09/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk04.1-c3 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c3.dts | 14 ++ 2 files changed, 15 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c3.dts diff --git

[PATCH 11/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk07.1-c1 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c1.dts | 60 + 2 files changed, 61 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c1.dts

[PATCH 07/15] ARM: dts: ipq4019: Add ipq4019-ap.dk04.1-c1 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts | 8 2 files changed, 9 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts diff --git

[PATCH 14/15] ARM: dts: ipq8074: Add pcie nodes

The driver/phy support for ipq8074 is available now. So enabling the nodes in DT. Signed-off-by: Sricharan R --- arch/arm64/boot/dts/qcom/ipq8074.dtsi | 155 +- 1 file changed, 154 insertions(+), 1 deletion(-) diff --git

[PATCH 09/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk04.1-c3 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c3.dts | 14 ++ 2 files changed, 15 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c3.dts diff --git

[PATCH 11/15] ARM: dts: ipq4019: Add qcom-ipq4019-ap.dk07.1-c1 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c1.dts | 60 + 2 files changed, 61 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1-c1.dts diff --git

[PATCH 07/15] ARM: dts: ipq4019: Add ipq4019-ap.dk04.1-c1 board file

Signed-off-by: Sricharan R --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts | 8 2 files changed, 9 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts diff --git a/arch/arm/boot/dts/Makefile

[PATCH 14/15] ARM: dts: ipq8074: Add pcie nodes

The driver/phy support for ipq8074 is available now. So enabling the nodes in DT. Signed-off-by: Sricharan R --- arch/arm64/boot/dts/qcom/ipq8074.dtsi | 155 +- 1 file changed, 154 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi

[PATCH 15/15] ARM: dts: ipq8074: Enable few peripherals for hk01 board

Signed-off-by: Sricharan R --- arch/arm64/boot/dts/qcom/ipq8074-hk01.dts | 99 +++ 1 file changed, 99 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/ipq8074-hk01.dts b/arch/arm64/boot/dts/qcom/ipq8074-hk01.dts index 6a838b5..69a1b0c

[PATCH 06/15] ARM: dts: ipq4019: Add ipq4019-ap.dk04.dtsi

Add the common parts for the dk04 boards. Signed-off-by: Sricharan R --- arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1.dtsi | 147 ++ 1 file changed, 147 insertions(+) create mode 100644 arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1.dtsi diff --git

  1   2   3   4   5   6   7   8   9   10   >