Re: [PATCH v5] kprobes: unpoison stack in jprobe_return() for KASAN

* Dmitry Vyukov wrote: > On Sat, Oct 15, 2016 at 8:30 AM, Ingo Molnar wrote: > > > > * Dmitry Vyukov wrote: > > > >> KASAN stack instrumentation poisons stack redzones on function entry > >> and unpoisons them on function exit. If a function exits abnormally > >> (e.g. with a longjmp like jpro

Re: [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches

* Michael Ellerman wrote: > Currently after bringing up secondary CPUs all arches print "Brought up > %d CPUs". On x86 they also print the number of nodes that were brought > online. > > It would be nice to also print the number of nodes on other arches. > Although we could override smp_announc

Re: Intermittent perf build failures

* 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 -0700, Laura Abbott wrote: > Hi, > > While building today's Fedora r

Re: [RFC] scripts: Include postprocessing script for memory allocation tracing

On Sat 15-10-16 19:31:22, Janani Ravichandran wrote: > > > On Oct 11, 2016, at 10:43 AM, Janani Ravichandran > > wrote: > > > > Alright. I’ll add a starting tracepoint, change the script accordingly and > > send a v2. Thanks! > > > I looked at it again and I think that the context information

[PATCH] fs: always set I_DIRTY_TIME to fsync correctly on lazytime

While lazytime states that "The on-disk timestamps are updated only when: ... - the application employs fsync(2), syncfs(2), or sync(2)" [1], it does not write a timestamp update on fsync(). [1] http://manpages.ubuntu.com/manpages/xenial/man8/mount.8.html The following commands will reproduce the

[PATCH] MD-RAID: Use seq_putc() in three status functions

From: Markus Elfring Date: Sun, 16 Oct 2016 10:10:28 +0200 A single character (a closing square bracket) should be put into a sequence at the end in these functions. Thus use the corresponding function "seq_putc". This issue was detected also by using the Coccinelle software. Signed-off-by: Mar

Re: [PATCH 0/5] Replace data type declarations with variables of same types in several source files.

On Mon, Oct 10, 2016 at 04:02:17PM +0200, Sergio Paracuellos wrote: > This patch series replaces several sizeof(struct XXX) stuff in favour > of sizeof(var) which is the preferred one. > Why not squash this series into one patch? The commit messages are fairly similar and the changes are focused

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

Hi Ralf, (Cc i2c) On Fri, Oct 14, 2016 at 9:31 PM, Ralf Ramsauer wrote: > Instantiated SPI device nodes are marked with OF_POPULATE. This was > introduced in bd6c164. On unloading, loaded device nodes will of course > be unmarked. The problem are nodes the fail during initialisation: If a > node

Re: [PATCH] char/pcmcia: add scr24x_cs chip card interface driver

Hi Greg, (responses inline) On Mon, 2016-10-10 at 19:33 +0200, Greg Kroah-Hartman wrote: > On Mon, Oct 10, 2016 at 05:58:15PM +0200, Lubomir Rintel wrote: > > > > This implements only the very basic protocol "Mode A", just to make > > the > > device functional. Patches to implement "Mode C" that

ERROR: "bad_dma_ops" [sound/soc/bcm/snd-soc-cygnus.ko] undefined!

Hi Simran, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 1200a7d9b2c65ffb2dd673add65cd5dc95671489 ASoC: cygnus: Add Cygnus audio DMA driver date: 5 months ago con

fs/xfs/xfs_ondisk.h:96:2: error: call to '__compiletime_assert_96' declared with attribute error: XFS: sizeof(xfs_dir2_sf_entry_t) is wrong, expected 3

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 7 months a

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

On Sun, Oct 16, 2016 at 10:49:11AM +0200, Geert Uytterhoeven wrote: > Hi Ralf, > > (Cc i2c) Thanks for letting me know! Adding Pantelis to CC, as he is the original author of OF_DYNAMIC. Please keep me in the loop. > > On Fri, Oct 14, 2016 at 9:31 PM, Ralf Ramsauer > wrote: > > Instantiated SP

BYD TouchPad driver (4.8.1) misdetects a Logitech mouse

Not a big deal, but something nonetheless ... I recently upgraded my kernel from 4.3 to 4.8.1 (this is a Linux From Scratch build). There was only one obvious hiccup - X would not start because it no longer saw the mouse. I have a Logitech RX250 PS2/USB mouse on the PS/2 port (via a USB->PS2 ada

[PATCH] [media] usbtv: add video controls

Brightness, Contrast, Hue and Color Saturation are supported. Signed-off-by: Lubomir Rintel --- drivers/media/usb/usbtv/usbtv-video.c | 97 ++- drivers/media/usb/usbtv/usbtv.h | 3 ++ 2 files changed, 99 insertions(+), 1 deletion(-) diff --git a/drivers/me

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

Hi Geert, On 10/16/2016 10:49 AM, Geert Uytterhoeven wrote: > Hi Ralf, > > (Cc i2c) > > On Fri, Oct 14, 2016 at 9:31 PM, Ralf Ramsauer > wrote: >> Instantiated SPI device nodes are marked with OF_POPULATE. This was >> introduced in bd6c164. On unloading, loaded device nodes will of course >> be

Re: [PATCH] char/pcmcia: add scr24x_cs chip card interface driver

On Sun, Oct 16, 2016 at 11:23:36AM +0200, Lubomir Rintel wrote: > Hi Greg, > > (responses inline) > > On Mon, 2016-10-10 at 19:33 +0200, Greg Kroah-Hartman wrote: > > On Mon, Oct 10, 2016 at 05:58:15PM +0200, Lubomir Rintel wrote: > > > > > > This implements only the very basic protocol "Mode A"

[PATCH] staging: greybus: audio: Rename cport with intf_id

gb_audio_manager_module_descriptor's cport field is actually used to manage and pass interface id to user space. Thus rename gb_audio_manager_module_descriptor's 'cport' field and few other things to avoid confusion. Signed-off-by: Pankaj Bharadiya --- drivers/staging/greybus/audio_manager.h

Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment workaround

Robert Jarzmik writes: > diff --git a/drivers/net/ethernet/smsc/smc91x.h > b/drivers/net/ethernet/smsc/smc91x.h > index ea8465467469..dff165ed106d 100644 > --- a/drivers/net/ethernet/smsc/smc91x.h > +++ b/drivers/net/ethernet/smsc/smc91x.h And there is also the specific case of ARCH=MN10300, wh

ERROR: "bad_dma_ops" [drivers/tty/serial/stm32-usart.ko] undefined!

Hi Alexandre, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 3489187204eb75e5635d8836babfd0a18be613f4 serial: stm32: adding dma support date: 3 weeks ago config:

[PATCH] ARM-mm-dump: Use seq_putc() in note_page()

From: Markus Elfring Date: Sun, 16 Oct 2016 12:00:26 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/arm/mm/dump.c | 2 +- 1 fi

[PATCH] ARM/orion/gpio: Replace three seq_printf() calls by seq_puts() in orion_gpio_dbg_show()

From: Markus Elfring Date: Sun, 16 Oct 2016 12:30:48 +0200 Strings which did not contain data format specifications should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/a

Re: [PATCH] ARM: at91/dt: pullup dbgu rx instead of tx

Hi again, I forgot about this, and it's been a year. But isn't it time to upstream those pull-up fixes that Sylvain provided? Cheers, Peter On 2015-09-24 16:47, Alexandre Belloni wrote: > Hi Peter, > > Thanks for the patch but you actually got beaten by Sylvain: > http://lists.infradead.org/pi

[PATCH] kconfig.h: remove config_enabled() macro

The use of config_enabled() is ambiguous. For config options, IS_ENABLED(), IS_REACHABLE(), etc. will make intention clearer. Sometimes config_enabled() has been used for non-config options because it is useful to check whether the given symbol is defined or not. I have been tackling on deprecati

[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 in

[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 swi

[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 "unreac

[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 conse

[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: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 AVX512_4VN

[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 Mil

[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 Knigh

[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 Mi

[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 Kni

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: > https://pat

[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' argum

[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 ++-- 1

[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 & ne

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:

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

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

[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 co

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 powerp

[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 ++-- 1

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 fo

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 > --- > drive

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: [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 that

[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: will-i

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 registered

[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 drive

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 - 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 <<

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 d

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 Mo

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]

[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 i

[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 exis

[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 nand_d

[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 t

[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 enabled,

[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 fun

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 don'

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 -0700,

[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, pl

[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 PSCI

[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 Y

[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] 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 b/drivers/clk/uniphie

[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 +++ b/kern

[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 b_fw->nam

[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 05/12] kprobes: declare __{start,stop}_kprobe_blacklist as external array

Cc: Ananth N Mavinakayanahalli Cc: Anil S Keshavamurthy Cc: "David S. Miller" Cc: Masami Hiramatsu Signed-off-by: Vegard Nossum --- kernel/kprobes.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/kernel/kprobes.c b/kernel/kprobes.c index d630954..f163f74 100644 --

[PATCH 06/12] tracing: declare __{start,stop}_ftrace_events as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/trace_events.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c index 03c0a48..400162f 100644 --- a/kernel/trace/trace_events.c +++ b/kernel/trace/

[PATCH 11/12] jump_label: declare jump table as external array

Cc: Jason Baron Cc: Peter Zijlstra Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- include/linux/jump_label.h | 4 ++-- kernel/jump_label.c| 10 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h index

[PATCH 12/12] dynamic debug: declare table as external array

Cc: Greg Banks Cc: Jason Baron Signed-off-by: Vegard Nossum --- lib/dynamic_debug.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c index da796e2..101a420 100644 --- a/lib/dynamic_debug.c +++ b/lib/dynamic_debug.c @@ -13

[PATCH 00/12] external array access helpers

Hi, The first two patches in the series fix the concrete bug (a boot crash when using gcc 7.0+) by defining new wrappers for arrays defined in linker scripts. These two patches should probably go into the kernel + stable as soon as people are happy with the new interface. Not sure who would pick t

[PATCH 07/12] tracing: declare __{start,stop}_ftrace_enum_maps as external array

Cc: Steven Rostedt Signed-off-by: Vegard Nossum --- kernel/trace/trace.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index 8696ce6..d1bee81 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -11,6 +11,7 @

[PATCH 01/12] extarray: define helpers for arrays defined in linker scripts

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 b_f

[PATCH] Staging: media: omap4iss: fixed coding style issues

Fixed coding style issues Signed-off-by: Hector Roussille --- drivers/staging/media/omap4iss/iss_video.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/staging/media/omap4iss/iss_video.c b/drivers/staging/media/omap4iss/iss_video.c index c16927a..8f2d374

[PATCH] clk: uniphier: fix type of variable passed to regmap_read()

The 3rd argument of regmap_read() takes a pointer to unsigned int. This driver is saved just because u32 happens to be typedef'ed as unsigned int, but we should not rely on that fact. Change the variable type just in case. Signed-off-by: Masahiro Yamada --- drivers/clk/uniphier/clk-uniphier-mu

Re: [PATCH] ARM/orion/gpio: Replace three seq_printf() calls by seq_puts() in orion_gpio_dbg_show()

On Sun, Oct 16, 2016 at 12:38:26PM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 16 Oct 2016 12:30:48 +0200 > > Strings which did not contain data format specifications should be put > into a sequence. Thus use the corresponding function "seq_puts". > > This issue was detec

Re: [PATCH] Staging: media: omap4iss: fixed coding style issues

Hi Hector, Thank you for the patch. On Sunday 16 Oct 2016 17:18:56 Hector Roussille wrote: > Fixed coding style issues What coding style issues ? > > Signed-off-by: Hector Roussille > --- > drivers/staging/media/omap4iss/iss_video.c | 11 +++ > 1 file changed, 7 insertions(+), 4 dele

Re: [PATCH 57/80] staging: lustre: osc: revise unstable pages accounting

Digging up an old email... On Tue, Aug 16, 2016 at 04:19:10PM -0400, James Simmons wrote: > From: Jinshan Xiong > > A few changes are made in this patch for unstable pages tracking: > > 1. Remove kernel NFS unstable pages tracking because it killed >performance > 2. Track unstable pages as

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

On Sun, Oct 16, 2016 at 06:12:32PM +0530, 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

Re: [PATCH][V2] ubi: fix swapped arguments to call to ubi_alloc_aeb

On Sat, 15 Oct 2016 17:00:11 +0100 Colin King wrote: > From: Colin Ian King > > Static analysis by CoverityScan detected the ec and pnum > arguments are in the wrong order on a call to ubi_alloc_aeb. > Swap the order to fix this. > > Fixes: 91f4285fe389a27 ("UBI: provide helpers to allocate an

[PATCH 1/2] arm64: dts: uniphier: increase register region size of sysctrl node

The System Control node has 0x1 byte of registers. The current reg size must be expanded to use the cpufreq driver because the registers controlling CPU frequency are located at offset 0x8000. Signed-off-by: Masahiro Yamada --- arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 2 +- arch/

[PATCH 2/2] ARM: dts: uniphier: increase register region size of sysctrl node

The System Control node has 0x1 byte of registers. The current reg size must be expanded to use the cpufreq driver because the registers controlling CPU frequency are located at offset 0x8000. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-common32.dtsi | 2 +- 1 file change

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

On 10/16/2016 05:30 AM, Stafford Horne wrote: 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

Re: [PATCH] Staging: media: omap4iss: fixed coding style issues

On Sun, Oct 16, 2016 at 05:18:56PM +0200, Hector Roussille wrote: > Fixed coding style issues You need to be a lot more specific please. thanks, greg k-h

Re: [PATCH] watchdog: at91sam9: keep watchdog running in idle mode

On 10/16/2016 08:33 AM, Sylvain Rochet wrote: Hi, On Wed, Oct 07, 2015 at 01:01:12PM +0200, Alexandre Belloni wrote: On 06/10/2015 at 22:28:45 +0200, Sylvain Rochet wrote : Since turning on idle-halt in commit 5161b31dc39a (watchdog: at91sam9_wdt: better watchdog support"), SoCs compatible wit

Re: [PATCH] watchdog: at91sam9: keep watchdog running in idle mode

On 10/16/2016 08:50 AM, Guenter Roeck wrote: On 10/16/2016 08:33 AM, Sylvain Rochet wrote: Hi, On Wed, Oct 07, 2015 at 01:01:12PM +0200, Alexandre Belloni wrote: On 06/10/2015 at 22:28:45 +0200, Sylvain Rochet wrote : Since turning on idle-halt in commit 5161b31dc39a (watchdog: at91sam9_wdt:

[PATCH 01/10] fault injection: fix a few documentation errors

Signed-off-by: Vegard Nossum --- Documentation/fault-injection/fault-injection.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/fault-injection/fault-injection.txt b/Documentation/fault-injection/fault-injection.txt index 415484f..2ef8531 100644 --- a

[PATCH 02/10] fault injection: fix Kconfig menu

We need an explicit dependency on FAULT_INJECTION in order to keep FAIL_MMC_REQUEST (and subsequent entries) inside the FAULT_INJECTION menu. Fixes: 28ff4fda9e5b ("mmc: kconfig: replace FAULT_INJECTION with FAULT_INJECTION_DEBUG_FS") Cc: Adrien Schildknecht Cc: Ulf Hansson Signed-off-by: Vegard

[PATCH 10/10] fault injection: inject faults in new/rare callchains

Before this patch, fault injection uses a combination of randomness and frequency to determine where to inject faults. The problem with this is that code paths which are executed very rarely get proportional amounts of faults injected. A better heuristic is to look at the actual callchain leading

[PATCH 04/10] fault injection: prevent recursive fault injection

If something we call in the fail_dump() code path tries to acquire a resource that might fail (due to fault injection), then we should not try to recurse back into the fault injection code. I've seen this happen with the console semaphore in the upcoming semaphore trylock fault injection code. Cc

[PATCH 08/10] fault injection: down_{read,write}_trylock() fault injection

Cc: Peter Zijlstra Cc: Ingo Molnar Signed-off-by: Vegard Nossum --- kernel/locking/rwsem.c | 35 +-- lib/Kconfig.debug | 6 ++ 2 files changed, 39 insertions(+), 2 deletions(-) diff --git a/kernel/locking/rwsem.c b/kernel/locking/rwsem.c index 45ba475.

[PATCH 06/10] fault injection: rt_mutex_trylock() fault injection

Cc: Peter Zijlstra Cc: Ingo Molnar Signed-off-by: Vegard Nossum --- kernel/locking/rtmutex.c | 26 ++ lib/Kconfig.debug| 6 ++ 2 files changed, 32 insertions(+) diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c index 1ec0f48..22ff6da 100644 -

[PATCH 10/12] serial_core: declare __earlycon_table{,_end} as external array

Cc: Peter Hurley Cc: Greg Kroah-Hartman Signed-off-by: Vegard Nossum --- drivers/of/fdt.c | 2 +- drivers/tty/serial/earlycon.c | 2 +- include/asm-generic/vmlinux.lds.h | 8 include/linux/serial_core.h | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(

  1   2   3   >