Re: [PATCH V8 1/6] LIBIO: Introduce a generic PIO mapping method

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/LIBIO-Introduce

Re: [PATCH V8 1/6] LIBIO: Introduce a generic PIO mapping method

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/zhichang-yuan/LIBIO-Introduce

[RFC][PATCH 2/2] exec: If possible don't wait for ptraced threads to be reaped

Take advantage of the situation when sighand->count == 1 to only wait for threads to reach EXIT_ZOMBIE instead of EXIT_DEAD in de_thread. Only old old linux threading libraries use CLONE_SIGHAND without CLONE_THREAD. So this situation should be present most of the time. This allows ptracing

[RFC][PATCH 2/2] exec: If possible don't wait for ptraced threads to be reaped

Take advantage of the situation when sighand->count == 1 to only wait for threads to reach EXIT_ZOMBIE instead of EXIT_DEAD in de_thread. Only old old linux threading libraries use CLONE_SIGHAND without CLONE_THREAD. So this situation should be present most of the time. This allows ptracing

[RFC][PATCH 1/2] sighand: Count each thread group once in sighand_struct

In practice either a thread group is either using a sighand_struct or it isn't. Therefore simplify things a bit and only increment the count in sighand_struct when a new thread group is created that uses the existing sighand_struct, and only decrement the count in sighand_struct when a thread

[RFC][PATCH 1/2] sighand: Count each thread group once in sighand_struct

In practice either a thread group is either using a sighand_struct or it isn't. Therefore simplify things a bit and only increment the count in sighand_struct when a new thread group is created that uses the existing sighand_struct, and only decrement the count in sighand_struct when a thread

[RFC][PATCH 0/2] exec: Fixing ptrace'd mulit-threaded hang

I spent a little more time with this and only waiting until the killed thread are zombies (and not reaped as we do today) really looks like the right fix. Oleg the following two patches work on top of your PTRACE_EVENT_EXIT change and probably need a little more cleanup until they are ready for

[RFC][PATCH 0/2] exec: Fixing ptrace'd mulit-threaded hang

I spent a little more time with this and only waiting until the killed thread are zombies (and not reaped as we do today) really looks like the right fix. Oleg the following two patches work on top of your PTRACE_EVENT_EXIT change and probably need a little more cleanup until they are ready for

Re: [PATCH V2 net-next 1/7] ptr_ring: introduce batch dequeuing

On 2017年03月31日 22:31, Michael S. Tsirkin wrote: On Fri, Mar 31, 2017 at 11:52:24AM +0800, Jason Wang wrote: On 2017年03月30日 21:53, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:24PM +0800, Jason Wang wrote: This patch introduce a batched version of consuming, consumer can dequeue

Re: [PATCH V2 net-next 1/7] ptr_ring: introduce batch dequeuing

On 2017年03月31日 22:31, Michael S. Tsirkin wrote: On Fri, Mar 31, 2017 at 11:52:24AM +0800, Jason Wang wrote: On 2017年03月30日 21:53, Michael S. Tsirkin wrote: On Thu, Mar 30, 2017 at 03:22:24PM +0800, Jason Wang wrote: This patch introduce a batched version of consuming, consumer can dequeue

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

Hi, Michal, Michal Hocko writes: > On Fri 24-03-17 06:56:10, Dave Hansen wrote: >> On 03/24/2017 12:33 AM, John Hubbard wrote: >> > There might be some additional information you are using to come up with >> > that conclusion, that is not obvious to me. Any thoughts there?

Re: [PATCH -v2 1/2] mm, swap: Use kvzalloc to allocate some swap data structure

Hi, Michal, Michal Hocko writes: > On Fri 24-03-17 06:56:10, Dave Hansen wrote: >> On 03/24/2017 12:33 AM, John Hubbard wrote: >> > There might be some additional information you are using to come up with >> > that conclusion, that is not obvious to me. Any thoughts there? These >> > calls use

Re: [PATCH v13 3/6] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

Hi Jan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jan-Glauber/Cavium-MMC-driver/20170401-055302

Re: [PATCH v13 3/6] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

