[tip:perf/urgent] perf ppc64le: Fix build failure when libelf is not present

Commit-ID: f046f3df665361d2f89e660f8c79ba164069f02a Gitweb: http://git.kernel.org/tip/f046f3df665361d2f89e660f8c79ba164069f02a Author: Ravi Bangoria AuthorDate: Thu, 11 Aug 2016 14:43:59 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 12 Aug 2016 14:39:48 -0300 perf

[tip:perf/urgent] perf symbols: Fix annotation of objects with debuginfo files

Commit-ID: 50de1a0c54cdbc69a6dbcbc323f53daf95a4050e Gitweb: http://git.kernel.org/tip/50de1a0c54cdbc69a6dbcbc323f53daf95a4050e Author: Anton Blanchard AuthorDate: Sat, 13 Aug 2016 11:55:33 +1000 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 15 Aug 2016 16:49:57 -0300 perf

[tip:perf/urgent] perf intel-pt: Fix ip compression

Commit-ID: e1717e0485af4f47fc4da1e979ac817f9ad61b0f Gitweb: http://git.kernel.org/tip/e1717e0485af4f47fc4da1e979ac817f9ad61b0f Author: Adrian Hunter AuthorDate: Wed, 20 Jul 2016 12:00:06 +0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf tools mem: Fix -t store option for record command

Commit-ID: 33da54fa86e29b87fe1e83bd0f15b4ef2be53ecb Gitweb: http://git.kernel.org/tip/33da54fa86e29b87fe1e83bd0f15b4ef2be53ecb Author: Jiri Olsa AuthorDate: Thu, 11 Aug 2016 10:50:57 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 12 Aug

[tip:perf/urgent] perf jitdump: Add the right header to get the major()/minor() definitions

Commit-ID: 49a7f01064a94c4fd6afb6b4f7e3ccc37d0edf99 Gitweb: http://git.kernel.org/tip/49a7f01064a94c4fd6afb6b4f7e3ccc37d0edf99 Author: Arnaldo Carvalho de Melo AuthorDate: Sat, 13 Aug 2016 01:12:10 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf intel-pt: Fix ip compression

Commit-ID: e1717e0485af4f47fc4da1e979ac817f9ad61b0f Gitweb: http://git.kernel.org/tip/e1717e0485af4f47fc4da1e979ac817f9ad61b0f Author: Adrian Hunter AuthorDate: Wed, 20 Jul 2016 12:00:06 +0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 12 Aug 2016 14:39:48 -0300 perf

[tip:perf/urgent] perf tools mem: Fix -t store option for record command

Commit-ID: 33da54fa86e29b87fe1e83bd0f15b4ef2be53ecb Gitweb: http://git.kernel.org/tip/33da54fa86e29b87fe1e83bd0f15b4ef2be53ecb Author: Jiri Olsa AuthorDate: Thu, 11 Aug 2016 10:50:57 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 12 Aug 2016 14:39:48 -0300 perf tools mem:

[tip:perf/urgent] perf jitdump: Add the right header to get the major()/minor() definitions

Commit-ID: 49a7f01064a94c4fd6afb6b4f7e3ccc37d0edf99 Gitweb: http://git.kernel.org/tip/49a7f01064a94c4fd6afb6b4f7e3ccc37d0edf99 Author: Arnaldo Carvalho de Melo AuthorDate: Sat, 13 Aug 2016 01:12:10 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 15 Aug 2016 13:10:28 -0300

Re: [GIT PULL v2 00/11] perf/urgent fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, this time with the request-pull output, the > patches are > exactly the same as yesterday's. > > - Arnaldo > > Build stats: > > # time dm > 1 70.159253018 alpine:3.4: Ok > 2 27.099391445

Re: [GIT PULL v2 00/11] perf/urgent fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, this time with the request-pull output, the > patches are > exactly the same as yesterday's. > > - Arnaldo > > Build stats: > > # time dm > 1 70.159253018 alpine:3.4: Ok > 2 27.099391445

[PATCH 0/3] toshiba_acpi: Functions cleanup

