[PATCH 04/12] tracing: declare __{start,stop}_{annotated_,}branch_profile as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/trace_branch.c | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/kernel/trace/trace_branch.c b/kernel/trace/trace_branch.c index 3a2a737..47d78fd

[PATCH 02/12] firmware: declare {__start,__end}_builtin_fw as external array

The test in this loop: for (b_fw = __start_builtin_fw; b_fw != __end_builtin_fw; b_fw++) { was getting completely compiled out by my gcc, 7.0.0 20160520. The result was that the loop was going beyond the end of the builtin_fw array and giving me a page fault when trying to dereference

[PATCH 04/12] tracing: declare __{start,stop}_{annotated_,}branch_profile as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/trace_branch.c | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/kernel/trace/trace_branch.c b/kernel/trace/trace_branch.c index 3a2a737..47d78fd 100644 --- a/kernel/trace/trace_branch.c +++

[PATCH 02/12] firmware: declare {__start,__end}_builtin_fw as external array

The test in this loop: for (b_fw = __start_builtin_fw; b_fw != __end_builtin_fw; b_fw++) { was getting completely compiled out by my gcc, 7.0.0 20160520. The result was that the loop was going beyond the end of the builtin_fw array and giving me a page fault when trying to dereference

[PATCH 03/12] ftrace: declare __{start,stop}_mcount_loc as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/ftrace.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 2050a765..3c37036 100644 ---

[PATCH 03/12] ftrace: declare __{start,stop}_mcount_loc as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/ftrace.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 2050a765..3c37036 100644 --- a/kernel/trace/ftrace.c +++ b/kernel/trace/ftrace.c @@ -13,6

[PATCH] clk: uniphier: add system clock support for sLD3 SoC

I do not know why, but I missed to add this compatible string in the initial commit of this driver. Signed-off-by: Masahiro Yamada --- drivers/clk/uniphier/clk-uniphier-core.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH] clk: uniphier: add system clock support for sLD3 SoC

I do not know why, but I missed to add this compatible string in the initial commit of this driver. Signed-off-by: Masahiro Yamada --- drivers/clk/uniphier/clk-uniphier-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/clk/uniphier/clk-uniphier-core.c

[PATCH 2/3] arm64: dts: uniphier: add CPU clock and OPP table for LD11 SoC

Add a CPU clock to every CPU node and a CPU OPP table to use the generic cpufreq driver. Note: clock-latency-ns (300ns) was calculated based on the CPU-gear switch sequencer spec; it takes 12 clock cycles on the sequencer running at 50 MHz, plus a bit additional latency. Signed-off-by: Masahiro

[PATCH 0/3] arm64: dts: uniphier: switch to PSCI, DT-side support for cpufreq driver

The UniPhier clock driver was merged, and now ARM Trusted Firmware poring was finished. Now, I can upstream more features with this platform. Masahiro Yamada (3): arm64: dts: uniphier: switch over to PSCI enable method arm64: dts: uniphier: add CPU clock and OPP table for LD11 SoC arm64:

[PATCH 2/3] arm64: dts: uniphier: add CPU clock and OPP table for LD11 SoC

Add a CPU clock to every CPU node and a CPU OPP table to use the generic cpufreq driver. Note: clock-latency-ns (300ns) was calculated based on the CPU-gear switch sequencer spec; it takes 12 clock cycles on the sequencer running at 50 MHz, plus a bit additional latency. Signed-off-by: Masahiro

[PATCH 0/3] arm64: dts: uniphier: switch to PSCI, DT-side support for cpufreq driver

The UniPhier clock driver was merged, and now ARM Trusted Firmware poring was finished. Now, I can upstream more features with this platform. Masahiro Yamada (3): arm64: dts: uniphier: switch over to PSCI enable method arm64: dts: uniphier: add CPU clock and OPP table for LD11 SoC arm64:

Re: Intermittent perf build failures

On Sun, Oct 16, 2016 at 09:14:45AM +0200, Ingo Molnar wrote: > > * Laura Abbott wrote: > > > On 10/12/2016 03:12 AM, Jiri Olsa wrote: > > >On Tue, Oct 11, 2016 at 02:18:49PM -0700, Laura Abbott wrote: > > >>On 10/11/2016 01:59 PM, Jiri Olsa wrote: > > >>>On Tue, Oct 11, 2016

[PATCH 3/3] arm64: dts: uniphier: add CPU clocks and OPP tables for LD20 SoC

Add a CPU clock to every CPU node and CPU OPP tables to use the generic cpufreq driver. All the CPUs in each cluster share the same OPP table. Note: clock-latency-ns (300ns) was calculated based on the CPU-gear switch sequencer spec; it takes 12 clock cycles on the sequencer running at 50 MHz,

[PATCH 1/3] arm64: dts: uniphier: switch over to PSCI enable method

At the first system bring-up, I chose to use spin-table because ARM Trusted Firmware was not ready for this platform at that moment. Actually, these SoCs are equipped with EL3 and able to provide PSCI. Now I finished porting the ATF BL31 for the UniPhier platform, so it is ready to migrate to

Re: Intermittent perf build failures

On Sun, Oct 16, 2016 at 09:14:45AM +0200, Ingo Molnar wrote: > > * Laura Abbott wrote: > > > On 10/12/2016 03:12 AM, Jiri Olsa wrote: > > >On Tue, Oct 11, 2016 at 02:18:49PM -0700, Laura Abbott wrote: > > >>On 10/11/2016 01:59 PM, Jiri Olsa wrote: > > >>>On Tue, Oct 11, 2016 at 01:43:36PM

[PATCH 3/3] arm64: dts: uniphier: add CPU clocks and OPP tables for LD20 SoC

Add a CPU clock to every CPU node and CPU OPP tables to use the generic cpufreq driver. All the CPUs in each cluster share the same OPP table. Note: clock-latency-ns (300ns) was calculated based on the CPU-gear switch sequencer spec; it takes 12 clock cycles on the sequencer running at 50 MHz,

[PATCH 1/3] arm64: dts: uniphier: switch over to PSCI enable method

At the first system bring-up, I chose to use spin-table because ARM Trusted Firmware was not ready for this platform at that moment. Actually, these SoCs are equipped with EL3 and able to provide PSCI. Now I finished porting the ATF BL31 for the UniPhier platform, so it is ready to migrate to

Re: [RFC v2 0/2] proc connector: get namespace events

Alban Crequy writes: > This is v2 of the patch set to add namespace events in the proc > connector. So while not totally wrong the way you report namespaces makes me grumpy. You are not including the device node of the filesystem those inodes are on. The inode number

Re: [RFC v2 0/2] proc connector: get namespace events

Alban Crequy writes: > This is v2 of the patch set to add namespace events in the proc > connector. So while not totally wrong the way you report namespaces makes me grumpy. You are not including the device node of the filesystem those inodes are on. The inode number is meaningless if you

[PATCH v2 7/7] mtd: nand: move BBT code to drivers/mtd/nand/

Now that the BBT code is generic, we can move it to drivers/mtd/nand/. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/Kconfig | 3 +++ drivers/mtd/nand/Makefile | 4 drivers/mtd/nand/{raw/nand_bbt.c => bbt.c} | 5

[PATCH v2 0/7] mtd: nand: Abstract away the NAND interface type

Hi, This series is aiming at providing a generic NAND layer to share code between different NAND based devices. We currently have 3 different interfaces to interact with NANDs: - Raw NANDs - OneNANDs - SPI NANDs Apart from the way these NAND devices are accessed they have a lot in common, like

[PATCH v2 2/7] mtd: nand: move raw NAND related code to the raw/ subdir

As part of the process of sharing more code between different NAND based devices, we need to move all raw NAND related code to the raw/ subdirectory. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/Kconfig | 573

[PATCH v2] ARM: dts: imx6sx: Add UDOO Neo support

Add initial device trees for UDOO Neo Basic, Extended and Full boards: * Serial console is enabled, other serial ports are prepared. * I2C based PMIC is enabled. * Ethernet is enabled for Basic and Full. * SDHC is enabled, with the SDIO_PWR GPIO modeled as a regulator. * Both user LEDs are

[PATCH v2 1/7] mtd: nand: Rename nand.h into rawnand.h

We are planning to share more code between different NAND based devices (SPI NAND, OneNAND and raw NANDs), but before doing that we need to move the existing include/linux/mtd/nand.h file into include/linux/mtd/rawnand.h so we can later create a nand.h header containing all common structure and

[PATCH v2 7/7] mtd: nand: move BBT code to drivers/mtd/nand/

Now that the BBT code is generic, we can move it to drivers/mtd/nand/. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/Kconfig | 3 +++ drivers/mtd/nand/Makefile | 4 drivers/mtd/nand/{raw/nand_bbt.c => bbt.c} | 5 + drivers/mtd/nand/raw/Kconfig

[PATCH v2 0/7] mtd: nand: Abstract away the NAND interface type

Hi, This series is aiming at providing a generic NAND layer to share code between different NAND based devices. We currently have 3 different interfaces to interact with NANDs: - Raw NANDs - OneNANDs - SPI NANDs Apart from the way these NAND devices are accessed they have a lot in common, like

[PATCH v2 2/7] mtd: nand: move raw NAND related code to the raw/ subdir

As part of the process of sharing more code between different NAND based devices, we need to move all raw NAND related code to the raw/ subdirectory. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/Kconfig | 573 + drivers/mtd/nand/Makefile

[PATCH v2] ARM: dts: imx6sx: Add UDOO Neo support

Add initial device trees for UDOO Neo Basic, Extended and Full boards: * Serial console is enabled, other serial ports are prepared. * I2C based PMIC is enabled. * Ethernet is enabled for Basic and Full. * SDHC is enabled, with the SDIO_PWR GPIO modeled as a regulator. * Both user LEDs are

[PATCH v2 1/7] mtd: nand: Rename nand.h into rawnand.h

We are planning to share more code between different NAND based devices (SPI NAND, OneNAND and raw NANDs), but before doing that we need to move the existing include/linux/mtd/nand.h file into include/linux/mtd/rawnand.h so we can later create a nand.h header containing all common structure and

[PATCH v2 6/7] mtd: nand: raw: make BBT code more generic

BBT support is currently tightly tied to raw NAND, though this is the kind of code we could share across all NAND based devices, no matter what physical interface is to communicate with the NAND chip. Make BBT code interface agnostic by replacing all occurrence of struct nand_chip by struct

[PATCH v2 6/7] mtd: nand: raw: make BBT code more generic

BBT support is currently tightly tied to raw NAND, though this is the kind of code we could share across all NAND based devices, no matter what physical interface is to communicate with the NAND chip. Make BBT code interface agnostic by replacing all occurrence of struct nand_chip by struct

[PATCH v2 3/7] mtd: nand: add a nand.h file to expose basic NAND stuff

Now that raw NAND header has been moved to rawnand.h, we can add a new nand.h file and define the common nand stuff in there. Signed-off-by: Boris Brezillon --- include/linux/mtd/nand.h | 480 +++ 1 file changed,

[PATCH v2 5/7] mtd: nand: raw: create struct rawnand_device

Create the rawnand_device struct inheriting from nand_device and make nand_chip inherit from this struct. The rawnand_device object should be used for the new rawnand-device/rawnand-controller model, and fields inside nand_chip should progressively move to the future rawnand_controller or the

[PATCH v2 3/7] mtd: nand: add a nand.h file to expose basic NAND stuff

Now that raw NAND header has been moved to rawnand.h, we can add a new nand.h file and define the common nand stuff in there. Signed-off-by: Boris Brezillon --- include/linux/mtd/nand.h | 480 +++ 1 file changed, 480 insertions(+) create mode 100644

[PATCH v2 5/7] mtd: nand: raw: create struct rawnand_device

Create the rawnand_device struct inheriting from nand_device and make nand_chip inherit from this struct. The rawnand_device object should be used for the new rawnand-device/rawnand-controller model, and fields inside nand_chip should progressively move to the future rawnand_controller or the

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

   > [  121.111585] systemd-shutdown[1]: All swaps deactivated. >    > [  121.116661] systemd-shutdown[1]: Detaching loop devices.    >    > [  121.126395] systemd-shutdown[1]: All loop devices detached.     >    > [  121.130525] syst

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

t; [  121.111585] systemd-shutdown[1]: All swaps deactivated. >    > [  121.116661] systemd-shutdown[1]: Detaching loop devices.    >    > [  121.126395] systemd-shutdown[1]: All loop devices detached.     >    > [  121.130525] systemd-shutdown[1]: Detachin

Re: [tip:x86/urgent] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features

On Sun, Oct 16, 2016 at 04:21:49AM -0700, tip-bot for Piotr Luc wrote: > Commit-ID: a518dcc82b6162009c8ca3d169fe61c81536ff17 > Gitweb: http://git.kernel.org/tip/a518dcc82b6162009c8ca3d169fe61c81536ff17 > Author: Piotr Luc > AuthorDate: Wed, 12 Oct 2016 19:57:31 +0200

Re: [tip:x86/urgent] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features

On Sun, Oct 16, 2016 at 04:21:49AM -0700, tip-bot for Piotr Luc wrote: > Commit-ID: a518dcc82b6162009c8ca3d169fe61c81536ff17 > Gitweb: http://git.kernel.org/tip/a518dcc82b6162009c8ca3d169fe61c81536ff17 > Author: Piotr Luc > AuthorDate: Wed, 12 Oct 2016 19:57:31 +0200 > Committer: Ingo

core.c:undefined reference to `fpu_save'

Hi Andrew, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: c60f169202c7643991a8b4bfeea60e06843d5b5a arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h

core.c:undefined reference to `fpu_save'

Hi Andrew, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: c60f169202c7643991a8b4bfeea60e06843d5b5a arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h

Re: RFC - unclear change in "[media] DiBxxxx: Codingstype updates"

On Mon, Oct 10, 2016 at 08:31:12AM +0200, Patrick Boettcher wrote: > Hi, der Herr Hofrat ;-) > > On Sat, 8 Oct 2016 13:57:14 + > Nicholas Mc Guire wrote: > > - lo6 |= (1 << 2) | 2; > > - else > > - lo6 |= (1 << 2) | 1; > > +

