[PATCH net-next] tun: fix build warnings

Stephen Rothwell reports a build warnings(powerpc ppc64_defconfig) drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized] int err; This is because tun_ring_recv() may

[PATCH net-next] tun: fix build warnings

Stephen Rothwell reports a build warnings(powerpc ppc64_defconfig) drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized] int err; This is because tun_ring_recv() may

Re: [PATCH v3 2/3] bcache: update document info

在 16/7/4 上午9:23, Yijing Wang 写道: > There is no return in continue_at(), update the documentation. > Thanks. Acked-by: Coly Li > Signed-off-by: Yijing Wang > --- > drivers/md/bcache/closure.c |2 +- > drivers/md/bcache/closure.h |3 ++- > 2

Re: [PATCH v3 2/3] bcache: update document info

在 16/7/4 上午9:23, Yijing Wang 写道: > There is no return in continue_at(), update the documentation. > Thanks. Acked-by: Coly Li > Signed-off-by: Yijing Wang > --- > drivers/md/bcache/closure.c |2 +- > drivers/md/bcache/closure.h |3 ++- > 2 files changed, 3 insertions(+), 2

linux-next: manual merge of the kvm tree with the kspp tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/vmx.c between commit: 255303026193 ("x86: apply more __ro_after_init and const") from the kspp tree and commit: c45dcc71b794 ("KVM: VMX: enable guest access to LMCE related MSRs") from the kvm tree. I

Re: [PATCH] netfilter: nf_conntrack_sip: CSeq 0 is a valid CSeq