These set of patches make some cleanup in some of the driver's functions. The first patch changes the variables declaration, the second changes the error checking logic and the third simply fixes a typo found while making these changes. Azael Avalos (3): toshiba_acpi: Cleanup variable

[PATCH 3/3] toshiba_acpi: Fix typo in *_cooling_method_set function

This patch simply fixes a typo in the error string printed in such function. Signed-off-by: Azael Avalos --- drivers/platform/x86/toshiba_acpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/platform/x86/toshiba_acpi.c

[PATCH 0/3] toshiba_acpi: Functions cleanup

These set of patches make some cleanup in some of the driver's functions. The first patch changes the variables declaration, the second changes the error checking logic and the third simply fixes a typo found while making these changes. Azael Avalos (3): toshiba_acpi: Cleanup variable

[PATCH 3/3] toshiba_acpi: Fix typo in *_cooling_method_set function

This patch simply fixes a typo in the error string printed in such function. Signed-off-by: Azael Avalos --- drivers/platform/x86/toshiba_acpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/platform/x86/toshiba_acpi.c b/drivers/platform/x86/toshiba_acpi.c index

[PATCH 2/3] toshiba_acpi: Change error checking logic from TCI functions

Currently the success/error checking logic is intermixed, making the code a bit cumbersome to understand. This patch changes the affected functions to first check for errors and take appropriate actions, then check for the supported features. This patch also separates the error check from the

[PATCH 1/3] toshiba_acpi: Cleanup variable declaration

This patch moves all the multiple line variable declaration to a single line declaration (except variables being initialized) following the reverse tree order, to conform to the practices of the kernel. Signed-off-by: Azael Avalos --- drivers/platform/x86/toshiba_acpi.c

[PATCH 2/3] toshiba_acpi: Change error checking logic from TCI functions

Currently the success/error checking logic is intermixed, making the code a bit cumbersome to understand. This patch changes the affected functions to first check for errors and take appropriate actions, then check for the supported features. This patch also separates the error check from the

[PATCH 1/3] toshiba_acpi: Cleanup variable declaration

This patch moves all the multiple line variable declaration to a single line declaration (except variables being initialized) following the reverse tree order, to conform to the practices of the kernel. Signed-off-by: Azael Avalos --- drivers/platform/x86/toshiba_acpi.c | 98

[PATCH] toshiba_acpi: Fix the kbd_backlight_mode_show printed value

The mentioned function prints the value in decimal, but the documentation and its parent function available_kbd_modes_show are showing the value as hexadecimal. This patch simply changes the value printed from decimal to hex, as stated in the documentation and the parent function. Signed-off-by:

[PATCH] toshiba_acpi: Fix the kbd_backlight_mode_show printed value

The mentioned function prints the value in decimal, but the documentation and its parent function available_kbd_modes_show are showing the value as hexadecimal. This patch simply changes the value printed from decimal to hex, as stated in the documentation and the parent function. Signed-off-by:

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

console and in the >> > > output of >> > > the dmesg command. >> > Hey Geert. >> > >> > This doesn't apply to -next as the pr_notice/pr_cont below is >> > properly changed to a single pr_notice. >> In which -next? >> >>

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

of >> > > the dmesg command. >> > Hey Geert. >> > >> > This doesn't apply to -next as the pr_notice/pr_cont below is >> > properly changed to a single pr_notice. >> In which -next? >> >> Not in next-20160816, where the patch appli

Re: [PATCH 1/2] ASoC: rt5677: Add ACPI support

On Sun, Aug 14, 2016 at 12:18:22PM +0100, John Keeping wrote: > The Chromebook Pixel 2015 uses this codec with the ACPI ID RT5677CE, so > add an ACPI match table and support for reading properties from ACPI. This would be a lot easier to review with a concrete description of what "support for

Re: [PATCH 1/2] ASoC: rt5677: Add ACPI support

On Sun, Aug 14, 2016 at 12:18:22PM +0100, John Keeping wrote: > The Chromebook Pixel 2015 uses this codec with the ACPI ID RT5677CE, so > add an ACPI match table and support for reading properties from ACPI. This would be a lot easier to review with a concrete description of what "support for

Re: [PACTH v3 3/3] Documentation/filesystems: Added /proc/PID/totmaps documentation