Re: RFC - unclear change in "[media] DiBxxxx: Codingstype updates"

On Mon, Oct 10, 2016 at 08:31:12AM +0200, Patrick Boettcher wrote: > Hi, der Herr Hofrat ;-) > > On Sat, 8 Oct 2016 13:57:14 + > Nicholas Mc Guire wrote: > > - lo6 |= (1 << 2) | 2; > > - else > > - lo6 |= (1 << 2) | 1; > > + lo6 |= (1

Re: [RFC PATCH] perf: honouring the cpuid for number of fixed counters in hypervisors

On Thu, Oct 13, 2016 at 01:28:09AM -0700, Imre Palik wrote: > + if (version > 1) { > + unsigned int ecx = cpuid_ecx(1); > + > + if (ecx >> 31) What is this magic, undocumented gunk doing? Is that supposed to be static_cpu_has(X86_FEATURE_HYPERVISOR) ?

Re: [RFC PATCH] perf: honouring the cpuid for number of fixed counters in hypervisors

On Thu, Oct 13, 2016 at 01:28:09AM -0700, Imre Palik wrote: > + if (version > 1) { > + unsigned int ecx = cpuid_ecx(1); > + > + if (ecx >> 31) What is this magic, undocumented gunk doing? Is that supposed to be static_cpu_has(X86_FEATURE_HYPERVISOR) ?

[PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo

[PATCH v2] clk: samsung: clk-exynos-audss: Fix module autoload

If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo

Re: [PATCH] clk: samsung: clk-exynos-audss: Fix module autoload

Hello Krzysztof, On 10/15/2016 02:27 PM, Krzysztof Kozlowski wrote: > On Fri, Oct 14, 2016 at 03:44:05PM -0300, Javier Martinez Canillas wrote: >> If the driver is built as a module, autoload won't work because the module >> alias information is not filled. So user-space can't match the

Re: [PATCH] clk: samsung: clk-exynos-audss: Fix module autoload

Hello Krzysztof, On 10/15/2016 02:27 PM, Krzysztof Kozlowski wrote: > On Fri, Oct 14, 2016 at 03:44:05PM -0300, Javier Martinez Canillas wrote: >> If the driver is built as a module, autoload won't work because the module >> alias information is not filled. So user-space can't match the

[arch/x86] 9bfaa248c8: WARNING: CPU: 8 PID: 48 at arch/x86/events/intel/uncore.c:1151 uncore_change_context+0xbf/0x13a

FYI, we noticed the following commit: https://github.com/0day-ci/linux Prarit-Bhargava/arch-x86-Remove-second-call-to-topology_update_package_map/20161012-231511 commit 9bfaa248c817a9f6734d5daee3b33c25d8a73f0d ("arch/x86: Remove second call to topology_update_package_map()") in testcase:

[arch/x86] 9bfaa248c8: WARNING: CPU: 8 PID: 48 at arch/x86/events/intel/uncore.c:1151 uncore_change_context+0xbf/0x13a

FYI, we noticed the following commit: https://github.com/0day-ci/linux Prarit-Bhargava/arch-x86-Remove-second-call-to-topology_update_package_map/20161012-231511 commit 9bfaa248c817a9f6734d5daee3b33c25d8a73f0d ("arch/x86: Remove second call to topology_update_package_map()") in testcase:

Re: [PATCH] x86/smp: Add irq_enter/exit() in smp_reschedule_interrupt()

On Fri, Oct 14, 2016 at 09:48:53AM +0800, Wanpeng Li wrote: > === > [ INFO: suspicious RCU usage. ] > 4.8.0+ #24 Not tainted > --- > ./arch/x86/include/asm/msr-trace.h:47 suspicious rcu_dereference_check() > usage! > > other info

Re: [PATCH] x86/smp: Add irq_enter/exit() in smp_reschedule_interrupt()

On Fri, Oct 14, 2016 at 09:48:53AM +0800, Wanpeng Li wrote: > === > [ INFO: suspicious RCU usage. ] > 4.8.0+ #24 Not tainted > --- > ./arch/x86/include/asm/msr-trace.h:47 suspicious rcu_dereference_check() > usage! > > other info

Re: [PATCH v2] iio: light: ltr501: claim direct mode during raw writes

On 16/10/16 06:02, Alison Schofield wrote: > Driver was checking for direct mode but not locking it. Use > claim/release helper functions to guarantee the device stays > in direct mode during all raw write operations. > > Signed-off-by: Alison Schofield > --- > Changes in

Re: [PATCH v2] iio: light: ltr501: claim direct mode during raw writes

On 16/10/16 06:02, Alison Schofield wrote: > Driver was checking for direct mode but not locking it. Use > claim/release helper functions to guarantee the device stays > in direct mode during all raw write operations. > > Signed-off-by: Alison Schofield > --- > Changes in v2: > Replaced 'goto

Re: [Outreachy kernel] [PATCH] Staging: dgnc: Clean up Macros

On Sun, 16 Oct 2016, Siddhi Dave wrote: > Fix checkpatch warning: Macros with flow control statements should be avoided > > Because Macros with flow control statements (goto and return) are > not very nice to read as any flow movement is unexpected. > > Signed-off-by: Siddhi Dave

Re: [Outreachy kernel] [PATCH] Staging: dgnc: Clean up Macros

On Sun, 16 Oct 2016, Siddhi Dave wrote: > Fix checkpatch warning: Macros with flow control statements should be avoided > > Because Macros with flow control statements (goto and return) are > not very nice to read as any flow movement is unexpected. > > Signed-off-by: Siddhi Dave > --- >

Re: [PATCH v2] iio: light: ltr501: claim direct mode during select raw reads

On 16/10/16 06:00, Alison Schofield wrote: > Driver was checking for direct mode but not locking it. Use > claim/release helper functions to guarantee the device stays > in direct mode during required raw read cases. > > Signed-off-by: Alison Schofield Very nice. Applied

Re: [PATCH v2] iio: light: ltr501: claim direct mode during select raw reads

On 16/10/16 06:00, Alison Schofield wrote: > Driver was checking for direct mode but not locking it. Use > claim/release helper functions to guarantee the device stays > in direct mode during required raw read cases. > > Signed-off-by: Alison Schofield Very nice. Applied to the togreg branch

[PATCH] Staging: dgnc: Clean up Macros

Fix checkpatch warning: Macros with flow control statements should be avoided Because Macros with flow control statements (goto and return) are not very nice to read as any flow movement is unexpected. Signed-off-by: Siddhi Dave --- drivers/staging/dgnc/dgnc_sysfs.c | 20

[PATCH] Staging: dgnc: Clean up Macros

Fix checkpatch warning: Macros with flow control statements should be avoided Because Macros with flow control statements (goto and return) are not very nice to read as any flow movement is unexpected. Signed-off-by: Siddhi Dave --- drivers/staging/dgnc/dgnc_sysfs.c | 20 ++--

Re: v4.9-rc1: Build and qemu test results (3 build failures, 9 qemu test failures)

On Sat, 15 Oct 2016, Guenter Roeck wrote: Here are some build and qemu test results for v4.9-rc1. Details are available at http://kerneltests.org/builders/. Build results: total: 149 pass: 146 fail: 3 Failed builds: arm:allmodconfig arm64:allmodconfig

Re: v4.9-rc1: Build and qemu test results (3 build failures, 9 qemu test failures)

On Sat, 15 Oct 2016, Guenter Roeck wrote: Here are some build and qemu test results for v4.9-rc1. Details are available at http://kerneltests.org/builders/. Build results: total: 149 pass: 146 fail: 3 Failed builds: arm:allmodconfig arm64:allmodconfig

[PATCH] dmaengine: ioatdma: loop for number elements in array chanerr_str

From: Colin Ian King Just iterate over the number of elements in array chanerr_str rather than for all 32 bits. This removes the need for a NULL chanerr_str[i] check which could possibly overrun if the upper bits (28..31) of chanerr are set and 27th bit in chanerr is

[PATCH] dmaengine: ioatdma: loop for number elements in array chanerr_str

From: Colin Ian King Just iterate over the number of elements in array chanerr_str rather than for all 32 bits. This removes the need for a NULL chanerr_str[i] check which could possibly overrun if the upper bits (28..31) of chanerr are set and 27th bit in chanerr is zero. This simplifies the

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

Re: [PATCH v4 3/8] media: adv7180: add support for NEWAVMODE

Hi Steve, Thank you for the patch. On Wednesday 03 Aug 2016 11:03:45 Steve Longerbeam wrote: > Parse the optional v4l2 endpoint DT node. If the bus type is > V4L2_MBUS_BT656 and the endpoint node specifies "newavmode", > configure the BT.656 bus in NEWAVMODE. > > Signed-off-by: Steve Longerbeam

Re: [PATCH v4 3/8] media: adv7180: add support for NEWAVMODE

Hi Steve, Thank you for the patch. On Wednesday 03 Aug 2016 11:03:45 Steve Longerbeam wrote: > Parse the optional v4l2 endpoint DT node. If the bus type is > V4L2_MBUS_BT656 and the endpoint node specifies "newavmode", > configure the BT.656 bus in NEWAVMODE. > > Signed-off-by: Steve Longerbeam

linux-next: stats (Was: Linux 4.9-rc1)

Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20161004 was the first linux-next after the merge window opened.) Commits in v4.9-rc1 (relative to v4.8):14308 Commits in next-20161004:

linux-next: stats (Was: Linux 4.9-rc1)

Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20161004 was the first linux-next after the merge window opened.) Commits in v4.9-rc1 (relative to v4.8):14308 Commits in next-20161004:

[tip:x86/fpu] x86/fpu: Split old_fpu & new_fpu handling into separate functions

Commit-ID: c474e50711aa79b7bd0ea30b44744baca5650375 Gitweb: http://git.kernel.org/tip/c474e50711aa79b7bd0ea30b44744baca5650375 Author: Rik van Riel AuthorDate: Fri, 14 Oct 2016 08:15:31 -0400 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/fpu] x86/fpu: Split old_fpu & new_fpu handling into separate functions

Commit-ID: c474e50711aa79b7bd0ea30b44744baca5650375 Gitweb: http://git.kernel.org/tip/c474e50711aa79b7bd0ea30b44744baca5650375 Author: Rik van Riel AuthorDate: Fri, 14 Oct 2016 08:15:31 -0400 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:38:41 +0200 x86/fpu: Split old_fpu &

[PATCH] Staging: dgnc: Clean up Macros

Fix checkpatch warning: Macros with flow control statements should be avoided Because Macros with flow control statements (goto and return) are not very nice to read as any flow movement is unexpected. Signed-off-by: Siddhi Dave --- drivers/staging/dgnc/dgnc_sysfs.c | 20

[PATCH] Staging: dgnc: Clean up Macros

Fix checkpatch warning: Macros with flow control statements should be avoided Because Macros with flow control statements (goto and return) are not very nice to read as any flow movement is unexpected. Signed-off-by: Siddhi Dave --- drivers/staging/dgnc/dgnc_sysfs.c | 20 ++--

[tip:x86/fpu] x86/fpu: Remove 'cpu' argument from __cpu_invalidate_fpregs_state()

Commit-ID: 317b622cb2fda1812d8646e211cdb23dce2564d0 Gitweb: http://git.kernel.org/tip/317b622cb2fda1812d8646e211cdb23dce2564d0 Author: Rik van Riel AuthorDate: Fri, 14 Oct 2016 08:15:30 -0400 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/fpu] x86/fpu: Remove 'cpu' argument from __cpu_invalidate_fpregs_state()

Commit-ID: 317b622cb2fda1812d8646e211cdb23dce2564d0 Gitweb: http://git.kernel.org/tip/317b622cb2fda1812d8646e211cdb23dce2564d0 Author: Rik van Riel AuthorDate: Fri, 14 Oct 2016 08:15:30 -0400 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:38:31 +0200 x86/fpu: Remove 'cpu'

Re: [PATCH] arm64: uniphier: select ARCH_HAS_RESET_CONTROLLER

2016-10-08 11:25 GMT+09:00 Masahiro Yamada : > The UniPhier reset driver (drivers/reset/reset-uniphier.c) has been > merged. Select ARCH_HAS_RESET_CONTROLLER from the SoC Kconfig. > > Signed-off-by: Masahiro Yamada > --- > > This is a

Re: [PATCH] arm64: uniphier: select ARCH_HAS_RESET_CONTROLLER

2016-10-08 11:25 GMT+09:00 Masahiro Yamada : > The UniPhier reset driver (drivers/reset/reset-uniphier.c) has been > merged. Select ARCH_HAS_RESET_CONTROLLER from the SoC Kconfig. > > Signed-off-by: Masahiro Yamada > --- > > This is a counter-part of the following ARM-32bit variant: >

[tip:x86/urgent] perf/x86/intel/uncore: Add Knights Mill CPUID

Commit-ID: 5cbf5c59d1b9395e519b197196ef8ac270837cfc Gitweb: http://git.kernel.org/tip/5cbf5c59d1b9395e519b197196ef8ac270837cfc Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:27:58 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] perf/x86/intel/uncore: Add Knights Mill CPUID

Commit-ID: 5cbf5c59d1b9395e519b197196ef8ac270837cfc Gitweb: http://git.kernel.org/tip/5cbf5c59d1b9395e519b197196ef8ac270837cfc Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:27:58 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:32:11 +0200 perf/x86/intel/uncore: Add

[tip:x86/urgent] perf/x86/intel: Add Knights Mill CPUID

Commit-ID: d673b8340cac02d02de30197d6fe66c22a1df6e4 Gitweb: http://git.kernel.org/tip/d673b8340cac02d02de30197d6fe66c22a1df6e4 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:26:34 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] perf/x86/intel: Add Knights Mill CPUID

Commit-ID: d673b8340cac02d02de30197d6fe66c22a1df6e4 Gitweb: http://git.kernel.org/tip/d673b8340cac02d02de30197d6fe66c22a1df6e4 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:26:34 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:32:11 +0200 perf/x86/intel: Add Knights

[tip:x86/urgent] perf/x86/intel/rapl: Add Knights Mill CPUID

Commit-ID: 8d6feacbdb233b81ea8fb2047032e3073f7fc15e Gitweb: http://git.kernel.org/tip/8d6feacbdb233b81ea8fb2047032e3073f7fc15e Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:27:25 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] perf/x86/intel/rapl: Add Knights Mill CPUID

Commit-ID: 8d6feacbdb233b81ea8fb2047032e3073f7fc15e Gitweb: http://git.kernel.org/tip/8d6feacbdb233b81ea8fb2047032e3073f7fc15e Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:27:25 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:32:11 +0200 perf/x86/intel/rapl: Add

[tip:x86/urgent] x86/cpu/intel: Add Knights Mill to Intel family

Commit-ID: 0adc909065d5e5b36a241a5ed1846fb277b89e70 Gitweb: http://git.kernel.org/tip/0adc909065d5e5b36a241a5ed1846fb277b89e70 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:05:20 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] x86/cpu/intel: Add Knights Mill to Intel family

Commit-ID: 0adc909065d5e5b36a241a5ed1846fb277b89e70 Gitweb: http://git.kernel.org/tip/0adc909065d5e5b36a241a5ed1846fb277b89e70 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 20:05:20 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:32:11 +0200 x86/cpu/intel: Add Knights

[tip:x86/urgent] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features

Commit-ID: a518dcc82b6162009c8ca3d169fe61c81536ff17 Gitweb: http://git.kernel.org/tip/a518dcc82b6162009c8ca3d169fe61c81536ff17 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 19:57:31 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features

Commit-ID: a518dcc82b6162009c8ca3d169fe61c81536ff17 Gitweb: http://git.kernel.org/tip/a518dcc82b6162009c8ca3d169fe61c81536ff17 Author: Piotr Luc AuthorDate: Wed, 12 Oct 2016 19:57:31 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:32:11 +0200 x86/cpufeature: Add

[tip:x86/urgent] x86/e820: Don't merge consecutive E820_PRAM ranges

Commit-ID: 23446cb66c073b827779e5eb3dec301623299b32 Gitweb: http://git.kernel.org/tip/23446cb66c073b827779e5eb3dec301623299b32 Author: Dan Williams AuthorDate: Wed, 12 Oct 2016 11:01:48 -0700 Committer: Ingo Molnar CommitDate: Sun, 16 Oct

[tip:locking/urgent] locking/rwsem: Add stack frame dependency for ____down_write()

Commit-ID: 9a0f9948b35140ebb8aa9b753e3ed09975700483 Gitweb: http://git.kernel.org/tip/9a0f9948b35140ebb8aa9b753e3ed09975700483 Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:26:15 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:x86/urgent] x86/e820: Don't merge consecutive E820_PRAM ranges

Commit-ID: 23446cb66c073b827779e5eb3dec301623299b32 Gitweb: http://git.kernel.org/tip/23446cb66c073b827779e5eb3dec301623299b32 Author: Dan Williams AuthorDate: Wed, 12 Oct 2016 11:01:48 -0700 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:16:48 +0200 x86/e820: Don't merge

[tip:locking/urgent] locking/rwsem: Add stack frame dependency for ____down_write()

Commit-ID: 9a0f9948b35140ebb8aa9b753e3ed09975700483 Gitweb: http://git.kernel.org/tip/9a0f9948b35140ebb8aa9b753e3ed09975700483 Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:26:15 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:17:58 +0200 locking/rwsem: Add stack

[tip:core/urgent] objtool: Skip all "unreachable instruction" warnings for gcov kernels

Commit-ID: 9cfffb116887b1b7c51cd4e3fa5790dc52a0758f Gitweb: http://git.kernel.org/tip/9cfffb116887b1b7c51cd4e3fa5790dc52a0758f Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:22:53 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:core/urgent] objtool: Skip all "unreachable instruction" warnings for gcov kernels

Commit-ID: 9cfffb116887b1b7c51cd4e3fa5790dc52a0758f Gitweb: http://git.kernel.org/tip/9cfffb116887b1b7c51cd4e3fa5790dc52a0758f Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:22:53 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 09:12:36 +0200 objtool: Skip all

[tip:core/urgent] objtool: Improve rare switch jump table pattern detection

Commit-ID: 3732710ff6f2ce2b1b7f044937a422b717d4f953 Gitweb: http://git.kernel.org/tip/3732710ff6f2ce2b1b7f044937a422b717d4f953 Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:22:52 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:core/urgent] objtool: Improve rare switch jump table pattern detection

Commit-ID: 3732710ff6f2ce2b1b7f044937a422b717d4f953 Gitweb: http://git.kernel.org/tip/3732710ff6f2ce2b1b7f044937a422b717d4f953 Author: Josh Poimboeuf AuthorDate: Thu, 13 Oct 2016 16:22:52 -0500 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 09:12:35 +0200 objtool: Improve rare

[tip:perf/urgent] kprobes: Unpoison stack in jprobe_return() for KASAN

Commit-ID: 9f7d416c36124667c406978bcb39746589c35d7f Gitweb: http://git.kernel.org/tip/9f7d416c36124667c406978bcb39746589c35d7f Author: Dmitry Vyukov AuthorDate: Fri, 14 Oct 2016 16:07:23 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016

[tip:perf/urgent] kprobes: Unpoison stack in jprobe_return() for KASAN

Commit-ID: 9f7d416c36124667c406978bcb39746589c35d7f Gitweb: http://git.kernel.org/tip/9f7d416c36124667c406978bcb39746589c35d7f Author: Dmitry Vyukov AuthorDate: Fri, 14 Oct 2016 16:07:23 +0200 Committer: Ingo Molnar CommitDate: Sun, 16 Oct 2016 11:02:31 +0200 kprobes: Unpoison stack

<    1   2   3   4   5   >