2016-07-01 17:48 GMT+08:00 Christophe Leroy : > Do not drop packet when CSeq is 0 as 0 is also a valid value for CSeq. > > --- a/net/netfilter/nf_conntrack_sip.c > +++ b/net/netfilter/nf_conntrack_sip.c > @@ -1368,6 +1368,7 @@ static int process_sip_response(struct sk_buff

linux-next: manual merge of the kvm tree with the kspp tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/vmx.c between commit: 255303026193 ("x86: apply more __ro_after_init and const") from the kspp tree and commit: c45dcc71b794 ("KVM: VMX: enable guest access to LMCE related MSRs") from the kvm tree. I

Re: [PATCH] netfilter: nf_conntrack_sip: CSeq 0 is a valid CSeq

2016-07-01 17:48 GMT+08:00 Christophe Leroy : > Do not drop packet when CSeq is 0 as 0 is also a valid value for CSeq. > > --- a/net/netfilter/nf_conntrack_sip.c > +++ b/net/netfilter/nf_conntrack_sip.c > @@ -1368,6 +1368,7 @@ static int process_sip_response(struct sk_buff *skb, > unsigned int

[PATCH] fsl/fman: fix error handling

This is likely that checking 'fman->fifo_offset' instead of 'fman->cam_offset' is expected here. Signed-off-by: Christophe JAILLET --- The type of 'fifo_offset' may also need to be changed. --- drivers/net/ethernet/freescale/fman/fman.c | 2 +- 1 file changed, 1

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On (07/04/16 14:29), Joonsoo Kim wrote: > > > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > > > free_pages() tracking functionality. This adds to the dump_page_owner() > > > > output an

[PATCH] fsl/fman: fix error handling

This is likely that checking 'fman->fifo_offset' instead of 'fman->cam_offset' is expected here. Signed-off-by: Christophe JAILLET --- The type of 'fifo_offset' may also need to be changed. --- drivers/net/ethernet/freescale/fman/fman.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On (07/04/16 14:29), Joonsoo Kim wrote: > > > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > > > free_pages() tracking functionality. This adds to the dump_page_owner() > > > > output an

linux-next: build warnings after merge of the ftrace tree

Hi Steven, After merging the ftrace tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: WARNING: kernel/trace/libftrace.o(.text+0x9569): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats The function

linux-next: build warnings after merge of the ftrace tree

Hi Steven, After merging the ftrace tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: WARNING: kernel/trace/libftrace.o(.text+0x9569): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats The function

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On Mon, Jul 04, 2016 at 02:07:30PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (07/04/16 13:57), Joonsoo Kim wrote: > > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > > free_pages()

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On Mon, Jul 04, 2016 at 02:07:30PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (07/04/16 13:57), Joonsoo Kim wrote: > > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > > free_pages()

Re: [PATCH perf/core v13 04/15] perf/sdt: ELF support for SDT

On Fri, 1 Jul 2016 15:56:49 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:03:46PM +0900, Masami Hiramatsu escreveu: > > From: Hemant Kumar > > > > This patch serves the initial support to identify and list SDT events in > >

Re: [PATCH perf/core v13 04/15] perf/sdt: ELF support for SDT

On Fri, 1 Jul 2016 15:56:49 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:03:46PM +0900, Masami Hiramatsu escreveu: > > From: Hemant Kumar > > > > This patch serves the initial support to identify and list SDT events in > > binaries. > > When programs containing SDT

السر الخاصة بك الرقم السري: (25512560)

تهنئة حساب بريد إلكتروني حصل لك 90،00 $، USD من مايكروسوفت آسيا، ومايكروسوفت هي 41 عام وانتم لإرسال بياناتك الشخصية لهذا المكتب الآن تهنئة مرة أخرى.

السر الخاصة بك الرقم السري: (25512560)

تهنئة حساب بريد إلكتروني حصل لك 90،00 $، USD من مايكروسوفت آسيا، ومايكروسوفت هي 41 عام وانتم لإرسال بياناتك الشخصية لهذا المكتب الآن تهنئة مرة أخرى.

Re: linux-next: build warning after merge of the net-next tree

On 2016年07月04日 11:15, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used

Re: [GIT PULL] drm/mediatek: MT8173 gamma & dither support

Hi, Emil: On Sun, 2016-07-03 at 23:43 +0100, Emil Velikov wrote: > Hi Bibby, > > On 27 June 2016 at 12:29, Bibby Hsieh wrote: > > On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote: > >> > >> On 06/24/2016 09:27 AM, Bibby Hsieh wrote: > >> > Hi Dave, > >> > > >>

Re: linux-next: build warning after merge of the net-next tree

On 2016年07月04日 11:15, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used

Re: [GIT PULL] drm/mediatek: MT8173 gamma & dither support

Hi, Emil: On Sun, 2016-07-03 at 23:43 +0100, Emil Velikov wrote: > Hi Bibby, > > On 27 June 2016 at 12:29, Bibby Hsieh wrote: > > On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote: > >> > >> On 06/24/2016 09:27 AM, Bibby Hsieh wrote: > >> > Hi Dave, > >> > > >> > Please consider merging

Re: [PATCH 3/3] mm/page_owner: track page free call chain

Hello, On (07/04/16 13:57), Joonsoo Kim wrote: > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > free_pages() tracking functionality. This adds to the dump_page_owner() > > output an additional

Re: [PATCH 3/3] mm/page_owner: track page free call chain

Hello, On (07/04/16 13:57), Joonsoo Kim wrote: > On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > > free_pages() tracking functionality. This adds to the dump_page_owner() > > output an additional

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

2016-07-04 13:20 GMT+09:00 Andi Shyti : > Hi Tomasz, > >> > This patchset enables spi3 clocks by marking critical clocks as >> > CLK_IS_CRITICAL and in the meantime replaces the use of >> > CLK_IGNORE_UNUSED for spi1 clocks. >> > >> > The sclk needs to be considered

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

2016-07-04 13:20 GMT+09:00 Andi Shyti : > Hi Tomasz, > >> > This patchset enables spi3 clocks by marking critical clocks as >> > CLK_IS_CRITICAL and in the meantime replaces the use of >> > CLK_IGNORE_UNUSED for spi1 clocks. >> > >> > The sclk needs to be considered critical as well. >> > >> > The

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > free_pages() tracking functionality. This adds to the dump_page_owner() > output an additional backtrace, that tells us what path has freed the > page.

Re: [PATCH 3/3] mm/page_owner: track page free call chain

On Sun, Jul 03, 2016 at 01:16:56AM +0900, Sergey Senozhatsky wrote: > Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with > free_pages() tracking functionality. This adds to the dump_page_owner() > output an additional backtrace, that tells us what path has freed the > page.

Re: [PATCH] kasan: make depot_fetch_stack more robust

On Fri, Jul 01, 2016 at 07:38:18PM +0200, Dmitry Vyukov wrote: > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is >

Re: [PATCH] kasan: make depot_fetch_stack more robust

On Fri, Jul 01, 2016 at 07:38:18PM +0200, Dmitry Vyukov wrote: > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is >

Re: [PATCH 00/31] Move LRU page reclaim from zones to nodes v8

On Mon, Jul 04, 2016 at 10:37:03AM +0900, Minchan Kim wrote: > > The reason we have zone-based reclaim is that we used to have > > large highmem zones in common configurations and it was necessary > > to quickly find ZONE_NORMAL pages for reclaim. Today, this is much > > less of a concern as

Re: [PATCH 00/31] Move LRU page reclaim from zones to nodes v8

On Mon, Jul 04, 2016 at 10:37:03AM +0900, Minchan Kim wrote: > > The reason we have zone-based reclaim is that we used to have > > large highmem zones in common configurations and it was necessary > > to quickly find ZONE_NORMAL pages for reclaim. Today, this is much > > less of a concern as

Re: [RFC 08/12] lockdep: Apply crossrelease to PG_locked lock

On Fri, Jul 01, 2016 at 02:18:46PM +0300, Kirill A. Shutemov wrote: > On Fri, Jul 01, 2016 at 08:21:21AM +0900, Byungchul Park wrote: > > On Thu, Jun 30, 2016 at 03:04:58PM +0200, Peter Zijlstra wrote: > > > On Mon, Jun 20, 2016 at 01:55:23PM +0900, Byungchul Park wrote: > > > > @@ -215,6 +219,11

Re: [PATCH v3] kasan/quarantine: fix bugs on qlist_move_cache()

On Fri, Jul 01, 2016 at 05:17:10PM +0300, Andrey Ryabinin wrote: > > > On 07/01/2016 05:02 PM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > There are two bugs on qlist_move_cache(). One is that qlist's tail > > isn't set properly. curr->next can be NULL since

Re: [RFC 08/12] lockdep: Apply crossrelease to PG_locked lock

On Fri, Jul 01, 2016 at 02:18:46PM +0300, Kirill A. Shutemov wrote: > On Fri, Jul 01, 2016 at 08:21:21AM +0900, Byungchul Park wrote: > > On Thu, Jun 30, 2016 at 03:04:58PM +0200, Peter Zijlstra wrote: > > > On Mon, Jun 20, 2016 at 01:55:23PM +0900, Byungchul Park wrote: > > > > @@ -215,6 +219,11

Re: [PATCH v3] kasan/quarantine: fix bugs on qlist_move_cache()

On Fri, Jul 01, 2016 at 05:17:10PM +0300, Andrey Ryabinin wrote: > > > On 07/01/2016 05:02 PM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > There are two bugs on qlist_move_cache(). One is that qlist's tail > > isn't set properly. curr->next can be NULL since it is singly linked > >

[PATCH v4] kasan/quarantine: fix bugs on qlist_move_cache()

From: Joonsoo Kim There are two bugs on qlist_move_cache(). One is that qlist's tail isn't set properly. curr->next can be NULL since it is singly linked list and NULL value on tail is invalid if there is one item on qlist. Another one is that if cache is matched,

Re: linux-next: build failure after merge of the lightnvm tree

Hi Matias, On Thu, 30 Jun 2016 12:56:35 +1000 Stephen Rothwell wrote: > > After merging the lightnvm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "nvm_alloc_dev" [drivers/nvme/host/nvme-core.ko] undefined! > ERROR: "nvm_alloc_dev"

[PATCH v4] kasan/quarantine: fix bugs on qlist_move_cache()

From: Joonsoo Kim There are two bugs on qlist_move_cache(). One is that qlist's tail isn't set properly. curr->next can be NULL since it is singly linked list and NULL value on tail is invalid if there is one item on qlist. Another one is that if cache is matched, qlist_put() is called and it

Re: linux-next: build failure after merge of the lightnvm tree

Hi Matias, On Thu, 30 Jun 2016 12:56:35 +1000 Stephen Rothwell wrote: > > After merging the lightnvm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "nvm_alloc_dev" [drivers/nvme/host/nvme-core.ko] undefined! > ERROR: "nvm_alloc_dev"

Re: [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum

> > The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights > Landing) has an erratum where a processor thread setting the Accessed > or Dirty bits may not do so atomically against its checks for the > Present bit. This may cause a thread (which is about to page fault) > to set A

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

Hi Tomasz, > > This patchset enables spi3 clocks by marking critical clocks as > > CLK_IS_CRITICAL and in the meantime replaces the use of > > CLK_IGNORE_UNUSED for spi1 clocks. > > > > The sclk needs to be considered critical as well. > > > > The SPI3 in the tm2/tm2e boards will control an irled

Re: [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum

> > The Intel(R) Xeon Phi(TM) Processor x200 Family (codename: Knights > Landing) has an erratum where a processor thread setting the Accessed > or Dirty bits may not do so atomically against its checks for the > Present bit. This may cause a thread (which is about to page fault) > to set A

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

Hi Tomasz, > > This patchset enables spi3 clocks by marking critical clocks as > > CLK_IS_CRITICAL and in the meantime replaces the use of > > CLK_IGNORE_UNUSED for spi1 clocks. > > > > The sclk needs to be considered critical as well. > > > > The SPI3 in the tm2/tm2e boards will control an irled

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

Hi Andi, 2016-06-30 16:15 GMT+09:00 Andi Shyti : > Hi, > > This patchset enables spi3 clocks by marking critical clocks as > CLK_IS_CRITICAL and in the meantime replaces the use of > CLK_IGNORE_UNUSED for spi1 clocks. > > The sclk needs to be considered critical as well. >

Re: [PATCH v3 0/2] mark spi clocks as critical and enable spi3 clocks

Hi Andi, 2016-06-30 16:15 GMT+09:00 Andi Shyti : > Hi, > > This patchset enables spi3 clocks by marking critical clocks as > CLK_IS_CRITICAL and in the meantime replaces the use of > CLK_IGNORE_UNUSED for spi1 clocks. > > The sclk needs to be considered critical as well. > > The SPI3 in the

Re: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue

On 02.07.2016 22:46, Tejun Heo wrote: > On Sat, Jul 02, 2016 at 04:33:50PM +0530, Bhaktipriya Shridhar wrote: >> alloc_workqueue replaces deprecated create_singlethread_workqueue(). >> >> A dedicated workqueue has been used since work items need to be flushed >> as a group rather than

Re: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue

On 02.07.2016 22:46, Tejun Heo wrote: > On Sat, Jul 02, 2016 at 04:33:50PM +0530, Bhaktipriya Shridhar wrote: >> alloc_workqueue replaces deprecated create_singlethread_workqueue(). >> >> A dedicated workqueue has been used since work items need to be flushed >> as a group rather than

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Jul 3, 2016, at 11:08 PM, Al Viro wrote: > On Sun, Jul 03, 2016 at 08:37:22PM -0400, Oleg Drokin wrote: > >> Hm… This dates to sometime in 2006 and my memory is a bit hazy here. >> >> I think when we called into the open, it went into fifo open and stuck there >> waiting for the other

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Jul 3, 2016, at 11:08 PM, Al Viro wrote: > On Sun, Jul 03, 2016 at 08:37:22PM -0400, Oleg Drokin wrote: > >> Hm… This dates to sometime in 2006 and my memory is a bit hazy here. >> >> I think when we called into the open, it went into fifo open and stuck there >> waiting for the other

Re: [PATCH v9 01/10] clk: fix initial state of critical clock's parents

On Fri, 2016-07-01 at 18:21 -0700, Stephen Boyd wrote: > (Resending to everyone) > > On 06/22, Erin Lo wrote: > > From: James Liao > > > > This patch fixed wrong state of parent clocks if they are registered > > after critical clocks. > > > > Signed-off-by: James

Re: [PATCH v9 01/10] clk: fix initial state of critical clock's parents

On Fri, 2016-07-01 at 18:21 -0700, Stephen Boyd wrote: > (Resending to everyone) > > On 06/22, Erin Lo wrote: > > From: James Liao > > > > This patch fixed wrong state of parent clocks if they are registered > > after critical clocks. > > > > Signed-off-by: James Liao > > Signed-off-by: Erin

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

On Mon, Jul 4, 2016 at 10:37 AM, Alexandre Courbot wrote: > On Sun, Jul 3, 2016 at 12:21 AM, Markus Mayer > wrote: >> On 1 July 2016 at 18:18, Alexandre Courbot wrote: >>> On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

On Mon, Jul 4, 2016 at 10:37 AM, Alexandre Courbot wrote: > On Sun, Jul 3, 2016 at 12:21 AM, Markus Mayer > wrote: >> On 1 July 2016 at 18:18, Alexandre Courbot wrote: >>> On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer wrote: Call strtolower() rather than walking the string explicitly to

Re: [PATCH 6/8] mm/zsmalloc: keep comments consistent with code

On Mon, Jul 04, 2016 at 09:05:16AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:04PM +0800, Ganesh Mahendran wrote: > > some minor change of comments: > > 1). update zs_malloc(),zs_create_pool() function header > > 2). update "Usage of struct page fields" > > > > Signed-off-by:

Re: [PATCH 6/8] mm/zsmalloc: keep comments consistent with code

On Mon, Jul 04, 2016 at 09:05:16AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:04PM +0800, Ganesh Mahendran wrote: > > some minor change of comments: > > 1). update zs_malloc(),zs_create_pool() function header > > 2). update "Usage of struct page fields" > > > > Signed-off-by:

Re: [PATCH v2 1/1] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

On 2016년 07월 04일 11:47, Peter Chen wrote: > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: Chanwoo Choi > Cc: MyungJoo Ham > Cc: Kyungmin Park > Cc:

Re: [PATCH v2 1/1] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

On 2016년 07월 04일 11:47, Peter Chen wrote: > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: Chanwoo Choi > Cc: MyungJoo Ham > Cc: Kyungmin Park > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Signed-off-by: Peter Chen > --- >

Re: [PATCH 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice

On Mon, Jul 04, 2016 at 09:03:18AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:03PM +0800, Ganesh Mahendran wrote: > > Currently, if a class can not be merged, the max objects of zspage > > in that class may be calculated twice. > > > > This patch calculate max objects of zspage at

Re: [PATCH 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice

On Mon, Jul 04, 2016 at 09:03:18AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:03PM +0800, Ganesh Mahendran wrote: > > Currently, if a class can not be merged, the max objects of zspage > > in that class may be calculated twice. > > > > This patch calculate max objects of zspage at

Re: [PATCH 3/8] mm/zsmalloc: take obj index back from find_alloced_obj

On Mon, Jul 04, 2016 at 08:57:04AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:01PM +0800, Ganesh Mahendran wrote: > > the obj index value should be updated after return from > > find_alloced_obj() > > to avoid CPU buring caused by unnecessary object scanning. > >

Re: [PATCH 3/8] mm/zsmalloc: take obj index back from find_alloced_obj

On Mon, Jul 04, 2016 at 08:57:04AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:01PM +0800, Ganesh Mahendran wrote: > > the obj index value should be updated after return from > > find_alloced_obj() > > to avoid CPU buring caused by unnecessary object scanning. > >

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

Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]

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

Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]