On Tue, Aug 16, 2016 at 01:34:16PM -0400, robert.f...@collabora.com wrote: > + totmapsan extenssion based on maps, showing the total memory > +consumption of all mappings nit: s/extenssion/extension/ signature.asc Description: Digital signature

Re: [PACTH v3 3/3] Documentation/filesystems: Added /proc/PID/totmaps documentation

On Tue, Aug 16, 2016 at 01:34:16PM -0400, robert.f...@collabora.com wrote: > + totmapsan extenssion based on maps, showing the total memory > +consumption of all mappings nit: s/extenssion/extension/ signature.asc Description: Digital signature

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

g command. > > Hey Geert. > > > > This doesn't apply to -next as the pr_notice/pr_cont below is > > properly changed to a single pr_notice. > In which -next? > > Not in next-20160816, where the patch applies cleanly. > Also not in arm/for-next. My mistake, I was in t

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

eert. > > > > This doesn't apply to -next as the pr_notice/pr_cont below is > > properly changed to a single pr_notice. > In which -next? > > Not in next-20160816, where the patch applies cleanly. > Also not in arm/for-next. My mistake, I was in the wrong directory. It doesn't apply to Linus' tree. Still, it'd be slightly nicer to use a single pr_notice than the pr_notice/pr_cont. cheers, Joe

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Mel, thanks for taking a look. Your theory sounds more complete than mine, and since Dave is able to see the problem with 4.7, it would be nice to hear about the 4.6 behavior and commit ede37713737 in particular. That one seems more likely to affect contention than the zone/node one I found

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Mel, thanks for taking a look. Your theory sounds more complete than mine, and since Dave is able to see the problem with 4.7, it would be nice to hear about the 4.6 behavior and commit ede37713737 in particular. That one seems more likely to affect contention than the zone/node one I found

Re: [PATCH 5/7] arm64: dts: exynos: Add dts files for Samsung Exynos5433 64bit SoC

On Tue, Aug 16, 2016 at 09:59:26PM +0900, Chanwoo Choi wrote: > >> diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi > >> b/arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi > >> new file mode 100644 > >> index ..175121db367e > >> --- /dev/null > >> +++

Re: [PATCH 5/7] arm64: dts: exynos: Add dts files for Samsung Exynos5433 64bit SoC

On Tue, Aug 16, 2016 at 09:59:26PM +0900, Chanwoo Choi wrote: > >> diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi > >> b/arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi > >> new file mode 100644 > >> index ..175121db367e > >> --- /dev/null > >> +++

Re: [tip:x86/boot] x86/mm: Enable KASLR for physical mapping memory regions

On Tue, Aug 16, 2016 at 05:54:12PM +0200, Borislav Petkov wrote: > Ok, I ran this in a guest and it finds the microcode patches properly. Here's a better version to take care of the APs too: --- diff --git a/arch/x86/kernel/cpu/microcode/amd.c b/arch/x86/kernel/cpu/microcode/amd.c index

Re: [tip:x86/boot] x86/mm: Enable KASLR for physical mapping memory regions

On Tue, Aug 16, 2016 at 05:54:12PM +0200, Borislav Petkov wrote: > Ok, I ran this in a guest and it finds the microcode patches properly. Here's a better version to take care of the APs too: --- diff --git a/arch/x86/kernel/cpu/microcode/amd.c b/arch/x86/kernel/cpu/microcode/amd.c index

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

ine characters would be printed with >> a newline character appended, both on the console and in the output of >> the dmesg command. > > Hey Geert. > > This doesn't apply to -next as the pr_notice/pr_cont below is > properly changed to a single pr_notice. In which -next? Not in next-

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

th >> a newline character appended, both on the console and in the output of >> the dmesg command. > > Hey Geert. > > This doesn't apply to -next as the pr_notice/pr_cont below is > properly changed to a single pr_notice. In which -next? Not in next-20160816, where the patch

[PATCH] ARM: dts: msm8974: honami: Add touchscreen