Hi Jan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jan-Glauber/Cavium-MMC-driver/20170401-055302

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, Apr 01, 2017 at 04:32:39AM +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, Apr 01, 2017 at 04:32:39AM +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 05:08 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 08:52:50PM -0700, Joe Perches wrote: > > > > MILD SUGGESTION: don't spell the function name out in format strings; > > > "this_function: foo is %d", n > > > might be better off as > > > "%s: foo is %d", __func__, n >

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 05:08 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 08:52:50PM -0700, Joe Perches wrote: > > > > MILD SUGGESTION: don't spell the function name out in format strings; > > > "this_function: foo is %d", n > > > might be better off as > > > "%s: foo is %d", __func__, n >

Re: [PATCH 2/2] ARM: dts: imx7: add USDHC NAND clock to SDHC instances

On 2017-03-31 20:03, Dong Aisheng wrote: > On Wed, Mar 29, 2017 at 05:50:29PM -0700, Stefan Agner wrote: >> The USDHC instances need the USDHC NAND clock in order to operate. >> Add the clock as ahb bus clock. >> >> Signed-off-by: Stefan Agner >> --- >>

Re: [PATCH 2/2] ARM: dts: imx7: add USDHC NAND clock to SDHC instances

On 2017-03-31 20:03, Dong Aisheng wrote: > On Wed, Mar 29, 2017 at 05:50:29PM -0700, Stefan Agner wrote: >> The USDHC instances need the USDHC NAND clock in order to operate. >> Add the clock as ahb bus clock. >> >> Signed-off-by: Stefan Agner >> --- >> arch/arm/boot/dts/imx7s.dtsi | 6 +++--- >>

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 08:52:50PM -0700, Joe Perches wrote: > > MILD SUGGESTION: don't spell the function name out in format strings; > > "this_function: foo is %d", n > > might be better off as > > "%s: foo is %d", __func__, n > > in case you ever move it to another function or rename

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 08:52:50PM -0700, Joe Perches wrote: > > MILD SUGGESTION: don't spell the function name out in format strings; > > "this_function: foo is %d", n > > might be better off as > > "%s: foo is %d", __func__, n > > in case you ever move it to another function or rename

Re: [PATCH v13 3/6] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

Hi Jan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jan-Glauber/Cavium-MMC-driver/20170401-055302

Re: [PATCH v13 3/6] mmc: cavium: Add MMC PCI driver for ThunderX SOCs

Hi Jan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jan-Glauber/Cavium-MMC-driver/20170401-055302

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 04:46 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 08:36:22PM -0700, Joe Perches wrote: > > On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > > > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > > > Replace string with formatted arguments in the dev_warn()

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 04:46 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 08:36:22PM -0700, Joe Perches wrote: > > On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > > > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > > > Replace string with formatted arguments in the dev_warn()