[PATCH] ACPI/init: Correct the comments about acpi_subsystem_init

In acpi_subsystem_init, function acpi_enable_subsystem is called to do the real job. However with different flags passed to acpi_enable_subsystem, different code is executed. In acpi_subsystem_init with "~ACPI_NO_ACPI_ENABLE" passed in it will only switch over the platform to the ACPI mode. The

[PATCH] ACPI/init: Correct the comments about acpi_subsystem_init

In acpi_subsystem_init, function acpi_enable_subsystem is called to do the real job. However with different flags passed to acpi_enable_subsystem, different code is executed. In acpi_subsystem_init with "~ACPI_NO_ACPI_ENABLE" passed in it will only switch over the platform to the ACPI mode. The

Re: [PATCH 2/8] mm/zsmalloc: add per class compact trace event

Hi, Minchan: On Mon, Jul 04, 2016 at 08:49:21AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:00PM +0800, Ganesh Mahendran wrote: > > add per class compact trace event. It will show how many zs pages > > isolated, how many zs pages reclaimed. > > I don't know what you want with this

Re: [PATCH 2/8] mm/zsmalloc: add per class compact trace event

Hi, Minchan: On Mon, Jul 04, 2016 at 08:49:21AM +0900, Minchan Kim wrote: > On Fri, Jul 01, 2016 at 02:41:00PM +0800, Ganesh Mahendran wrote: > > add per class compact trace event. It will show how many zs pages > > isolated, how many zs pages reclaimed. > > I don't know what you want with this

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Sun, Jul 03, 2016 at 08:37:22PM -0400, Oleg Drokin wrote: > Hm… This dates to sometime in 2006 and my memory is a bit hazy here. > > I think when we called into the open, it went into fifo open and stuck there > waiting for the other opener. Something like that. And we cannot really be >

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Sun, Jul 03, 2016 at 08:37:22PM -0400, Oleg Drokin wrote: > Hm… This dates to sometime in 2006 and my memory is a bit hazy here. > > I think when we called into the open, it went into fifo open and stuck there > waiting for the other opener. Something like that. And we cannot really be >

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

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/mellanox/mlx5/core/en_main.c between commit: 29429f3300a3 ("net/mlx5e: Timeout if SQ doesn't flush during close") from the net tree and commit: 507f0c817f7a ("net/mlx5e: Add TXQ set max rate

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

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/mellanox/mlx5/core/en_main.c between commit: 29429f3300a3 ("net/mlx5e: Timeout if SQ doesn't flush during close") from the net tree and commit: 507f0c817f7a ("net/mlx5e: Add TXQ set max rate

Re: [PATCH v5 0/2] [media] atmel-isc: add driver for Atmel ISC

On 7/1/2016 20:20, Hans Verkuil wrote: Hi Songjun, First of all, please CC patch 2/2 to linux-media as well the next time you post this. I only see 1/2 on the mailinglist, and we need both. Secondly, before I can accept it you need to run the v4l2-compliance test first and I need to see

Re: [PATCH v5 0/2] [media] atmel-isc: add driver for Atmel ISC

On 7/1/2016 20:20, Hans Verkuil wrote: Hi Songjun, First of all, please CC patch 2/2 to linux-media as well the next time you post this. I only see 1/2 on the mailinglist, and we need both. Secondly, before I can accept it you need to run the v4l2-compliance test first and I need to see

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

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/mellanox/mlx5/core/en.h between commit: 6cd392a082de ("net/mlx5e: Handle RQ flush in error cases") from the net tree and commit: cb3c7fd4f839 ("net/mlx5e: Support adaptive RX coalescing")

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

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/ethernet/mellanox/mlx5/core/en.h between commit: 6cd392a082de ("net/mlx5e: Handle RQ flush in error cases") from the net tree and commit: cb3c7fd4f839 ("net/mlx5e: Support adaptive RX coalescing")

[PATCH v2 1/1] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

of_node_put needs to be called when the device node which is got from of_parse_phandle has finished using. Cc: Chanwoo Choi Cc: MyungJoo Ham Cc: Kyungmin Park Cc: Kukjin Kim Cc: Krzysztof Kozlowski

linux-next: manual merge of the thermal-soc tree with the thermal tree

Hi Eduardo, Today's linux-next merge of the thermal-soc tree got conflicts in: drivers/thermal/thermal_core.c drivers/thermal/thermal_helpers.c drivers/thermal/thermal_sysfs.c between commits from the thermal tree and the same (or similar) patches from the thermal-soc tree. It looks like

[PATCH v2 1/1] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

of_node_put needs to be called when the device node which is got from of_parse_phandle has finished using. Cc: Chanwoo Choi Cc: MyungJoo Ham Cc: Kyungmin Park Cc: Kukjin Kim Cc: Krzysztof Kozlowski Signed-off-by: Peter Chen --- Changes at v2: - It should define node as pointer, kbuild test

linux-next: manual merge of the thermal-soc tree with the thermal tree

Hi Eduardo, Today's linux-next merge of the thermal-soc tree got conflicts in: drivers/thermal/thermal_core.c drivers/thermal/thermal_helpers.c drivers/thermal/thermal_sysfs.c between commits from the thermal tree and the same (or similar) patches from the thermal-soc tree. It looks like

Re: [alsa-devel] [PATCH v5 6/9] ASoC: mediatek: add mt2701 platform driver implementation.

On Thu, 2016-06-30 at 21:39 +0800, Garlic Tseng wrote: > On Wed, 2016-06-29 at 20:13 +0100, Mark Brown wrote: > > On Fri, Jun 17, 2016 at 03:43:57PM +0800, Garlic Tseng wrote: > > > > > +static int mt2701_afe_i2s_set_clkdiv(struct snd_soc_dai *dai, int div_id, > > > +

Re: [alsa-devel] [PATCH v5 6/9] ASoC: mediatek: add mt2701 platform driver implementation.

On Thu, 2016-06-30 at 21:39 +0800, Garlic Tseng wrote: > On Wed, 2016-06-29 at 20:13 +0100, Mark Brown wrote: > > On Fri, Jun 17, 2016 at 03:43:57PM +0800, Garlic Tseng wrote: > > > > > +static int mt2701_afe_i2s_set_clkdiv(struct snd_soc_dai *dai, int div_id, > > > +

[PATCH] Update the maximum depth of C-state from 6 to 9

From: Chuansheng Liu Currently, CPUIDLE_STATE_MAX has been defined as 10 in the cpuidle head file, and max_cstate = CPUIDLE_STATE_MAX – 1, so 9 is the right maximum depth of C-state. This change is reflected in one place of the kernel-param file, but not in the other

[PATCH] Update the maximum depth of C-state from 6 to 9

From: Chuansheng Liu Currently, CPUIDLE_STATE_MAX has been defined as 10 in the cpuidle head file, and max_cstate = CPUIDLE_STATE_MAX – 1, so 9 is the right maximum depth of C-state. This change is reflected in one place of the kernel-param file, but not in the other place where I suggest

Re: [PATCH perf/core v13 06/15] perf buildid-cache: Scan and import user SDT events to probe cache

On Fri, 1 Jul 2016 15:22:01 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:04:10PM +0900, Masami Hiramatsu escreveu: > > From: Masami Hiramatsu > > > > perf buildid-cache --add scans given binary and add > > the SDT events

Re: [PATCH perf/core v13 06/15] perf buildid-cache: Scan and import user SDT events to probe cache

On Fri, 1 Jul 2016 15:22:01 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:04:10PM +0900, Masami Hiramatsu escreveu: > > From: Masami Hiramatsu > > > > perf buildid-cache --add scans given binary and add > > the SDT events to probe cache. "sdt_" prefix is appended for > >

[PATCH perf/core] [BUGFIX] perf-probe: Fix to show correct error message for $vars and $params

Fix to show correct error messages for $vars and $params because those special variables requires debug information to find the real variables or function parameters. E.g. without this fix; # perf probe -x /lib64/libc-2.23.so getaddrinfo \$params Failed to write event: Invalid argument

[PATCH perf/core] [BUGFIX] perf-probe: Fix to show correct error message for $vars and $params

Fix to show correct error messages for $vars and $params because those special variables requires debug information to find the real variables or function parameters. E.g. without this fix; # perf probe -x /lib64/libc-2.23.so getaddrinfo \$params Failed to write event: Invalid argument

[PATCH] regulator: core: Assign bool value to variable has_full_constraints

In commit 21cf891a (regulator: Make regulator_has_full_constraints a bool) type of variable has_full_constraints is changed to bool, so assign 'true' to has_full_constraints here. Signed-off-by: Baoquan He --- drivers/regulator/core.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] regulator: core: Assign bool value to variable has_full_constraints

In commit 21cf891a (regulator: Make regulator_has_full_constraints a bool) type of variable has_full_constraints is changed to bool, so assign 'true' to has_full_constraints here. Signed-off-by: Baoquan He --- drivers/regulator/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH perf/core v13 02/15] perf probe: Show all cached probes

On Fri, 1 Jul 2016 10:51:04 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:03:26PM +0900, Masami Hiramatsu escreveu: > > From: Masami Hiramatsu > > > > perf probe --list shows all cached probes when --cache > > is given.

Re: [PATCH v5 01/22] sh: Add sh-specific early_init_dt_reserve_memory_arch

On Mon, Jul 04, 2016 at 01:46:21AM +0900, Yoshinori Sato wrote: > sh used P1 address space in early device tree. > So need convert P1 to physical address before reserve memory. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/boards/of-generic.c | 12 >

Re: [PATCH perf/core v13 02/15] perf probe: Show all cached probes

On Fri, 1 Jul 2016 10:51:04 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Jul 01, 2016 at 05:03:26PM +0900, Masami Hiramatsu escreveu: > > From: Masami Hiramatsu > > > > perf probe --list shows all cached probes when --cache > > is given. Each caches are shown with on which binary that > >

Re: [PATCH v5 01/22] sh: Add sh-specific early_init_dt_reserve_memory_arch

On Mon, Jul 04, 2016 at 01:46:21AM +0900, Yoshinori Sato wrote: > sh used P1 address space in early device tree. > So need convert P1 to physical address before reserve memory. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/boards/of-generic.c | 12 > 1 file changed, 12

Re: [alsa-devel] [PATCH v5 7/9] ASoC: bt-sco: extend rate and add a general compatible string

On Sat, 2016-07-02 at 17:05 +0800, Chen-Yu Tsai wrote: Hi, > Could we also make this driver directly configurable from Kconfig, > and not just selected by platforms (currently Samsung) or by building > all coddecs? > > Thanks > ChenYu I'll add configure prompt for SND_SOC_BT_SCO in next

Re: [alsa-devel] [PATCH v5 7/9] ASoC: bt-sco: extend rate and add a general compatible string

On Sat, 2016-07-02 at 17:05 +0800, Chen-Yu Tsai wrote: Hi, > Could we also make this driver directly configurable from Kconfig, > and not just selected by platforms (currently Samsung) or by building > all coddecs? > > Thanks > ChenYu I'll add configure prompt for SND_SOC_BT_SCO in next

Update the maximum depth of C-state from 6 to 9

Currently, CPUIDLE_STATE_MAX has been defined as 10 in the cpuidle head file, and max_cstate = CPUIDLE_STATE_MAX – 1, so 9 is the right maximum depth of C-state. This change is reflected in one place of the kernel-param file, but not in the other place where I suggest changing. Signed-off-by:

Re: [PATCH v5 15/22] sh: Move common PCI stuff to arch/sh/kernel

On Mon, Jul 04, 2016 at 01:46:35AM +0900, Yoshinori Sato wrote: > Signed-off-by: Yoshinori Sato > --- > arch/sh/drivers/pci/Makefile | 2 - > arch/sh/drivers/pci/common.c | 162 > arch/sh/drivers/pci/pci.c| 320

  1   2   3   4   5   6   >