Add the i2c2 and rmi4 nodes to enable the Synaptics touchscreen found in the Honami. Signed-off-by: Bjorn Andersson --- .../boot/dts/qcom-msm8974-sony-xperia-honami.dts | 59 ++ 1 file changed, 59 insertions(+) diff --git

[PATCH] ARM: dts: msm8974: honami: Add touchscreen

Add the i2c2 and rmi4 nodes to enable the Synaptics touchscreen found in the Honami. Signed-off-by: Bjorn Andersson --- .../boot/dts/qcom-msm8974-sony-xperia-honami.dts | 59 ++ 1 file changed, 59 insertions(+) diff --git

[PATCH v2] x86/tsc: Set X86_FEATURE_TSC_RELIABLE to skip refined calibration

On some newer Intel x86 processors/SoCs the TSC frequency can be directly calculated by factors read from specific MSR registers or from a cpuid leaf (0x15). TSC frequency calculated by native msr/cpuid is absolutely accurate so we should always skip calibrating TSC aginst another clock, e.g. PIT,

[PATCH v2] x86/tsc: Set X86_FEATURE_TSC_RELIABLE to skip refined calibration

On some newer Intel x86 processors/SoCs the TSC frequency can be directly calculated by factors read from specific MSR registers or from a cpuid leaf (0x15). TSC frequency calculated by native msr/cpuid is absolutely accurate so we should always skip calibrating TSC aginst another clock, e.g. PIT,

Re: Problem with atomic accesses in pstore on some ARM CPUs

On Mon, Aug 15, 2016 at 3:15 PM, Mark Rutland wrote: > On Tue, Aug 16, 2016 at 08:02:53AM -0700, Guenter Roeck wrote: >> On Tue, Aug 16, 2016 at 6:21 AM, Will Deacon wrote: >> > On Tue, Aug 16, 2016 at 06:14:53AM -0700, Guenter Roeck wrote: >> >> On

Re: Problem with atomic accesses in pstore on some ARM CPUs

On Mon, Aug 15, 2016 at 3:15 PM, Mark Rutland wrote: > On Tue, Aug 16, 2016 at 08:02:53AM -0700, Guenter Roeck wrote: >> On Tue, Aug 16, 2016 at 6:21 AM, Will Deacon wrote: >> > On Tue, Aug 16, 2016 at 06:14:53AM -0700, Guenter Roeck wrote: >> >> On Tue, Aug 16, 2016 at 3:32 AM, Robin Murphy

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

Re: uprobes: memory leak in enable/disable loop