Re: [PATCH v23 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Xiongfeng Wang, On 1 April 2017 at 10:14, Xiongfeng Wang wrote: > > > On 2017/4/1 1:50, fu@linaro.org wrote: >> From: Fu Wei >> >> This patchset: >> (1)Preparation for adding GTDT support in arm_arch_timer: >> 1. Introduce a MMIO

Re: [PATCH v23 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Xiongfeng Wang, On 1 April 2017 at 10:14, Xiongfeng Wang wrote: > > > On 2017/4/1 1:50, fu@linaro.org wrote: >> From: Fu Wei >> >> This patchset: >> (1)Preparation for adding GTDT support in arm_arch_timer: >> 1. Introduce a MMIO CNTFRQ helper. >> 2. separate out

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 08:36:22PM -0700, Joe Perches wrote: > On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > > Replace string with formatted arguments in the dev_warn() call. It removes > > > the checkpatch warning: > > > > >

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 08:36:22PM -0700, Joe Perches wrote: > On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > > Replace string with formatted arguments in the dev_warn() call. It removes > > > the checkpatch warning: > > > > >

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function names []

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Sat, 2017-04-01 at 04:32 +0100, Al Viro wrote: > On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function names []

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 20:18 -0700, Chewie Lin wrote: > These are good points, but any feedback on the dev_warn() call itself? > I was trying to fix the checkpatch warning on my first try. Using "%s" with a long string is generally inefficient. Compare the compiled object size of

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 20:18 -0700, Chewie Lin wrote: > These are good points, but any feedback on the dev_warn() call itself? > I was trying to fix the checkpatch warning on my first try. Using "%s" with a long string is generally inefficient. Compare the compiled object size of

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

Re: [PATCH -mm -v7 4/9] mm, THP, swap: Add get_huge_swap_page()

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 12:28:17PM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> > On Tue, Mar 28, 2017 at 01:32:04PM +0800, Huang, Ying wrote: >> >> @@ -527,6 +527,23 @@ static inline swp_entry_t get_swap_page(void) >>

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 06:59:19PM -0700, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

Re: [PATCH -mm -v7 4/9] mm, THP, swap: Add get_huge_swap_page()

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 12:28:17PM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> > On Tue, Mar 28, 2017 at 01:32:04PM +0800, Huang, Ying wrote: >> >> @@ -527,6 +527,23 @@ static inline swp_entry_t get_swap_page(void) >> >> >> >> #endif /* CONFIG_SWAP */ >>

Re: [PATCH -mm -v7 1/9] mm, swap: Make swap cluster size same of THP size on x86_64

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 08:45:56AM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> >> > On Tue, Mar 28, 2017 at 01:32:01PM +0800, Huang, Ying wrote: >> >> @@ -499,6 +499,19 @@ config FRONTSWAP >> >> >> >> If

Re: [PATCH -mm -v7 1/9] mm, swap: Make swap cluster size same of THP size on x86_64

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 08:45:56AM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> >> > On Tue, Mar 28, 2017 at 01:32:01PM +0800, Huang, Ying wrote: >> >> @@ -499,6 +499,19 @@ config FRONTSWAP >> >> >> >> If unsure, say Y to enable frontswap. >> >> >>

Re: [PATCH] drivers: fixed a checkpatch warning

On Fri, Mar 31, 2017 at 11:53:55AM -0700, Joe Perches wrote: > On Fri, 2017-03-31 at 01:40 -0700, Chewie Lin wrote: > > fixed a coding style error/warning. > > > > Signed-off-by: Chewie Lin > > --- > > drivers/staging/vt6656/main_usb.c | 2 +- > > 1 file changed, 1

Re: [PATCH] drivers: fixed a checkpatch warning

On Fri, Mar 31, 2017 at 11:53:55AM -0700, Joe Perches wrote: > On Fri, 2017-03-31 at 01:40 -0700, Chewie Lin wrote: > > fixed a coding style error/warning. > > > > Signed-off-by: Chewie Lin > > --- > > drivers/staging/vt6656/main_usb.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) >

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 07:45:09PM -0700, Joe Perches wrote: > On Fri, 2017-03-31 at 19:15 -0700, Randy Dunlap wrote: > > On 03/31/17 18:59, Chewie Lin wrote: > > > Replace string with formatted arguments in the dev_warn() call. It removes > > > the checkpatch warning: > > > > > > WARNING:

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, Mar 31, 2017 at 07:45:09PM -0700, Joe Perches wrote: > On Fri, 2017-03-31 at 19:15 -0700, Randy Dunlap wrote: > > On 03/31/17 18:59, Chewie Lin wrote: > > > Replace string with formatted arguments in the dev_warn() call. It removes > > > the checkpatch warning: > > > > > > WARNING:

Re: [BUG nohz]: wrong user and system time accounting

On Sat, 1 Apr 2017 01:24:54 +0200 Frederic Weisbecker wrote: > On Fri, Mar 31, 2017 at 04:09:10PM -0400, Luiz Capitulino wrote: > > On Thu, 30 Mar 2017 17:25:46 -0400 > > Luiz Capitulino wrote: > > > > > On Thu, 30 Mar 2017 16:18:17 +0200 > > >

Re: [BUG nohz]: wrong user and system time accounting

On Sat, 1 Apr 2017 01:24:54 +0200 Frederic Weisbecker wrote: > On Fri, Mar 31, 2017 at 04:09:10PM -0400, Luiz Capitulino wrote: > > On Thu, 30 Mar 2017 17:25:46 -0400 > > Luiz Capitulino wrote: > > > > > On Thu, 30 Mar 2017 16:18:17 +0200 > > > Frederic Weisbecker wrote: > > > > > > > On

Re: [PATCH -mm -v7 9/9] mm, THP, swap: Delay splitting THP during swap out

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 12:15:13PM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> > On Tue, Mar 28, 2017 at 01:32:09PM +0800, Huang, Ying wrote: >> >> @@ -198,6 +240,18 @@ int add_to_swap(struct page *page, struct

Re: [PATCH -mm -v7 9/9] mm, THP, swap: Delay splitting THP during swap out

Johannes Weiner writes: > On Thu, Mar 30, 2017 at 12:15:13PM +0800, Huang, Ying wrote: >> Johannes Weiner writes: >> > On Tue, Mar 28, 2017 at 01:32:09PM +0800, Huang, Ying wrote: >> >> @@ -198,6 +240,18 @@ int add_to_swap(struct page *page, struct list_head >> >> *list) >> >>

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 19:15 -0700, Randy Dunlap wrote: > On 03/31/17 18:59, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function names > > #417: FILE:

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 19:15 -0700, Randy Dunlap wrote: > On 03/31/17 18:59, Chewie Lin wrote: > > Replace string with formatted arguments in the dev_warn() call. It removes > > the checkpatch warning: > > > > WARNING: Prefer using "%s", __func__ to embedded function names > > #417: FILE:

[PATCH] f2fs: remove the redundant variable definition

The variable 'i' has been defined before, so here we can use it directly. Signed-off-by: Kaixu Xia --- fs/f2fs/checkpoint.c |1 - 1 file changed, 1 deletion(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index 0339daf..2e42684 100644 ---

[PATCH] f2fs: remove the redundant variable definition

The variable 'i' has been defined before, so here we can use it directly. Signed-off-by: Kaixu Xia --- fs/f2fs/checkpoint.c |1 - 1 file changed, 1 deletion(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index 0339daf..2e42684 100644 --- a/fs/f2fs/checkpoint.c +++

[PATCH] staging: iio: light: constify attribute_group structures

As the event_attrs field of iio_info structures is constant, so these attribute_group structures can also be declared constant. File size before: textdata bss dec hex filename 150641528 0 1659240d0 drivers/staging/iio/light/tsl2x7x_core.o File size after:

[PATCH] staging: iio: light: constify attribute_group structures

As the event_attrs field of iio_info structures is constant, so these attribute_group structures can also be declared constant. File size before: textdata bss dec hex filename 150641528 0 1659240d0 drivers/staging/iio/light/tsl2x7x_core.o File size after:

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

On Fri, Mar 31, 2017 at 2:26 PM, Stas Sergeev wrote: > 31.03.2017 17:11, Alexandre Julliard пишет: >> >> In fact it would be nice to be able to make sidt/sgdt/etc. segfault >> too. I know a new syscall is a pain, > > Maybe arch_prctl() then? I still like my idea of a generic

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

On Fri, Mar 31, 2017 at 2:26 PM, Stas Sergeev wrote: > 31.03.2017 17:11, Alexandre Julliard пишет: >> >> In fact it would be nice to be able to make sidt/sgdt/etc. segfault >> too. I know a new syscall is a pain, > > Maybe arch_prctl() then? I still like my idea of a generic mechanism to turn

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 2017-03-31 21:57, Logan Gunthorpe wrote: On 31/03/17 05:51 PM, Sinan Kaya wrote: You can put a restriction with DMI/SMBIOS such that all devices from 2016 work else they belong to blacklist. How do you get a manufacturing date for a given device within the kernel? Is this actually

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 2017-03-31 21:57, Logan Gunthorpe wrote: On 31/03/17 05:51 PM, Sinan Kaya wrote: You can put a restriction with DMI/SMBIOS such that all devices from 2016 work else they belong to blacklist. How do you get a manufacturing date for a given device within the kernel? Is this actually

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 18:59 -0700, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On Fri, 2017-03-31 at 18:59 -0700, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

Re: [PATCH V8 5/6] ACPI: Support the probing on the devices which apply indirect-IO

On 04/01/2017 07:02 AM, Rafael J. Wysocki wrote: > On Fri, Mar 31, 2017 at 8:52 AM, zhichang.yuan > wrote: >> Hi, Rafael, >> >> Thanks for reviewing this! >> >> On 2017/3/31 4:31, Rafael J. Wysocki wrote: >>> On Thursday, March 30, 2017 11:26:58 PM zhichang.yuan

Re: [PATCH V8 5/6] ACPI: Support the probing on the devices which apply indirect-IO

On 04/01/2017 07:02 AM, Rafael J. Wysocki wrote: > On Fri, Mar 31, 2017 at 8:52 AM, zhichang.yuan > wrote: >> Hi, Rafael, >> >> Thanks for reviewing this! >> >> On 2017/3/31 4:31, Rafael J. Wysocki wrote: >>> On Thursday, March 30, 2017 11:26:58 PM zhichang.yuan wrote: On some

Re: [PATCH v23 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

On 2017/4/1 1:50, fu@linaro.org wrote: > From: Fu Wei > > This patchset: > (1)Preparation for adding GTDT support in arm_arch_timer: > 1. Introduce a MMIO CNTFRQ helper. > 2. separate out device-tree code from arch_timer_detect_rate > 3.

Re: [PATCH v23 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

On 2017/4/1 1:50, fu@linaro.org wrote: > From: Fu Wei > > This patchset: > (1)Preparation for adding GTDT support in arm_arch_timer: > 1. Introduce a MMIO CNTFRQ helper. > 2. separate out device-tree code from arch_timer_detect_rate > 3. remove

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On 03/31/17 18:59, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

Re: [PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

On 03/31/17 18:59, Chewie Lin wrote: > Replace string with formatted arguments in the dev_warn() call. It removes > the checkpatch warning: > > WARNING: Prefer using "%s", __func__ to embedded function names > #417: FILE: main_usb.c:417: > +

[PATCH 5/9] perf trace: Handle unpaired raw_syscalls:sys_exit event

From: Arnaldo Carvalho de Melo Which may happen when we start a tracing session and a thread is waiting for something like "poll" to return, in which case we better print "?" both for the syscall entry timestamp and for the duration. E.g.: Tracing existing mutt session: #

[PATCH 5/9] perf trace: Handle unpaired raw_syscalls:sys_exit event

From: Arnaldo Carvalho de Melo Which may happen when we start a tracing session and a thread is waiting for something like "poll" to return, in which case we better print "?" both for the syscall entry timestamp and for the duration. E.g.: Tracing existing mutt session: # perf trace -p

[PATCH 8/9] perf tools: Do not fail in case of empty HOME env variable

From: Jiri Olsa Currently we fail in the following case: $ unset HOME $ ./perf record ls $ echo $? 255 It's because the config code init fails due to a missing HOME variable value. Fix this by skipping the user config init if there's no HOME variable value.

[PATCH 7/9] tools include uapi: Grab copies of stat.h and fcntl.h

From: Arnaldo Carvalho de Melo We will need it to build tools/perf/trace/beauty/statx.h. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan

[PATCH 8/9] perf tools: Do not fail in case of empty HOME env variable

From: Jiri Olsa Currently we fail in the following case: $ unset HOME $ ./perf record ls $ echo $? 255 It's because the config code init fails due to a missing HOME variable value. Fix this by skipping the user config init if there's no HOME variable value. Reported-by: Jan Stancek

[PATCH 7/9] tools include uapi: Grab copies of stat.h and fcntl.h

From: Arnaldo Carvalho de Melo We will need it to build tools/perf/trace/beauty/statx.h. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: http://lkml.kernel.org/n/tip-nin41ve2fa63lrfbdr6x5...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo ---

[GIT PULL 0/9] perf/core improvements and fixes

into perf/core (2017-03-28 07:44:43 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.12-20170331 for you to fetch changes up to fd5cead23f54697310bd565aa2a23ae5128080a0: perf trace: Beautify statx syscall

[PATCH 6/9] perf utils: Fix spelling mistake: "Invalud" -> "Invalid"

From: Colin Ian King Trivial fix to spelling mistake in pr_debug message. Signed-off-by: Colin King Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Namhyung Kim Cc:

[GIT PULL 0/9] perf/core improvements and fixes

into perf/core (2017-03-28 07:44:43 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.12-20170331 for you to fetch changes up to fd5cead23f54697310bd565aa2a23ae5128080a0: perf trace: Beautify statx syscall

[PATCH 6/9] perf utils: Fix spelling mistake: "Invalud" -> "Invalid"

From: Colin Ian King Trivial fix to spelling mistake in pr_debug message. Signed-off-by: Colin King Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Namhyung Kim Cc: Krister Johansen Cc: Peter Zijlstra Cc: kernel-janit...@vger.kernel.org Link:

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

From: Ravi Bangoria SDT marker argument is in N@OP format. N is the size of argument and OP is the actual assembly operand. OP is arch dependent component and hence it's parsing logic also should be placed under tools/perf/arch/. Signed-off-by: Ravi Bangoria

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

From: Ravi Bangoria SDT marker argument is in N@OP format. N is the size of argument and OP is the actual assembly operand. OP is arch dependent component and hence it's parsing logic also should be placed under tools/perf/arch/. Signed-off-by: Ravi Bangoria Acked-by: Masami Hiramatsu Cc:

[PATCH 4/9] perf report: Drop cycles 0 for LBR print

From: Jin Yao For some platforms, for example Broadwell, it doesn't support cycles for LBR. But the perf always prints cycles:0, it's not necessary. The patch refactors the LBR info print code and drops the cycles:0. For example: perf report --branch-history

[PATCH 2/9] perf/sdt/x86: Add renaming logic for (missing) 8 bit registers

From: Ravi Bangoria I found couple of events using al, bl, cl and dl registers for argument. These are not directly accepted by uprobe_events and thus needs to be mapped to ax, bx, cx and dx respectively. Few ex, /usr/bin/qemu-system-s390x

[PATCH 1/9] perf tools: Remove support for command aliases

From: Arnaldo Carvalho de Melo This came from 'git', but isn't documented anywhere in tools/perf/Documentation/, looks like baggage we can do without, ditch it. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc:

[PATCH 2/9] perf/sdt/x86: Add renaming logic for (missing) 8 bit registers

From: Ravi Bangoria I found couple of events using al, bl, cl and dl registers for argument. These are not directly accepted by uprobe_events and thus needs to be mapped to ax, bx, cx and dx respectively. Few ex, /usr/bin/qemu-system-s390x css_adapter_interrupt: 1@%bl css_chpid_add:

[PATCH 1/9] perf tools: Remove support for command aliases

From: Arnaldo Carvalho de Melo This came from 'git', but isn't documented anywhere in tools/perf/Documentation/, looks like baggage we can do without, ditch it. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link:

[PATCH 4/9] perf report: Drop cycles 0 for LBR print

From: Jin Yao For some platforms, for example Broadwell, it doesn't support cycles for LBR. But the perf always prints cycles:0, it's not necessary. The patch refactors the LBR info print code and drops the cycles:0. For example: perf report --branch-history --no-children --stdio On

[PATCH 9/9] perf trace: Beautify statx syscall 'flag' and 'mask' arguments

From: Arnaldo Carvalho de Melo To test it, build samples/statx/test_statx, which I did as: $ make headers_install $ cc -I ~/git/linux/usr/include samples/statx/test-statx.c -o /tmp/statx And then use perf trace on it: # perf trace -e statx /tmp/statx /etc/passwd

[PATCH 9/9] perf trace: Beautify statx syscall 'flag' and 'mask' arguments

From: Arnaldo Carvalho de Melo To test it, build samples/statx/test_statx, which I did as: $ make headers_install $ cc -I ~/git/linux/usr/include samples/statx/test-statx.c -o /tmp/statx And then use perf trace on it: # perf trace -e statx /tmp/statx /etc/passwd statx(/etc/passwd) = 0

Re: [PATCH] dm ioctl: Remove double parentheses

On Fri, 2017-03-31 at 18:50 -0700, Matthias Kaehlcke wrote: > El Thu, Mar 16, 2017 at 09:48:30AM -0700 Matthias Kaehlcke ha dit: > > > The extra pair of parantheses is not needed and causes clang to generate > > the following warning: > > > > drivers/md/dm-ioctl.c:1776:11: error: equality

Re: [PATCH] dm ioctl: Remove double parentheses

On Fri, 2017-03-31 at 18:50 -0700, Matthias Kaehlcke wrote: > El Thu, Mar 16, 2017 at 09:48:30AM -0700 Matthias Kaehlcke ha dit: > > > The extra pair of parantheses is not needed and causes clang to generate > > the following warning: > > > > drivers/md/dm-ioctl.c:1776:11: error: equality

[PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

Replace string with formatted arguments in the dev_warn() call. It removes the checkpatch warning: WARNING: Prefer using "%s", __func__ to embedded function names #417: FILE: main_usb.c:417: +"usb_device_reset fail status=%d\n", status);

[PATCH 001/001] drivers/staging/vt6656/main_usb.c: checkpatch warning

Replace string with formatted arguments in the dev_warn() call. It removes the checkpatch warning: WARNING: Prefer using "%s", __func__ to embedded function names #417: FILE: main_usb.c:417: +"usb_device_reset fail status=%d\n", status);

Re: [PATCH] x86/intel_rdt: Add cpus_list rdtgroup file

On Thu, Mar 30, 2017 at 04:59:47PM +0200, Jiri Olsa wrote: > On Wed, Mar 29, 2017 at 06:16:00PM +0200, Jiri Olsa wrote: > > On Wed, Mar 29, 2017 at 09:08:26AM -0700, Fenghua Yu wrote: > > > On Wed, Mar 29, 2017 at 05:09:48PM +0200, Jiri Olsa wrote: > > > > While playing with the resctrl interface

[PATCH] eudyptula challenge

Hi all: Better and improved changelog version 3. I'm submitting this patch as part of Eudyptula challenge to fix a coding style problem. Thanks for taking time on this trivial patch. sl424 Chewie Lin (1): drivers/staging/vt6656/main_usb.c: checkpatch warning

Re: [PATCH] x86/intel_rdt: Add cpus_list rdtgroup file

On Thu, Mar 30, 2017 at 04:59:47PM +0200, Jiri Olsa wrote: > On Wed, Mar 29, 2017 at 06:16:00PM +0200, Jiri Olsa wrote: > > On Wed, Mar 29, 2017 at 09:08:26AM -0700, Fenghua Yu wrote: > > > On Wed, Mar 29, 2017 at 05:09:48PM +0200, Jiri Olsa wrote: > > > > While playing with the resctrl interface

[PATCH] eudyptula challenge

Hi all: Better and improved changelog version 3. I'm submitting this patch as part of Eudyptula challenge to fix a coding style problem. Thanks for taking time on this trivial patch. sl424 Chewie Lin (1): drivers/staging/vt6656/main_usb.c: checkpatch warning

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 31/03/17 05:51 PM, Sinan Kaya wrote: > You can put a restriction with DMI/SMBIOS such that all devices from 2016 > work else they belong to blacklist. How do you get a manufacturing date for a given device within the kernel? Is this actually something generically available? Logan

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 31/03/17 05:51 PM, Sinan Kaya wrote: > You can put a restriction with DMI/SMBIOS such that all devices from 2016 > work else they belong to blacklist. How do you get a manufacturing date for a given device within the kernel? Is this actually something generically available? Logan

[GIT PULL] nfsd bugfixes for 4.11

Please pull nfsd bugfixes from git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.11-1 The restriction of NFSv4 to TCP went overboard and also broke the backchannel; fix. Also some minor refinements to the nfsd version-setting interface that we'd like to get fixed before release. --b. Chuck

[GIT PULL] nfsd bugfixes for 4.11

Please pull nfsd bugfixes from git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.11-1 The restriction of NFSv4 to TCP went overboard and also broke the backchannel; fix. Also some minor refinements to the nfsd version-setting interface that we'd like to get fixed before release. --b. Chuck

Re: [PATCH] dm ioctl: Remove double parentheses

El Thu, Mar 16, 2017 at 09:48:30AM -0700 Matthias Kaehlcke ha dit: > The extra pair of parantheses is not needed and causes clang to generate > the following warning: > > drivers/md/dm-ioctl.c:1776:11: error: equality comparison with extraneous > parentheses [-Werror,-Wparentheses-equality] >

Re: [PATCH] dm ioctl: Remove double parentheses

El Thu, Mar 16, 2017 at 09:48:30AM -0700 Matthias Kaehlcke ha dit: > The extra pair of parantheses is not needed and causes clang to generate > the following warning: > > drivers/md/dm-ioctl.c:1776:11: error: equality comparison with extraneous > parentheses [-Werror,-Wparentheses-equality] >

  1   2   3   4   5   6   7   8   9   10   >