Re: [GIT PULL] percpu fix for v4.10-rc6

Linus Torvalds wrote: > The fact is, atomic_long_inc_not_zero() shouldn't be returning > anything with high bits.. Ummm... Why's that the case? If atomic_long_t can never exceed UINT_MAX, then why does it exist at all? David

Re: [GIT PULL] percpu fix for v4.10-rc6

Linus Torvalds wrote: > The fact is, atomic_long_inc_not_zero() shouldn't be returning > anything with high bits.. Ummm... Why's that the case? If atomic_long_t can never exceed UINT_MAX, then why does it exist at all? David

[PATCH v9 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon Hwang Signed-off-by: Andrzej Hajda Signed-off-by: Chanwoo Choi

[PATCH v9 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon Hwang Signed-off-by: Andrzej Hajda Signed-off-by: Chanwoo Choi Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi ---

[PATCH v9 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Reviewed-by: Andrzej Hajda

[PATCH v9 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Reviewed-by: Andrzej Hajda Acked-by: Rob Herring --- .../bindings/display/panel/samsung,s6e3ha2.txt | 28

[PATCH v9 0/3] Add support for the S6E3HA2 panel on TM2 board

Changes for V9: - Fixed the te-gpio to optional in bindings Changes for V8: - Applied below two patches: (drm/exynos) : drm/exynos: mic: Add mode_set callback function : drm/exynos: mic: Fix parse_dt function - The dt-binding patch and driver patch were divided. - Rebase these patches on

[PATCH v9 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon

[PATCH v9 0/3] Add support for the S6E3HA2 panel on TM2 board

Changes for V9: - Fixed the te-gpio to optional in bindings Changes for V8: - Applied below two patches: (drm/exynos) : drm/exynos: mic: Add mode_set callback function : drm/exynos: mic: Fix parse_dt function - The dt-binding patch and driver patch were divided. - Rebase these patches on

[PATCH v9 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun Kwon Tested-by: Chanwoo Choi Reviewed-by: Andrzej Hajda ---

Re: [PATCH v3 1/8] ASoC: sun4i-i2s: Update binding documentation to include A31

and resend. I based my series on linux-next 20170131. Which one I should use? Thank you in advance, Best regards, -- Mylène Josserand, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com

Re: [PATCH v3 1/8] ASoC: sun4i-i2s: Update binding documentation to include A31

and resend. I based my series on linux-next 20170131. Which one I should use? Thank you in advance, Best regards, -- Mylène Josserand, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

2017년 02월 01일 16:34에 Andrzej Hajda 이(가) 쓴 글: > On 01.02.2017 08:31, Inki Dae wrote: >> >> 2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: >>> In some platforms there is attached another device to the end of HDMI. >>> The patch adds support for it. >> Andrzej, can you clarify what bridge device can

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

2017년 02월 01일 16:34에 Andrzej Hajda 이(가) 쓴 글: > On 01.02.2017 08:31, Inki Dae wrote: >> >> 2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: >>> In some platforms there is attached another device to the end of HDMI. >>> The patch adds support for it. >> Andrzej, can you clarify what bridge device can

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

On 01.02.2017 08:31, Inki Dae wrote: > > 2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: >> In some platforms there is attached another device to the end of HDMI. >> The patch adds support for it. > Andrzej, can you clarify what bridge device can be attached and actually is > now attached to the end

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

On 01.02.2017 08:31, Inki Dae wrote: > > 2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: >> In some platforms there is attached another device to the end of HDMI. >> The patch adds support for it. > Andrzej, can you clarify what bridge device can be attached and actually is > now attached to the end

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On 02/01/2017 02:20 AM, Jarkko Sakkinen wrote: On Wed, Feb 01, 2017 at 12:14:12AM +0530, Nayna wrote: I already sent my pull request to 4.11 and even today I found something fishy. You declared a function local array by using a variable in "tpm: enhance TPM 2.0 PCR extend to support multiple

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On 02/01/2017 02:20 AM, Jarkko Sakkinen wrote: On Wed, Feb 01, 2017 at 12:14:12AM +0530, Nayna wrote: I already sent my pull request to 4.11 and even today I found something fishy. You declared a function local array by using a variable in "tpm: enhance TPM 2.0 PCR extend to support multiple

Re: [RFC] cpuset: Enable changing of top_cpuset's mems_allowed nodemask

On 01/31/2017 09:30 PM, Mel Gorman wrote: > On Tue, Jan 31, 2017 at 07:52:37PM +0530, Anshuman Khandual wrote: >> At present, top_cpuset.mems_allowed is same as node_states[N_MEMORY] and it >> cannot be changed at the runtime. Maximum possible node_states[N_MEMORY] >> also gets reflected in

Re: [RFC] cpuset: Enable changing of top_cpuset's mems_allowed nodemask

On 01/31/2017 09:30 PM, Mel Gorman wrote: > On Tue, Jan 31, 2017 at 07:52:37PM +0530, Anshuman Khandual wrote: >> At present, top_cpuset.mems_allowed is same as node_states[N_MEMORY] and it >> cannot be changed at the runtime. Maximum possible node_states[N_MEMORY] >> also gets reflected in

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: > In some platforms there is attached another device to the end of HDMI. > The patch adds support for it. Andrzej, can you clarify what bridge device can be attached and actually is now attached to the end of HDMI? And I wonder if we have the device

Re: [PATCH 4/7] drm/exynos/hdmi: add bridge support

2017년 01월 20일 15:52에 Andrzej Hajda 이(가) 쓴 글: > In some platforms there is attached another device to the end of HDMI. > The patch adds support for it. Andrzej, can you clarify what bridge device can be attached and actually is now attached to the end of HDMI? And I wonder if we have the device

Re: [PATCH 4.9 00/66] 4.9.7-stable review

On Tue, Jan 31, 2017 at 03:06:08PM -0700, Shuah Khan wrote: > On 01/30/2017 10:36 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.7 release. > > There are 66 patches in this series, all will be posted as a response > > to this one. If anyone has any

linux-next: Tree for Feb 1

Hi all, Changes since 20170131: Dropped tree: vfs-miklos (build failure and out of date) The vfs-miklos tree still had its build failure, so I just dropped it again for today. The v4l-dvb tree still had its build failure so I used the version from next-20170130. The net-next tree gained

Re: [PATCH 4.9 00/66] 4.9.7-stable review

On Tue, Jan 31, 2017 at 03:06:08PM -0700, Shuah Khan wrote: > On 01/30/2017 10:36 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.7 release. > > There are 66 patches in this series, all will be posted as a response > > to this one. If anyone has any

linux-next: Tree for Feb 1

Hi all, Changes since 20170131: Dropped tree: vfs-miklos (build failure and out of date) The vfs-miklos tree still had its build failure, so I just dropped it again for today. The v4l-dvb tree still had its build failure so I used the version from next-20170130. The net-next tree gained

Re: Staging: ks7010: clean up ks_hostif.h

On Tue, Jan 31, 2017 at 09:53:33PM -0800, Logan Gorence wrote: > >From 58defc62d53cb473f9d745127d98df834a10b321 Mon Sep 17 00:00:00 2001 > From: Logan Gorence > Date: Tue, 31 Jan 2017 21:51:05 -0800 > Subject: [PATCH] Staging: ks7010: clean up ks_hostif.h Why is this all

Re: Staging: ks7010: clean up ks_hostif.h

On Tue, Jan 31, 2017 at 09:53:33PM -0800, Logan Gorence wrote: > >From 58defc62d53cb473f9d745127d98df834a10b321 Mon Sep 17 00:00:00 2001 > From: Logan Gorence > Date: Tue, 31 Jan 2017 21:51:05 -0800 > Subject: [PATCH] Staging: ks7010: clean up ks_hostif.h Why is this all here in the body of your

Re: [PATCH v2 2/4] perf ftrace: Add ftrace.tracer config option

On 01/31/2017 10:15 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Jan 31, 2017 at 09:46:28AM -0300, Arnaldo Carvalho de Melo escreveu: Also you are silently ignoring any unknown variable in this section, so if someone has this: cat ~/.perfconfig [ftrace] trace = function I.e.

Re: [PATCH v2 2/4] perf ftrace: Add ftrace.tracer config option

On 01/31/2017 10:15 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Jan 31, 2017 at 09:46:28AM -0300, Arnaldo Carvalho de Melo escreveu: Also you are silently ignoring any unknown variable in this section, so if someone has this: cat ~/.perfconfig [ftrace] trace = function I.e.

Re: [PATCH 1/2] ARM: dts: i.MX25: add AIPS control registers

On Tue, Jan 31, 2017 at 08:20:01PM +0100, Martin Kaiser wrote: > The i.MX25 contains two AHB to IP bridges (AIPS), each of which has a set of > control registers. Add the memory regions for the control registers to > the Device Tree. > > All the registers from the i.MX53 AIPSTZ are present on the

Re: [PATCH 1/2] ARM: dts: i.MX25: add AIPS control registers

On Tue, Jan 31, 2017 at 08:20:01PM +0100, Martin Kaiser wrote: > The i.MX25 contains two AHB to IP bridges (AIPS), each of which has a set of > control registers. Add the memory regions for the control registers to > the Device Tree. > > All the registers from the i.MX53 AIPSTZ are present on the

Re: [PATCH v2 1/4] perf tools: Create for_each_event macro for tracepoints iteration

Hi, Arnaldo :) On 01/31/2017 09:21 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Jan 31, 2017 at 08:38:28PM +0900, Taeung Song escreveu: Such as for_each_subsystem and for_each_event in util/parse-events.c, add new macros 'for_each_event' for easy iteration over the tracepoints in order to be

Re: [PATCH v2 1/4] perf tools: Create for_each_event macro for tracepoints iteration

Hi, Arnaldo :) On 01/31/2017 09:21 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Jan 31, 2017 at 08:38:28PM +0900, Taeung Song escreveu: Such as for_each_subsystem and for_each_event in util/parse-events.c, add new macros 'for_each_event' for easy iteration over the tracepoints in order to be

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 11:34 PM, Dave Hansen wrote: > On 01/30/2017 11:25 PM, John Hubbard wrote: >> I also don't like having these policies hard-coded, and your 100x >> example above helps clarify what can go wrong about it. It would be >> nicer if, instead, we could better express the "distance" between

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 11:34 PM, Dave Hansen wrote: > On 01/30/2017 11:25 PM, John Hubbard wrote: >> I also don't like having these policies hard-coded, and your 100x >> example above helps clarify what can go wrong about it. It would be >> nicer if, instead, we could better express the "distance" between

Re: remove the cmd_type field from struct request

On 01/31/2017 07:02 PM, Jens Axboe wrote: On 01/31/2017 07:57 AM, Christoph Hellwig wrote: [1] which were a pain in the ass to untangle and debug during development, it's really time for it to die.. Outside of the patch series in question, how to we expedite the euthanasia of IDE? What

Re: remove the cmd_type field from struct request

On 01/31/2017 07:02 PM, Jens Axboe wrote: On 01/31/2017 07:57 AM, Christoph Hellwig wrote: [1] which were a pain in the ass to untangle and debug during development, it's really time for it to die.. Outside of the patch series in question, how to we expedite the euthanasia of IDE? What

RE: kernel 4.10-rcx iio helper question

On 1 February 2017 00:42:31 GMT+00:00, "Ken.Lin" wrote: > > >> -Original Message- >> From: Peter Rosin [mailto:p...@axentia.se] >> Sent: Tuesday, January 31, 2017 1:10 PM >> To: Ken.Lin; ji...@kernel.org >> Cc: knaac...@gmx.de; pme...@pmeerw.net;

RE: kernel 4.10-rcx iio helper question

On 1 February 2017 00:42:31 GMT+00:00, "Ken.Lin" wrote: > > >> -Original Message- >> From: Peter Rosin [mailto:p...@axentia.se] >> Sent: Tuesday, January 31, 2017 1:10 PM >> To: Ken.Lin; ji...@kernel.org >> Cc: knaac...@gmx.de; pme...@pmeerw.net; linux-...@vger.kernel.org; >linux- >>

Re: [PATCH v5 1/4] mm/migration: make isolate_movable_page() return int type

Hi Yisheng, On Tue, Jan 31, 2017 at 09:06:18PM +0800, ys...@foxmail.com wrote: > From: Yisheng Xie > > This patch changes the return type of isolate_movable_page() > from bool to int. It will return 0 when isolate movable page > successfully, return -EINVAL when the page

Re: [PATCH v5 1/4] mm/migration: make isolate_movable_page() return int type

Hi Yisheng, On Tue, Jan 31, 2017 at 09:06:18PM +0800, ys...@foxmail.com wrote: > From: Yisheng Xie > > This patch changes the return type of isolate_movable_page() > from bool to int. It will return 0 when isolate movable page > successfully, return -EINVAL when the page is not a non-lru

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 12:55 PM, John Hubbard wrote: > On 01/30/2017 05:57 PM, Dave Hansen wrote: >> On 01/30/2017 05:36 PM, Anshuman Khandual wrote: Let's say we had a CDM node with 100x more RAM than the rest of the system and it was just as fast as the rest of the RAM. Would we still

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 12:55 PM, John Hubbard wrote: > On 01/30/2017 05:57 PM, Dave Hansen wrote: >> On 01/30/2017 05:36 PM, Anshuman Khandual wrote: Let's say we had a CDM node with 100x more RAM than the rest of the system and it was just as fast as the rest of the RAM. Would we still

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 07:27 AM, Dave Hansen wrote: > On 01/30/2017 05:36 PM, Anshuman Khandual wrote: >>> Let's say we had a CDM node with 100x more RAM than the rest of the >>> system and it was just as fast as the rest of the RAM. Would we still >>> want it isolated like this? Or would we want a

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/31/2017 07:27 AM, Dave Hansen wrote: > On 01/30/2017 05:36 PM, Anshuman Khandual wrote: >>> Let's say we had a CDM node with 100x more RAM than the rest of the >>> system and it was just as fast as the rest of the RAM. Would we still >>> want it isolated like this? Or would we want a

[PATCH] block: queue lock must be acquired when iterating over rls

blk_set_queue_dying() does not acquire queue lock before it calls blk_queue_for_each_rl(). This allows a racing blkg_destroy() to remove blkg->q_node from the linked list and have blk_queue_for_each_rl() loop infitely over the removed blkg->q_node list node. Signed-off-by: Tahsin Erdogan

[PATCH] block: queue lock must be acquired when iterating over rls

blk_set_queue_dying() does not acquire queue lock before it calls blk_queue_for_each_rl(). This allows a racing blkg_destroy() to remove blkg->q_node from the linked list and have blk_queue_for_each_rl() loop infitely over the removed blkg->q_node list node. Signed-off-by: Tahsin Erdogan ---

Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

On Tue, Jan 31, 2017 at 04:39:28PM -0800, Andrew Morton wrote: > On Fri, 27 Jan 2017 20:44:30 +0200 Mike Rapoport > wrote: > > > When a non-cooperative userfaultfd monitor copies pages in the background, > > it may encounter regions that were already unmapped. Addition

Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

On Tue, Jan 31, 2017 at 04:39:28PM -0800, Andrew Morton wrote: > On Fri, 27 Jan 2017 20:44:30 +0200 Mike Rapoport > wrote: > > > When a non-cooperative userfaultfd monitor copies pages in the background, > > it may encounter regions that were already unmapped. Addition of > > UFFD_EVENT_UNMAP

Re: [PATCH v2 3/5] userfaultfd: non-cooperative: add event for exit() notification

On Tue, Jan 31, 2017 at 04:41:32PM -0800, Andrew Morton wrote: > On Fri, 27 Jan 2017 20:44:31 +0200 Mike Rapoport > wrote: > > > Allow userfaultfd monitor track termination of the processes that have > > memory backed by the uffd. > > > > --- a/fs/userfaultfd.c > > +++

Re: [PATCH v2 3/5] userfaultfd: non-cooperative: add event for exit() notification

On Tue, Jan 31, 2017 at 04:41:32PM -0800, Andrew Morton wrote: > On Fri, 27 Jan 2017 20:44:31 +0200 Mike Rapoport > wrote: > > > Allow userfaultfd monitor track termination of the processes that have > > memory backed by the uffd. > > > > --- a/fs/userfaultfd.c > > +++ b/fs/userfaultfd.c > >

Re: [PATCH 1/2 v3] mm: vmscan: do not pass reclaimed slab to vmpressure

On Tue, Jan 31, 2017 at 02:32:08PM +0530, Vinayak Menon wrote: > During global reclaim, the nr_reclaimed passed to vmpressure > includes the pages reclaimed from slab. But the corresponding > scanned slab pages is not passed. This can cause total reclaimed > pages to be greater than scanned,

Re: [PATCH 1/2 v3] mm: vmscan: do not pass reclaimed slab to vmpressure

On Tue, Jan 31, 2017 at 02:32:08PM +0530, Vinayak Menon wrote: > During global reclaim, the nr_reclaimed passed to vmpressure > includes the pages reclaimed from slab. But the corresponding > scanned slab pages is not passed. This can cause total reclaimed > pages to be greater than scanned,

linux-next: build warning after merge of the random tree

Hi Ted, [This actually appeared yesterday, but I missed it, sorry.] After merging the random tree, today's linux-next build (x86_64 allnoconfig) produced this warning: drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] static int

linux-next: build warning after merge of the random tree

Hi Ted, [This actually appeared yesterday, but I missed it, sorry.] After merging the random tree, today's linux-next build (x86_64 allnoconfig) produced this warning: drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] static int

Staging: ks7010: clean up ks_hostif.h

>From 58defc62d53cb473f9d745127d98df834a10b321 Mon Sep 17 00:00:00 2001 From: Logan Gorence Date: Tue, 31 Jan 2017 21:51:05 -0800 Subject: [PATCH] Staging: ks7010: clean up ks_hostif.h Clean up the errors in ks_hostif.h put out by checkpatch.pl. Signed-off by: Logan

Staging: ks7010: clean up ks_hostif.h

>From 58defc62d53cb473f9d745127d98df834a10b321 Mon Sep 17 00:00:00 2001 From: Logan Gorence Date: Tue, 31 Jan 2017 21:51:05 -0800 Subject: [PATCH] Staging: ks7010: clean up ks_hostif.h Clean up the errors in ks_hostif.h put out by checkpatch.pl. Signed-off by: Logan Gorence ---  

Re: [RFC 0/6]mm: add new LRU list for MADV_FREE pages

Hi Shaohua, On Sun, Jan 29, 2017 at 09:51:17PM -0800, Shaohua Li wrote: > Hi, > > We are trying to use MADV_FREE in jemalloc. Several issues are found. Without > solving the issues, jemalloc can't use the MADV_FREE feature. > - Doesn't support system without swap enabled. Because if swap is off,

Re: [RFC 0/6]mm: add new LRU list for MADV_FREE pages

Hi Shaohua, On Sun, Jan 29, 2017 at 09:51:17PM -0800, Shaohua Li wrote: > Hi, > > We are trying to use MADV_FREE in jemalloc. Several issues are found. Without > solving the issues, jemalloc can't use the MADV_FREE feature. > - Doesn't support system without swap enabled. Because if swap is off,

Re: [PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On 01/31/2017 06:22 PM, Krzysztof Kozlowski wrote: On Tue, Jan 31, 2017 at 2:01 AM, Inki Dae wrote: 2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글: Dear Thierry, Could you please review this patch? Thierry, I think this patch has been reviewed enough but no comment from

Re: [PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On 01/31/2017 06:22 PM, Krzysztof Kozlowski wrote: On Tue, Jan 31, 2017 at 2:01 AM, Inki Dae wrote: 2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글: Dear Thierry, Could you please review this patch? Thierry, I think this patch has been reviewed enough but no comment from you. Seems you are

Re: [PATCH 2/2] powerpc/pseries: Dynamically increase RMA size

Sukadev Bhattiprolu writes: > Paul Clarke [p...@us.ibm.com] wrote: > --- > > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001 I know it's been a while but I think it would still be good to get this in a shape that we can merge it. Comments

Re: [PATCH 2/2] powerpc/pseries: Dynamically increase RMA size

Sukadev Bhattiprolu writes: > Paul Clarke [p...@us.ibm.com] wrote: > --- > > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001 I know it's been a while but I think it would still be good to get this in a shape that we can merge it. Comments inline ... > From: root > Date:

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On 01/31/2017 12:48 PM, Eric Anholt wrote: I've been maintaining the bcm2835 branches here for a year or so. Acked-by: Stephen Warren

Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

On 01/31/2017 12:48 PM, Eric Anholt wrote: I've been maintaining the bcm2835 branches here for a year or so. Acked-by: Stephen Warren

Re: [PATCH v20 2/4] mailbox: mediatek: Add Mediatek CMDQ driver

On Thu, Jan 26, 2017 at 2:07 PM, Horng-Shyang Liao wrote: > Hi Jassi, > > On Thu, 2017-01-26 at 10:08 +0530, Jassi Brar wrote: >> On Wed, Jan 4, 2017 at 8:36 AM, HS Liao wrote: >> >> > diff --git a/drivers/mailbox/mtk-cmdq-mailbox.c >> >

Re: [PATCH v20 2/4] mailbox: mediatek: Add Mediatek CMDQ driver

On Thu, Jan 26, 2017 at 2:07 PM, Horng-Shyang Liao wrote: > Hi Jassi, > > On Thu, 2017-01-26 at 10:08 +0530, Jassi Brar wrote: >> On Wed, Jan 4, 2017 at 8:36 AM, HS Liao wrote: >> >> > diff --git a/drivers/mailbox/mtk-cmdq-mailbox.c >> > b/drivers/mailbox/mtk-cmdq-mailbox.c >> > new file mode

net: macb: lack of statistics - tx_dropped

macb doesn't maintain statistics of dropped packets when transmitting. so that it's not possible to detect packet loss in user space (sysfs, procfs...) macb_start_xmit should to increase tx_dropped in case of exception - buffer full, dma mapping fail Davy

net: macb: lack of statistics - tx_dropped

macb doesn't maintain statistics of dropped packets when transmitting. so that it's not possible to detect packet loss in user space (sysfs, procfs...) macb_start_xmit should to increase tx_dropped in case of exception - buffer full, dma mapping fail Davy

pri hiadani partnera!

Ahoj, Som zastupca investicneho zaujmu o zaujem zahranicnych investícii zahrnajuce velky objem financnych prostriedkov, u ktorych sa snazime svoju ucast ako v zamori zastupcu. Moj klient, ktory je rodak z Thajska, ma nejake peniaze zo svojich obchodnych uspor chce investovať na základe

pri hiadani partnera!

Ahoj, Som zastupca investicneho zaujmu o zaujem zahranicnych investícii zahrnajuce velky objem financnych prostriedkov, u ktorych sa snazime svoju ucast ako v zamori zastupcu. Moj klient, ktory je rodak z Thajska, ma nejake peniaze zo svojich obchodnych uspor chce investovať na základe

Re: [PATCHv2 00/11] KVM implementation of PAPR HPT resizing extension

On Wed, Feb 01, 2017 at 03:56:36PM +1100, David Gibson wrote: > On Wed, Feb 01, 2017 at 09:18:13AM +1100, Paul Mackerras wrote: > > On Tue, Dec 20, 2016 at 04:48:56PM +1100, David Gibson wrote: > > > Here is the KVM implementation for the proposed PAPR extension which > > > allows the runtime

Re: [PATCHv2 00/11] KVM implementation of PAPR HPT resizing extension

On Wed, Feb 01, 2017 at 03:56:36PM +1100, David Gibson wrote: > On Wed, Feb 01, 2017 at 09:18:13AM +1100, Paul Mackerras wrote: > > On Tue, Dec 20, 2016 at 04:48:56PM +1100, David Gibson wrote: > > > Here is the KVM implementation for the proposed PAPR extension which > > > allows the runtime

Re: [PATCHv2 00/11] KVM implementation of PAPR HPT resizing extension

On Wed, Feb 01, 2017 at 09:18:13AM +1100, Paul Mackerras wrote: > On Tue, Dec 20, 2016 at 04:48:56PM +1100, David Gibson wrote: > > Here is the KVM implementation for the proposed PAPR extension which > > allows the runtime resizing of a PAPR guest's Hashed Page Table (HPT). > > > > Using this

Re: [PATCHv2 00/11] KVM implementation of PAPR HPT resizing extension

On Wed, Feb 01, 2017 at 09:18:13AM +1100, Paul Mackerras wrote: > On Tue, Dec 20, 2016 at 04:48:56PM +1100, David Gibson wrote: > > Here is the KVM implementation for the proposed PAPR extension which > > allows the runtime resizing of a PAPR guest's Hashed Page Table (HPT). > > > > Using this

[PATCH v3] PCI: exynos: refactor exynos pcie driver

From: Niyas Ahmed S T Currently Exynos PCIe driver is only supported for Exynos5440 SoC. This patch does refactoring of Exynos PCIe driver to extend support for other Exynos SoC. Following are the main changes done via this patch: 1) It adds separate structs for

[PATCH v3] PCI: exynos: refactor exynos pcie driver

From: Niyas Ahmed S T Currently Exynos PCIe driver is only supported for Exynos5440 SoC. This patch does refactoring of Exynos PCIe driver to extend support for other Exynos SoC. Following are the main changes done via this patch: 1) It adds separate structs for memory, clock resources.

linux-next: manual merge of the char-misc tree with the driver-core tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: Documentation/driver-api/index.rst between commit: 113ccc38378b ("firmware: revamp firmware documentation") from the driver-core tree and commit: cadf8106661c ("doc: convert UIO howto from docbook to sphinx")

linux-next: manual merge of the char-misc tree with the driver-core tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: Documentation/driver-api/index.rst between commit: 113ccc38378b ("firmware: revamp firmware documentation") from the driver-core tree and commit: cadf8106661c ("doc: convert UIO howto from docbook to sphinx")

[PATCH 1/2] blk-mq: allocate blk_mq_tags and requests in correct node

blk_mq_tags/requests of specific hardware queue are mostly used in specific cpus, which might not be in the same numa node as disk. For example, a nvme card is in node 0. half hardware queue will be used by node 0, the other node 1. Signed-off-by: Shaohua Li --- block/blk-mq.c | 14

[PATCH 2/2] nvme: allocate nvme_queue in correct node

nvme_queue is per-cpu queue (mostly). Allocating it in node where blk-mq will use it. Signed-off-by: Shaohua Li --- drivers/nvme/host/pci.c | 19 +++ 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c

[PATCH 1/2] blk-mq: allocate blk_mq_tags and requests in correct node

blk_mq_tags/requests of specific hardware queue are mostly used in specific cpus, which might not be in the same numa node as disk. For example, a nvme card is in node 0. half hardware queue will be used by node 0, the other node 1. Signed-off-by: Shaohua Li --- block/blk-mq.c | 14

[PATCH 2/2] nvme: allocate nvme_queue in correct node

nvme_queue is per-cpu queue (mostly). Allocating it in node where blk-mq will use it. Signed-off-by: Shaohua Li --- drivers/nvme/host/pci.c | 19 +++ 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index

Re: [PATCH] jbd2: Fix use after free in kjournald2()

On 1/31/2017 9:21 PM, Jan Kara wrote: On Tue 31-01-17 20:08:57, Sahitya Tummala wrote: Below is the synchronization issue between unmount and kjournald2 contexts, which results into use after free issue in kjournald2(). Fix this issue by using journal->j_state_lock to synchronize the

Re: [PATCH] jbd2: Fix use after free in kjournald2()

On 1/31/2017 9:21 PM, Jan Kara wrote: On Tue 31-01-17 20:08:57, Sahitya Tummala wrote: Below is the synchronization issue between unmount and kjournald2 contexts, which results into use after free issue in kjournald2(). Fix this issue by using journal->j_state_lock to synchronize the

Re: [PATCH 13/17] net: stmmac: Implement NAPI for TX

From: Corentin Labbe Date: Tue, 31 Jan 2017 10:11:48 +0100 > The stmmac driver run TX completion under NAPI but without checking > the work done by the TX completion function. The current behavior is correct and completely intentional. A driver should _never_ account

Re: [PATCH 13/17] net: stmmac: Implement NAPI for TX

From: Corentin Labbe Date: Tue, 31 Jan 2017 10:11:48 +0100 > The stmmac driver run TX completion under NAPI but without checking > the work done by the TX completion function. The current behavior is correct and completely intentional. A driver should _never_ account TX work to the NAPI poll

[PATCH v2 00/01] KVM: x86: never specify a sample period for virtualized in_tx_cp counters

Changes in version 2: - Fixed block comment formatting as requested by Ingo Molnar - Changed commit summary to refer to a testcase that more easily shows the problem. For reference here's a complete testcase for an Intel TSX-enabled KVM guest: #include #include #include #include #include

[PATCH v2 00/01] KVM: x86: never specify a sample period for virtualized in_tx_cp counters

Changes in version 2: - Fixed block comment formatting as requested by Ingo Molnar - Changed commit summary to refer to a testcase that more easily shows the problem. For reference here's a complete testcase for an Intel TSX-enabled KVM guest: #include #include #include #include #include

[PATCH v2 01/01] KVM: x86: never specify a sample period for virtualized in_tx_cp counters

pmc_reprogram_counter() always sets a sample period based on the value of pmc->counter. However, hsw_hw_config() rejects sample periods less than 2^31 - 1. So for example, if a KVM guest does struct perf_event_attr attr; memset(, 0, sizeof(attr)); attr.type = PERF_TYPE_RAW;

[PATCH v2 01/01] KVM: x86: never specify a sample period for virtualized in_tx_cp counters

pmc_reprogram_counter() always sets a sample period based on the value of pmc->counter. However, hsw_hw_config() rejects sample periods less than 2^31 - 1. So for example, if a KVM guest does struct perf_event_attr attr; memset(, 0, sizeof(attr)); attr.type = PERF_TYPE_RAW;

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Wed, 2017-02-01 at 08:46 +1100, James Morris wrote: > On Tue, 31 Jan 2017, Jarkko Sakkinen wrote: > > > James, > > > > The discussion is about two features: > > > > 1. Extension to tpm_pcr_extend() (used by IMA) to extend all PCR banks > >instead of just SHA-1 banks. It is recommended by

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Wed, 2017-02-01 at 08:46 +1100, James Morris wrote: > On Tue, 31 Jan 2017, Jarkko Sakkinen wrote: > > > James, > > > > The discussion is about two features: > > > > 1. Extension to tpm_pcr_extend() (used by IMA) to extend all PCR banks > >instead of just SHA-1 banks. It is recommended by

linux-next: manual merge of the tip tree with the drm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/gpu/drm/ttm/ttm_bo.c between commit: 239ac65fa5ff ("drm/ttm: Make sure BOs being swapped out are cacheable") from the drm tree and commit: bdfafc4ffdd2 ("locking/atomic, kref: Kill kref_sub()") cf6c467d67d3

linux-next: manual merge of the tip tree with the drm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/gpu/drm/ttm/ttm_bo.c between commit: 239ac65fa5ff ("drm/ttm: Make sure BOs being swapped out are cacheable") from the drm tree and commit: bdfafc4ffdd2 ("locking/atomic, kref: Kill kref_sub()") cf6c467d67d3

Re: [PATCH] Btrfs: add another missing end_page_writeback on submit_extent_page failure

Thanks for your reply. I think you mentioned about the below if-block in __extent_writepage(). if (nr == 0) { /* make sure the mapping tag for page dirty gets cleared */ set_page_writeback(page); end_page_writeback(page); } However, this if-block only works when nr is

Re: [PATCH] Btrfs: add another missing end_page_writeback on submit_extent_page failure

Thanks for your reply. I think you mentioned about the below if-block in __extent_writepage(). if (nr == 0) { /* make sure the mapping tag for page dirty gets cleared */ set_page_writeback(page); end_page_writeback(page); } However, this if-block only works when nr is

Re: [PATCH] dt-bindings: display: move ANX7814 and SiI8620 bridge bindings

On 01/31/2017 11:24 PM, Rob Herring wrote: A few bindings snuck into bindings/video/bridge since consolidating everything under bindings/display/bridge/. Move them to the correct spot. Cc: Andrzej Hajda Cc: Archit Taneja Cc: Enric Balletbo i

Re: [PATCH] dt-bindings: display: move ANX7814 and SiI8620 bridge bindings

On 01/31/2017 11:24 PM, Rob Herring wrote: A few bindings snuck into bindings/video/bridge since consolidating everything under bindings/display/bridge/. Move them to the correct spot. Cc: Andrzej Hajda Cc: Archit Taneja Cc: Enric Balletbo i Serra Cc: Thierry Reding Signed-off-by: Rob

  1   2   3   4   5   6   7   8   9   10   >