On Tue, Aug 16, 2016 at 04:34:08PM +0200, Oleg Nesterov wrote: > @@ -172,8 +172,10 @@ static int __replace_page(struct vm_area > mmu_notifier_invalidate_range_start(mm, mmun_start, mmun_end); > err = -EAGAIN; > ptep = page_check_address(page, mm, addr, , 0); > - if (!ptep) >

Re: [PATCH v2] clk: Add fractional scale clock support

On Mon, Aug 15, 2016 at 5:14 PM, Stephen Boyd wrote: > Sorry I was away for some time. > > On 08/08, Hoan Tran wrote: >> On Wed, Jul 20, 2016 at 11:36 AM, Hoan Tran wrote: >> > On Fri, Jul 1, 2016 at 5:09 PM, Hoan Tran wrote: >> >> >> >> Hi

Re: uprobes: memory leak in enable/disable loop

On Tue, Aug 16, 2016 at 04:34:08PM +0200, Oleg Nesterov wrote: > @@ -172,8 +172,10 @@ static int __replace_page(struct vm_area > mmu_notifier_invalidate_range_start(mm, mmun_start, mmun_end); > err = -EAGAIN; > ptep = page_check_address(page, mm, addr, , 0); > - if (!ptep) >

Re: [PATCH v2] clk: Add fractional scale clock support

On Mon, Aug 15, 2016 at 5:14 PM, Stephen Boyd wrote: > Sorry I was away for some time. > > On 08/08, Hoan Tran wrote: >> On Wed, Jul 20, 2016 at 11:36 AM, Hoan Tran wrote: >> > On Fri, Jul 1, 2016 at 5:09 PM, Hoan Tran wrote: >> >> >> >> Hi Stephen, >> >> >> >> On Fri, Jul 1, 2016 at 11:38 AM,

[PACTH v3 3/3] Documentation/filesystems: Added /proc/PID/totmaps documentation

From: Robert Foss Added documentation covering /proc/PID/totmaps. Signed-off-by: Robert Foss --- Documentation/filesystems/proc.txt | 21 + 1 file changed, 21 insertions(+) diff --git

[PACTH v3 2/3] Documentation/filesystems: Fixed typo

From: Robert Foss Fixed a -> an typo. Signed-off-by: Robert Foss --- Documentation/filesystems/proc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/filesystems/proc.txt

[PACTH v3 3/3] Documentation/filesystems: Added /proc/PID/totmaps documentation

From: Robert Foss Added documentation covering /proc/PID/totmaps. Signed-off-by: Robert Foss --- Documentation/filesystems/proc.txt | 21 + 1 file changed, 21 insertions(+) diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index

[PACTH v3 2/3] Documentation/filesystems: Fixed typo

From: Robert Foss Fixed a -> an typo. Signed-off-by: Robert Foss --- Documentation/filesystems/proc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index e8d0075..7d001be 100644 ---

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Tue, Aug 16, 2016 at 04:20:56PM +0100, Catalin Marinas wrote: > diff --git a/include/linux/kmemleak.h b/include/linux/kmemleak.h > index 4894c6888bc6..380f72bc3657 100644 > --- a/include/linux/kmemleak.h > +++ b/include/linux/kmemleak.h > @@ -21,6 +21,7 @@ > #ifndef __KMEMLEAK_H > #define

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Tue, Aug 16, 2016 at 04:20:56PM +0100, Catalin Marinas wrote: > diff --git a/include/linux/kmemleak.h b/include/linux/kmemleak.h > index 4894c6888bc6..380f72bc3657 100644 > --- a/include/linux/kmemleak.h > +++ b/include/linux/kmemleak.h > @@ -21,6 +21,7 @@ > #ifndef __KMEMLEAK_H > #define

[PACTH v3 1/3] mm, proc: Implement /proc//totmaps

From: Robert Foss This is based on earlier work by Thiago Goncales. It implements a new per process proc file which summarizes the contents of the smaps file but doesn't display any addresses. It gives more detailed information than statm like the PSS (proprotional

[PACTH v3 1/3] mm, proc: Implement /proc//totmaps

From: Robert Foss This is based on earlier work by Thiago Goncales. It implements a new per process proc file which summarizes the contents of the smaps file but doesn't display any addresses. It gives more detailed information than statm like the PSS (proprotional set size). It differs from

[PACTH v3 0/3] Implement /proc//totmaps

From: Robert Foss This series provides the /proc/PID/totmaps feature, which summarizes the information provided by /proc/PID/smaps for improved performance and usability reasons. A use case is to speed up monitoring of memory consumption in environments where RSS

[PACTH v3 0/3] Implement /proc//totmaps

From: Robert Foss This series provides the /proc/PID/totmaps feature, which summarizes the information provided by /proc/PID/smaps for improved performance and usability reasons. A use case is to speed up monitoring of memory consumption in environments where RSS isn't precise. For example

RE: [PATCH 09/22] IB/qib: Remove deprecated create_singlethread_workqueue

> Subject: [PATCH 09/22] IB/qib: Remove deprecated > create_singlethread_workqueue > Looks and tests good! Tested-by: Mike Marciniszyn Acked-by: Mike Marciniszyn

RE: [PATCH 09/22] IB/qib: Remove deprecated create_singlethread_workqueue

> Subject: [PATCH 09/22] IB/qib: Remove deprecated > create_singlethread_workqueue > Looks and tests good! Tested-by: Mike Marciniszyn Acked-by: Mike Marciniszyn

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Wed, Aug 17, 2016 at 01:15:53AM +0800, kbuild test robot wrote: > [auto build test ERROR on mmotm/master] > [also build test ERROR on v4.8-rc2 next-20160816] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > >

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

On Wed, Aug 17, 2016 at 01:15:53AM +0800, kbuild test robot wrote: > [auto build test ERROR on mmotm/master] > [also build test ERROR on v4.8-rc2 next-20160816] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > >

Re: [PATCH 2/2] clk: fixed-rate: Remove export symbol on setup function

On 08/16, Geert Uytterhoeven wrote: > Hi Stephen, > > On Sat, Aug 13, 2016 at 3:50 AM, Stephen Boyd wrote: > > This function is only called by builtin code, but we always > > exported it and had marked it as __init before commit > > e4eda8e0654c (clk: remove exported

Re: [PATCH 2/2] clk: fixed-rate: Remove export symbol on setup function

On 08/16, Geert Uytterhoeven wrote: > Hi Stephen, > > On Sat, Aug 13, 2016 at 3:50 AM, Stephen Boyd wrote: > > This function is only called by builtin code, but we always > > exported it and had marked it as __init before commit > > e4eda8e0654c (clk: remove exported function from __init

Re: [PATCH 1/3] clk: meson: Add GXBB AO Clock and Reset controller driver

On 08/16, Neil Armstrong wrote: > On 08/13/2016 03:29 AM, Stephen Boyd wrote: > > On 08/09, Neil Armstrong wrote: > > >> + > >> +static struct clk_hw_onecell_data gxbb_aoclk_onecell_data = { > > > > can this be const? > > It would be awesome, but it will be discarded by of_clk_add_hw_provider :

Re: [PATCH 1/3] clk: meson: Add GXBB AO Clock and Reset controller driver

On 08/16, Neil Armstrong wrote: > On 08/13/2016 03:29 AM, Stephen Boyd wrote: > > On 08/09, Neil Armstrong wrote: > > >> + > >> +static struct clk_hw_onecell_data gxbb_aoclk_onecell_data = { > > > > can this be const? > > It would be awesome, but it will be discarded by of_clk_add_hw_provider :

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

Re: Problem with atomic accesses in pstore on some ARM CPUs

On Tue, Aug 16, 2016 at 08:02:53AM -0700, Guenter Roeck wrote: > On Tue, Aug 16, 2016 at 6:21 AM, Will Deacon wrote: > > On Tue, Aug 16, 2016 at 06:14:53AM -0700, Guenter Roeck wrote: > >> On Tue, Aug 16, 2016 at 3:32 AM, Robin Murphy wrote: > >> > On

Re: Problem with atomic accesses in pstore on some ARM CPUs

On Tue, Aug 16, 2016 at 08:02:53AM -0700, Guenter Roeck wrote: > On Tue, Aug 16, 2016 at 6:21 AM, Will Deacon wrote: > > On Tue, Aug 16, 2016 at 06:14:53AM -0700, Guenter Roeck wrote: > >> On Tue, Aug 16, 2016 at 3:32 AM, Robin Murphy wrote: > >> > On 16/08/16 00:19, Guenter Roeck wrote: > >> >>

Re: [PATCH v1 3/3] PM / AVS: rockchip-cpu-avs: add driver handling Rockchip cpu avs

Hi Finley, Am Dienstag, 16. August 2016, 10:38:59 schrieb Finlye Xiao: > From: Finley Xiao > > This patch supports adjusting opp's voltage according to leakage > > Signed-off-by: Finley Xiao we of course talked about this before and it

Re: [PATCH v1 3/3] PM / AVS: rockchip-cpu-avs: add driver handling Rockchip cpu avs

Hi Finley, Am Dienstag, 16. August 2016, 10:38:59 schrieb Finlye Xiao: > From: Finley Xiao > > This patch supports adjusting opp's voltage according to leakage > > Signed-off-by: Finley Xiao we of course talked about this before and it generally looks good, I just found a bunch of smaller

Re: [PATCH] phy: rockchip-inno-usb2: add COMMON_CLK dependency

On Tue, Aug 16, 2016 at 02:02:00PM +0800, Frank Wang wrote: > On kernel builds without COMMON_CLK, the newly added rockchip-inno-usb2 > driver fails to build: > > drivers/phy/phy-rockchip-inno-usb2.c:124:16: error: field 'clk480m_hw' > has incomplete type >struct clk_hw clk480m_hw; > > In

Re: [PATCH] phy: rockchip-inno-usb2: add COMMON_CLK dependency

On Tue, Aug 16, 2016 at 02:02:00PM +0800, Frank Wang wrote: > On kernel builds without COMMON_CLK, the newly added rockchip-inno-usb2 > driver fails to build: > > drivers/phy/phy-rockchip-inno-usb2.c:124:16: error: field 'clk480m_hw' > has incomplete type >struct clk_hw clk480m_hw; > > In

Re: [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Tue, Aug 16, 2016 at 09:59:00AM -0700, H. Peter Anvin wrote: > Dang... Isn't 9.3% improvement a good thing(tm) ? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --

Re: [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Tue, Aug 16, 2016 at 09:59:00AM -0700, H. Peter Anvin wrote: > Dang... Isn't 9.3% improvement a good thing(tm) ? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping

Hi Catalin, [auto build test ERROR on mmotm/master] [also build test ERROR on v4.8-rc2 next-20160816] [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/Catalin-Marinas/mm-kmemleak-Avoid-using-__va

[PATCH 1/4] dax: check resource alignment at dax region/device create

All the extents of a dax-device must match the alignment of the region. Otherwise, we are unable to guarantee fault semantics of a given page size. The region must be self-consistent itself as well. Signed-off-by: Dan Williams --- drivers/dax/dax.c | 22

[PATCH 1/4] dax: check resource alignment at dax region/device create

All the extents of a dax-device must match the alignment of the region. Otherwise, we are unable to guarantee fault semantics of a given page size. The region must be self-consistent itself as well. Signed-off-by: Dan Williams --- drivers/dax/dax.c | 22 +++--- 1 file

[PATCH 0/4] device-dax prepare for dynamic resize / allocate

In preparation for dynamic resize / allocation support: - convert device-dax instances to reserve memory ranges from their parent region - produce a 'seed' device instance to accept new allocation requests --- Dan Williams (4): dax: check resource alignment at dax region/device create

[PATCH 2/4] dax: add region-available-size attribute

In preparation for a facility that enables dax regions to be sub-divided, introduce a 'dax/available_size' attribute. This attribute appears under the parent device that registered the device-dax region, and it assumes that the device-dax-core owns the driver-data for that device.

[PATCH 3/4] dax: convert devm_create_dax_dev to PTR_ERR

For sub-division support we need access to the dax_dev created by devm_create_dax_dev(). Signed-off-by: Dan Williams --- drivers/dax/dax.c | 16 ++-- drivers/dax/dax.h |5 +++-- drivers/dax/pmem.c |5 +++-- 3 files changed, 16 insertions(+), 10

[PATCH 0/4] device-dax prepare for dynamic resize / allocate

In preparation for dynamic resize / allocation support: - convert device-dax instances to reserve memory ranges from their parent region - produce a 'seed' device instance to accept new allocation requests --- Dan Williams (4): dax: check resource alignment at dax region/device create

[PATCH 2/4] dax: add region-available-size attribute

In preparation for a facility that enables dax regions to be sub-divided, introduce a 'dax/available_size' attribute. This attribute appears under the parent device that registered the device-dax region, and it assumes that the device-dax-core owns the driver-data for that device.

[PATCH 3/4] dax: convert devm_create_dax_dev to PTR_ERR

For sub-division support we need access to the dax_dev created by devm_create_dax_dev(). Signed-off-by: Dan Williams --- drivers/dax/dax.c | 16 ++-- drivers/dax/dax.h |5 +++-- drivers/dax/pmem.c |5 +++-- 3 files changed, 16 insertions(+), 10 deletions(-) diff --git

RE: [PATCH v2] Added perf functionality to mmdc driver

> > Added cpumask and migration handling support to driver > > Validated event during event_init > > Added code to properly stop counters > > Used perf_invalid_context instead of perf_sw_context > > Added hrtimer to poll for overflow > > Added better description > >

[PATCH 4/4] dax: register seed device

Towards adding support for sub-dividing device-dax regions, add a seed device. Similar to libnvdimm a 'seed' device is un-configured device that is enabled after setting configuration parameters. After a given seed device is enabled another is created and this process repeats until no more seed

RE: [PATCH v2] Added perf functionality to mmdc driver

> > Added cpumask and migration handling support to driver > > Validated event during event_init > > Added code to properly stop counters > > Used perf_invalid_context instead of perf_sw_context > > Added hrtimer to poll for overflow > > Added better description > >

[PATCH 4/4] dax: register seed device

Towards adding support for sub-dividing device-dax regions, add a seed device. Similar to libnvdimm a 'seed' device is un-configured device that is enabled after setting configuration parameters. After a given seed device is enabled another is created and this process repeats until no more seed

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

On Tue, 2016-08-16 at 15:40 +0200, Geert Uytterhoeven wrote: > Before commit 874f9c7da9a4acbc ("printk: create pr_ functions"), > pr_*() calls without a trailing newline characters would be printed with > a newline character appended, both on the console and in the output of > the dmesg command.

[PATCH] Staging: android: ion: ion_test.c: fix parenthesis alignment

This fixes the checkpatch.pl "Alignment should match open parenthesis" issues in ion_test.c. Signed-off-by: Ben LeMasurier --- drivers/staging/android/ion/ion_test.c | 23 +-- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git

[PATCH] Staging: android: ion: ion_test.c: fix parenthesis alignment

This fixes the checkpatch.pl "Alignment should match open parenthesis" issues in ion_test.c. Signed-off-by: Ben LeMasurier --- drivers/staging/android/ion/ion_test.c | 23 +-- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git

Re: [PATCH v2] ARM: Add missing newline terminators to kernel messages

On Tue, 2016-08-16 at 15:40 +0200, Geert Uytterhoeven wrote: > Before commit 874f9c7da9a4acbc ("printk: create pr_ functions"), > pr_*() calls without a trailing newline characters would be printed with > a newline character appended, both on the console and in the output of > the dmesg command.

Re: perf: fuzzer WARNING event_function_local.constprop

On Tue, Aug 16, 2016 at 12:17:27PM -0400, Vince Weaver wrote: > On Tue, 16 Aug 2016, Peter Zijlstra wrote: > > > Could you see if the below cures things? > > > > --- > > kernel/events/core.c | 60 > > +--- > > 1 file changed, 48 insertions(+), 12

Re: perf: fuzzer WARNING event_function_local.constprop

On Tue, Aug 16, 2016 at 12:17:27PM -0400, Vince Weaver wrote: > On Tue, 16 Aug 2016, Peter Zijlstra wrote: > > > Could you see if the below cures things? > > > > --- > > kernel/events/core.c | 60 > > +--- > > 1 file changed, 48 insertions(+), 12

Re: [PATCH v2 4/6] kexec_file: Add mechanism to update kexec segments.

Hello Andrew, Thank you for your review! Am Montag, 15 August 2016, 15:27:56 schrieb Andrew Morton: > On Sat, 13 Aug 2016 00:18:23 -0300 Thiago Jung Bauermann > wrote: > > +/** > > + * kexec_update_segment - update the contents of a kimage segment > > + * @buffer:

Re: [PATCH v2 4/6] kexec_file: Add mechanism to update kexec segments.

Hello Andrew, Thank you for your review! Am Montag, 15 August 2016, 15:27:56 schrieb Andrew Morton: > On Sat, 13 Aug 2016 00:18:23 -0300 Thiago Jung Bauermann > wrote: > > +/** > > + * kexec_update_segment - update the contents of a kimage segment > > + * @buffer:New contents of the

Re: [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On August 16, 2016 7:26:43 AM PDT, kernel test robot wrote: > >FYI, we noticed a 9.3% improvement of will-it-scale.per_process_ops due >to commit: > >commit 65ea11ec6a82b1d44aba62b59e9eb20247e57c6e ("x86/hweight: Don't >clobber %rdi")

Re: [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On August 16, 2016 7:26:43 AM PDT, kernel test robot wrote: > >FYI, we noticed a 9.3% improvement of will-it-scale.per_process_ops due >to commit: > >commit 65ea11ec6a82b1d44aba62b59e9eb20247e57c6e ("x86/hweight: Don't >clobber %rdi")

<    3   4   5   6   7   8   9   10   11   12   >