Re: [PATCH] checkpatch: Whine about ACCESS_ONCE

On Sat, 16 Apr 2016, Joe Perches wrote: > On Sat, 2016-04-16 at 12:04 -0700, Joe Perches wrote: > > Add a test for use of ACCESS_ONCE that could be written using > > READ_ONCE or WRITE_ONCE. > > > > --fix it too if desired. > > And here's a simple coccinelle script that does a > rather better

Re: [PATCH] checkpatch: Whine about ACCESS_ONCE

On Sat, 16 Apr 2016, Joe Perches wrote: > On Sat, 2016-04-16 at 12:04 -0700, Joe Perches wrote: > > Add a test for use of ACCESS_ONCE that could be written using > > READ_ONCE or WRITE_ONCE. > > > > --fix it too if desired. > > And here's a simple coccinelle script that does a > rather better

[PATCH 1/6] drm/fsl-dcu: detach panel on destroy

Disable the earlier attached panel on connector destroy. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c index

[PATCH 1/6] drm/fsl-dcu: detach panel on destroy

Disable the earlier attached panel on connector destroy. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_rgb.c index f586f1e..a07886f

[PATCH 2/6] drm/fsl-dcu: handle missing panel gracefully

If the device tree property fsl,panel is missing, drm_panel_attach is called with a NULL pointer as first argument. Having a panel is basically mandatory since RGB is the only supported connector. Check if a panel node has been found, return -ENODEV and cleanup otherwise. Signed-off-by: Stefan

[PATCH 2/6] drm/fsl-dcu: handle missing panel gracefully

If the device tree property fsl,panel is missing, drm_panel_attach is called with a NULL pointer as first argument. Having a panel is basically mandatory since RGB is the only supported connector. Check if a panel node has been found, return -ENODEV and cleanup otherwise. Signed-off-by: Stefan

[PATCH 3/6] drm/fsl-dcu: use variable name dev for struct drm_device

The driver uses different variable names for struct drm_device across functions which is confusing. Stick to the more common variable name dev. While at it, remove unnecessary if statement in error handling. Signed-off-by: Stefan Agner ---

[PATCH 5/6] drm/fsl-dcu: disable output polling on driver unload

Disabling output polling before unloading the driver. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c index

[PATCH 6/6] drm/fsl-dcu: implement lastclose callback

Use CMA helper drm_fbdev_cma_restore_mode to restore fbdev mode in process which uses drm/kms dies. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c

[PATCH 3/6] drm/fsl-dcu: use variable name dev for struct drm_device

The driver uses different variable names for struct drm_device across functions which is confusing. Stick to the more common variable name dev. While at it, remove unnecessary if statement in error handling. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 29

[PATCH 5/6] drm/fsl-dcu: disable output polling on driver unload

Disabling output polling before unloading the driver. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c index 182578d..f9227b7

[PATCH 6/6] drm/fsl-dcu: implement lastclose callback

Use CMA helper drm_fbdev_cma_restore_mode to restore fbdev mode in process which uses drm/kms dies. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c

[PATCH 4/6] drm/fsl-dcu: deallocate fbdev CMA on unload

Free fbdev CMA using drm_fbdev_cma_fini on unload. This fixes a warning when unloading the driver: WARNING: CPU: 0 PID: 164 at drivers/gpu/drm/drm_crtc.c:5930 drm_mode_config_cleanup+0x204/0x208 Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 9

[PATCH 4/6] drm/fsl-dcu: deallocate fbdev CMA on unload

Free fbdev CMA using drm_fbdev_cma_fini on unload. This fixes a warning when unloading the driver: WARNING: CPU: 0 PID: 164 at drivers/gpu/drm/drm_crtc.c:5930 drm_mode_config_cleanup+0x204/0x208 Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 9 + 1 file

[PATCH 0/6] drm/fsl-dcu: unload fixes

Hi all, This patchset fixes several issues around unloading/unbinding the driver. There is still one WARNING when unloading the driver while vblank interrupts are enabled. I am not sure what/who should make sure that vblank interrupts get disabled before unloading the driver: root@colibri-vf:~#

[PATCH 0/6] drm/fsl-dcu: unload fixes

Hi all, This patchset fixes several issues around unloading/unbinding the driver. There is still one WARNING when unloading the driver while vblank interrupts are enabled. I am not sure what/who should make sure that vblank interrupts get disabled before unloading the driver: root@colibri-vf:~#

drivers/mfd/syscon.c:67:9: error: implicit declaration of function 'ioremap'

Hi Philipp, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: ca668f0edfae65438c3f0a3ad5d3e59e3515915f mfd: syscon: Set regmap max_register in of_syscon_register date:

drivers/mfd/syscon.c:67:9: error: implicit declaration of function 'ioremap'

Hi Philipp, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: ca668f0edfae65438c3f0a3ad5d3e59e3515915f mfd: syscon: Set regmap max_register in of_syscon_register date:

/tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: 5eeb50de42fd3251845d03c556db012267c72b3f uprobes: Change handle_trampoline() to flush the frames invalidated by longjmp() date: 9 months ago config:

/tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: 5eeb50de42fd3251845d03c556db012267c72b3f uprobes: Change handle_trampoline() to flush the frames invalidated by longjmp() date: 9 months ago config:

drivers/mfd/syscon.c:89:2: error: implicit declaration of function 'iounmap'

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: 0166dc11be911213e0b1b764488c671be4c48cf3 of: make CONFIG_OF user selectable date: 11 months ago config:

drivers/mfd/syscon.c:89:2: error: implicit declaration of function 'iounmap'

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce commit: 0166dc11be911213e0b1b764488c671be4c48cf3 of: make CONFIG_OF user selectable date: 11 months ago config:

Re: [PATCH V6 00/13] Support for generic ACPI based PCI host controller

On 4/15/2016 1:06 PM, Tomasz Nowicki wrote: >>From the functionality point of view this series might be split into the > following logic parts: > 1. Necessary fixes as the preparation for using driver on ARM64. > 2. New ECAM API and update for users of the pci-host-common API > 3. Use new MCFG

Re: [PATCH V6 00/13] Support for generic ACPI based PCI host controller

On 4/15/2016 1:06 PM, Tomasz Nowicki wrote: >>From the functionality point of view this series might be split into the > following logic parts: > 1. Necessary fixes as the preparation for using driver on ARM64. > 2. New ECAM API and update for users of the pci-host-common API > 3. Use new MCFG

Re: [PATCH] dspi: config dspi master regmap with right mode depend on BE or LE

On 04/13/2016 06:12 AM, Po Liu wrote: > When kernel config with big endian mode, spi master need > to config regmap data value to be little endian mode. Or else, > the kernel boot will hang. > > Signed-off-by: Po Liu > --- > drivers/spi/spi-fsl-dspi.c | 3 +++ > 1 file changed,

Re: [PATCH] dspi: config dspi master regmap with right mode depend on BE or LE

On 04/13/2016 06:12 AM, Po Liu wrote: > When kernel config with big endian mode, spi master need > to config regmap data value to be little endian mode. Or else, > the kernel boot will hang. > > Signed-off-by: Po Liu > --- > drivers/spi/spi-fsl-dspi.c | 3 +++ > 1 file changed, 3 insertions(+)

Re: Isolated expedited RCU code to a new tree_exp.h

On Sat, Apr 16, 2016 at 03:29:09PM +, Mathieu Desnoyers wrote: > - On Apr 16, 2016, at 9:08 AM, Frederic Weisbecker fweis...@gmail.com > wrote: > > > On Fri, Apr 15, 2016 at 04:52:02PM -0700, Paul E. McKenney wrote: > >> Hello, Frederic, > >> > >> One thing that I have had on my list

Re: Isolated expedited RCU code to a new tree_exp.h

On Sat, Apr 16, 2016 at 03:29:09PM +, Mathieu Desnoyers wrote: > - On Apr 16, 2016, at 9:08 AM, Frederic Weisbecker fweis...@gmail.com > wrote: > > > On Fri, Apr 15, 2016 at 04:52:02PM -0700, Paul E. McKenney wrote: > >> Hello, Frederic, > >> > >> One thing that I have had on my list

Re: [PATCH tip/core/rcu 10/10] documentation: Add documentation for RCU's major data structures

On Sat, Apr 16, 2016 at 10:52:39PM +0800, Boqun Feng wrote: > Hi Paul, > > On Tue, Apr 12, 2016 at 08:18:21AM -0700, Paul E. McKenney wrote: > > This commit adds documentation for RCU's major data structures, > > including rcu_state, rcu_node, rcu_data, rcu_dynticks, and rcu_head. > > > > One

Re: [PATCH tip/core/rcu 10/10] documentation: Add documentation for RCU's major data structures

On Sat, Apr 16, 2016 at 10:52:39PM +0800, Boqun Feng wrote: > Hi Paul, > > On Tue, Apr 12, 2016 at 08:18:21AM -0700, Paul E. McKenney wrote: > > This commit adds documentation for RCU's major data structures, > > including rcu_state, rcu_node, rcu_data, rcu_dynticks, and rcu_head. > > > > One

Re: [PATCH 01/31] huge tmpfs: prepare counts in meminfo, vmstat and SysRq-m

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:12:26PM -0700, Hugh Dickins wrote: > > ShmemFreeHoles will show the wastage from using huge pages for small, or > > sparsely occupied, or unrounded files: wastage not included in Shmem or > > MemFree, but will be freed

Re: [PATCH 01/31] huge tmpfs: prepare counts in meminfo, vmstat and SysRq-m

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:12:26PM -0700, Hugh Dickins wrote: > > ShmemFreeHoles will show the wastage from using huge pages for small, or > > sparsely occupied, or unrounded files: wastage not included in Shmem or > > MemFree, but will be freed

Re: [PATCH 03/31] huge tmpfs: huge=N mount option and /proc/sys/vm/shmem_huge

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:15:05PM -0700, Hugh Dickins wrote: > > Plumb in a new "huge=1" or "huge=0" mount option to tmpfs: I don't > > want to get into a maze of boot options, madvises and fadvises at > > this stage, nor extend the use of the

Re: [PATCH 03/31] huge tmpfs: huge=N mount option and /proc/sys/vm/shmem_huge

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:15:05PM -0700, Hugh Dickins wrote: > > Plumb in a new "huge=1" or "huge=0" mount option to tmpfs: I don't > > want to get into a maze of boot options, madvises and fadvises at > > this stage, nor extend the use of the

Re: [RFC PATCH 1/1] powerpc/fsl: Fix build of the dtb embedded kernel images

On Fri, 2016-04-15 at 10:27 +0200, Alessio Igor Bogani wrote: > Hi, > > On 6 April 2016 at 15:45, Alessio Igor Bogani > wrote: > > The commit dc37374 move a lot of device tree files into fsl directory > > fixing Makefile for cuImage target only. Unfortunately there are

Re: [RFC PATCH 1/1] powerpc/fsl: Fix build of the dtb embedded kernel images

On Fri, 2016-04-15 at 10:27 +0200, Alessio Igor Bogani wrote: > Hi, > > On 6 April 2016 at 15:45, Alessio Igor Bogani > wrote: > > The commit dc37374 move a lot of device tree files into fsl directory > > fixing Makefile for cuImage target only. Unfortunately there are others > > target which

Re: [PATCH 09/31] huge tmpfs: avoid premature exposure of new pagetable

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:24:23PM -0700, Hugh Dickins wrote: > > > > That itself is not a problem on x86_64, but there's plenty more: > > how about those places which use pte_offset_map_lock() - if that > > spinlock is in the struct page of a

Re: [PATCH 09/31] huge tmpfs: avoid premature exposure of new pagetable

On Mon, 11 Apr 2016, Kirill A. Shutemov wrote: > On Tue, Apr 05, 2016 at 02:24:23PM -0700, Hugh Dickins wrote: > > > > That itself is not a problem on x86_64, but there's plenty more: > > how about those places which use pte_offset_map_lock() - if that > > spinlock is in the struct page of a

Re: [PATCH 1/2] clk: sunxi: add predivider handling for factors clock

Hi Vishnu, [auto build test ERROR on clk/clk-next] [also build test ERROR on v4.6-rc3 next-20160415] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 1/2] clk: sunxi: add predivider handling for factors clock

Hi Vishnu, [auto build test ERROR on clk/clk-next] [also build test ERROR on v4.6-rc3 next-20160415] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

On Sun, 17 Apr 2016, Kirill A. Shutemov wrote: > On Sat, Apr 16, 2016 at 04:41:33PM -0700, Hugh Dickins wrote: > > The pmd_fault() method gives the filesystem an opportunity to place > > a trans huge pmd entry at *pmd, before any pagetable is exposed (and > > an opportunity to split it on COW

Re: [PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

On Sun, 17 Apr 2016, Kirill A. Shutemov wrote: > On Sat, Apr 16, 2016 at 04:41:33PM -0700, Hugh Dickins wrote: > > The pmd_fault() method gives the filesystem an opportunity to place > > a trans huge pmd entry at *pmd, before any pagetable is exposed (and > > an opportunity to split it on COW

Re: {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits

On Sun, Apr 17, 2016 at 08:20:38AM +0800, kbuild test robot wrote: > FYI, the error/warning still remains. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 306a63bee192859ebd32c7328c7766636d882d8f > commit:

Re: {standard input}:136: Error: number (0x9000000080000000) larger than 32 bits

On Sun, Apr 17, 2016 at 08:20:38AM +0800, kbuild test robot wrote: > FYI, the error/warning still remains. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 306a63bee192859ebd32c7328c7766636d882d8f > commit:

[PATCH v2 1/2] i2c: exynos5: Check clk_prepare_enable() return value

The clk_prepare_enable() function can fail so check the return value and propagate the error to the caller in case of a failure. Signed-off-by: Javier Martinez Canillas --- Changes in v2: None drivers/i2c/busses/i2c-exynos5.c | 12 +--- 1 file changed, 9

[PATCH v2 2/2] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

The exynos5 I2C controller driver always prepares and enables a clock before using it and then disables unprepares it when the clock is not used anymore. But this can cause a possible ABBA deadlock in some scenarios since a driver that uses regmap to access its I2C registers, will first grab the

[PATCH v2 1/2] i2c: exynos5: Check clk_prepare_enable() return value

The clk_prepare_enable() function can fail so check the return value and propagate the error to the caller in case of a failure. Signed-off-by: Javier Martinez Canillas --- Changes in v2: None drivers/i2c/busses/i2c-exynos5.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-)

[PATCH v2 2/2] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

The exynos5 I2C controller driver always prepares and enables a clock before using it and then disables unprepares it when the clock is not used anymore. But this can cause a possible ABBA deadlock in some scenarios since a driver that uses regmap to access its I2C registers, will first grab the

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

[GIT PULL] char/misc driver fixes for 4.6-rc4

The following changes since commit c4004b02f8e5b9ce357a0bb1641756cc86962664: x86: remove the kernel code/data/bss resources from /proc/iomem (2016-04-06 13:45:07 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/

[GIT PULL] char/misc driver fixes for 4.6-rc4

The following changes since commit c4004b02f8e5b9ce357a0bb1641756cc86962664: x86: remove the kernel code/data/bss resources from /proc/iomem (2016-04-06 13:45:07 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/

[GIT PULL] Driver core fixes for 4.6-rc4

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.6-rc4 for you to fetch changes up to

[GIT PULL] Driver core fixes for 4.6-rc4

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca: Linux 4.6-rc1 (2016-03-26 16:03:24 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.6-rc4 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.6-rc4

The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb: Linux 4.6-rc3 (2016-04-10 17:58:30 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.6-rc4 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.6-rc4

The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb: Linux 4.6-rc3 (2016-04-10 17:58:30 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.6-rc4 for you to fetch changes up to

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

Hello Krzysztof, Thanks a lot for your feedback. On 04/16/2016 12:11 PM, Krzysztof Kozlowski wrote: > On Fri, Apr 15, 2016 at 06:04:47PM -0400, Javier Martinez Canillas wrote: [snip] >> >> Fix this by only preparing the clock on probe and {en,dis}able in the >> rest of the driver. >> >> This

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

Hello Krzysztof, Thanks a lot for your feedback. On 04/16/2016 12:11 PM, Krzysztof Kozlowski wrote: > On Fri, Apr 15, 2016 at 06:04:47PM -0400, Javier Martinez Canillas wrote: [snip] >> >> Fix this by only preparing the clock on probe and {en,dis}able in the >> rest of the driver. >> >> This

arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 5 months ago config:

arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 5 months ago config:

Re: [PATCH] bpf: avoid warning for wrong pointer cast

On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > Two new functions in bpf contain a cast from a 'u64' to a > pointer. This works on 64-bit architectures but causes a warning > on all 32-bit architectures: > > kernel/trace/bpf_trace.c: In function 'bpf_perf_event_output_tp': >

Re: [PATCH] bpf: avoid warning for wrong pointer cast

On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > Two new functions in bpf contain a cast from a 'u64' to a > pointer. This works on 64-bit architectures but causes a warning > on all 32-bit architectures: > > kernel/trace/bpf_trace.c: In function 'bpf_perf_event_output_tp': >

Re: [PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

On Sat, Apr 16, 2016 at 04:41:33PM -0700, Hugh Dickins wrote: > The pmd_fault() method gives the filesystem an opportunity to place > a trans huge pmd entry at *pmd, before any pagetable is exposed (and > an opportunity to split it on COW fault): now use it for huge tmpfs. > > This patch is a

Re: [PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

On Sat, Apr 16, 2016 at 04:41:33PM -0700, Hugh Dickins wrote: > The pmd_fault() method gives the filesystem an opportunity to place > a trans huge pmd entry at *pmd, before any pagetable is exposed (and > an opportunity to split it on COW fault): now use it for huge tmpfs. > > This patch is a

Re: [PATCH, RESEND] serial-uartlite: un-constify uartlite_be/uartlite_le

On Sun, Apr 17, 2016 at 02:12:47AM +0200, Arnd Bergmann wrote: > The patch to make uartlite_be/uartlite_le const was well-intended but > caused a new build warning: > > tty/serial/uartlite.c: In function 'ulite_request_port': > tty/serial/uartlite.c:348:21: error: assignment discards 'const'

Re: [PATCH, RESEND] serial-uartlite: un-constify uartlite_be/uartlite_le

On Sun, Apr 17, 2016 at 02:12:47AM +0200, Arnd Bergmann wrote: > The patch to make uartlite_be/uartlite_le const was well-intended but > caused a new build warning: > > tty/serial/uartlite.c: In function 'ulite_request_port': > tty/serial/uartlite.c:348:21: error: assignment discards 'const'

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

Hello Anand, On 04/16/2016 08:15 AM, Anand Moon wrote: [snip] >> > > Thanks for fixing this bug. I also tried the same thing on clk, but > missed the return on failed. > > Reviewed-by: Anand Moon > Tested-by: Anand Moon > Thanks a lot for your

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

Hello Anand, On 04/16/2016 08:15 AM, Anand Moon wrote: [snip] >> > > Thanks for fixing this bug. I also tried the same thing on clk, but > missed the return on failed. > > Reviewed-by: Anand Moon > Tested-by: Anand Moon > Thanks a lot for your testing and review. > Best Regards > -Anand

Re: Bug 116411: tools/perf_clean: output directory does not exist. Stop.

On 15-04-2016 17:00, Arnaldo Carvalho de Melo wrote: 8-< snip Thanks for narrowing it down, do you have any patch fixing this? I'm having some success with the following change although I'm a long way from completing tests of all possible permutations. It's a bit 'raw' and could be

Re: Bug 116411: tools/perf_clean: output directory does not exist. Stop.

On 15-04-2016 17:00, Arnaldo Carvalho de Melo wrote: 8-< snip Thanks for narrowing it down, do you have any patch fixing this? I'm having some success with the following change although I'm a long way from completing tests of all possible permutations. It's a bit 'raw' and could be

{standard input}:136: Error: number (0x9000000080000000) larger than 32 bits

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: de361e8bb9f666235d44ae9770238718be4f0483 MIPS: JZ4740: introduce CONFIG_MACH_INGENIC date: 10 months ago

{standard input}:136: Error: number (0x9000000080000000) larger than 32 bits

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: de361e8bb9f666235d44ae9770238718be4f0483 MIPS: JZ4740: introduce CONFIG_MACH_INGENIC date: 10 months ago

[PATCH, RESEND] serial-uartlite: un-constify uartlite_be/uartlite_le

The patch to make uartlite_be/uartlite_le const was well-intended but caused a new build warning: tty/serial/uartlite.c: In function 'ulite_request_port': tty/serial/uartlite.c:348:21: error: assignment discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]

[PATCH, RESEND] serial-uartlite: un-constify uartlite_be/uartlite_le

The patch to make uartlite_be/uartlite_le const was well-intended but caused a new build warning: tty/serial/uartlite.c: In function 'ulite_request_port': tty/serial/uartlite.c:348:21: error: assignment discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]

Re: [PATCH] ARM: dts: omap3-n900: Specify peripherals LDO regulators initial mode

Hi Ivo, On Sat, Apr 16, 2016 at 09:37:23AM +0300, Ivaylo Dimitrov wrote: > Without that, regulators are left in the mode last set by the bootloader or > by the kernel the device was rebooted from. This leads to various problems > like non-working peripherals. > > Signed-off-by: Ivaylo Dimitrov

Re: [PATCH] ARM: dts: omap3-n900: Specify peripherals LDO regulators initial mode

Hi Ivo, On Sat, Apr 16, 2016 at 09:37:23AM +0300, Ivaylo Dimitrov wrote: > Without that, regulators are left in the mode last set by the bootloader or > by the kernel the device was rebooted from. This leads to various problems > like non-working peripherals. > > Signed-off-by: Ivaylo Dimitrov

Re: [net][PATCH v2 0/2] RDS: couple of fixes for 4.6

On 4/16/2016 3:53 PM, David Miller wrote: From: Santosh Shilimkar Date: Thu, 14 Apr 2016 10:43:25 -0700 git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_4.6/net/rds-fixes I have no idea how you set this up, but there is no WAY this can

Re: [net][PATCH v2 0/2] RDS: couple of fixes for 4.6

On 4/16/2016 3:53 PM, David Miller wrote: From: Santosh Shilimkar Date: Thu, 14 Apr 2016 10:43:25 -0700 git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_4.6/net/rds-fixes I have no idea how you set this up, but there is no WAY this can be pulled from by me. Thought

collect2: error: ld returned 1 exit status

Hi Anton, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: 238abecde8ad43f914e095fcf23e0bd35dc7a7f2 powerpc: Don't use gcc specific options on clang date: 10 months

collect2: error: ld returned 1 exit status

Hi Anton, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 306a63bee192859ebd32c7328c7766636d882d8f commit: 238abecde8ad43f914e095fcf23e0bd35dc7a7f2 powerpc: Don't use gcc specific options on clang date: 10 months

Re: [PATCH v2] drm/msm: Use 64-bit timekeeping

On Wednesday 13 April 2016 02:52:14 Tina Ruchandani wrote: > ktime_t rem = ktime_sub(*timeout, now); > - struct timespec ts = ktime_to_timespec(rem); > - remaining_jiffies = timespec_to_jiffies(); > + struct

Re: [PATCH v2] drm/msm: Use 64-bit timekeeping

On Wednesday 13 April 2016 02:52:14 Tina Ruchandani wrote: > ktime_t rem = ktime_sub(*timeout, now); > - struct timespec ts = ktime_to_timespec(rem); > - remaining_jiffies = timespec_to_jiffies(); > + struct

[PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

The pmd_fault() method gives the filesystem an opportunity to place a trans huge pmd entry at *pmd, before any pagetable is exposed (and an opportunity to split it on COW fault): now use it for huge tmpfs. This patch is a little raw: with more time before LSF/MM, I would probably want to dress it

[PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault()

The pmd_fault() method gives the filesystem an opportunity to place a trans huge pmd entry at *pmd, before any pagetable is exposed (and an opportunity to split it on COW fault): now use it for huge tmpfs. This patch is a little raw: with more time before LSF/MM, I would probably want to dress it

Re: [Y2038] [PATCH] drm/sti: Use 64-bit timestamps

On Wednesday 13 April 2016 02:28:02 Tina Ruchandani wrote: > 'struct timespec' uses a 32-bit field for seconds, which > will overflow in year 2038 and beyond. This patch is part > of a larger attempt to remove instances of timeval, timespec > and time_t, all of which suffer from the y2038 issue,

Re: [Y2038] [PATCH] drm/sti: Use 64-bit timestamps

On Wednesday 13 April 2016 02:28:02 Tina Ruchandani wrote: > 'struct timespec' uses a 32-bit field for seconds, which > will overflow in year 2038 and beyond. This patch is part > of a larger attempt to remove instances of timeval, timespec > and time_t, all of which suffer from the y2038 issue,

[PATCH mmotm 4/5] huge tmpfs: avoid premature exposure of new pagetable revert

This patch reverts all of my 09/31, your huge-tmpfs-avoid-premature-exposure-of-new-pagetable.patch and also the mm/memory.c changes from the patch after it, huge-tmpfs-map-shmem-by-huge-page-pmd-or-by-page-team-ptes.patch I've diffed this against the top of the tree, but it may be better to

[PATCH mmotm 4/5] huge tmpfs: avoid premature exposure of new pagetable revert

This patch reverts all of my 09/31, your huge-tmpfs-avoid-premature-exposure-of-new-pagetable.patch and also the mm/memory.c changes from the patch after it, huge-tmpfs-map-shmem-by-huge-page-pmd-or-by-page-team-ptes.patch I've diffed this against the top of the tree, but it may be better to

Re: [PATCH v3] prism54: isl_38xx: Replace 'struct timeval'

On Wednesday 13 April 2016 10:38:26 Johannes Berg wrote: > > The patch was build-tested / debugged by removing the > > "if VERBOSE > SHOW_ERROR_MESSAGES" guards. > > Stands to reason that we should just remove the (more or less) dead > code, since I don't think anyone really ever touches this

Re: [PATCH v3] prism54: isl_38xx: Replace 'struct timeval'

On Wednesday 13 April 2016 10:38:26 Johannes Berg wrote: > > The patch was build-tested / debugged by removing the > > "if VERBOSE > SHOW_ERROR_MESSAGES" guards. > > Stands to reason that we should just remove the (more or less) dead > code, since I don't think anyone really ever touches this

DREAM TO SHARE WITH YOU

I am Capt. Lawrence Tyman, an officer in US Army,and also a West Point Graduate, serving in the Military with the 82nd Air Borne Division Peace keeping force deployed from Afganistan to Syria. We were moved to Syria from Iraq as the last batch just left,and i really need your help in assisting

DREAM TO SHARE WITH YOU

I am Capt. Lawrence Tyman, an officer in US Army,and also a West Point Graduate, serving in the Military with the 82nd Air Borne Division Peace keeping force deployed from Afganistan to Syria. We were moved to Syria from Iraq as the last batch just left,and i really need your help in assisting

Re: [PATCH] PCI: rcar: select PCI_MSI_IRQ_DOMAIN

On Sat, Apr 16, 2016 at 10:15:46PM +0200, Arnd Bergmann wrote: > The R-CAR PCIe driver requires the use of irq domains for its > MSI code: > > drivers/pci/host/pcie-rcar.c: In function 'rcar_pcie_msi_irq': > drivers/pci/host/pcie-rcar.c:635:9: error: implicit declaration of function >

[PATCH mmotm 3/5] huge tmpfs recovery: tweak shmem_getpage_gfp to fill team fix

Please add this fix after my 27/31, your huge-tmpfs-recovery-tweak-shmem_getpage_gfp-to-fill-team.patch for later merging into it. Great catch by Mika Penttila, a bug which prevented some unusual cases from being recovered into huge pages as intended: an initially sparse head would be set

Re: [PATCH] PCI: rcar: select PCI_MSI_IRQ_DOMAIN

On Sat, Apr 16, 2016 at 10:15:46PM +0200, Arnd Bergmann wrote: > The R-CAR PCIe driver requires the use of irq domains for its > MSI code: > > drivers/pci/host/pcie-rcar.c: In function 'rcar_pcie_msi_irq': > drivers/pci/host/pcie-rcar.c:635:9: error: implicit declaration of function >

[PATCH mmotm 3/5] huge tmpfs recovery: tweak shmem_getpage_gfp to fill team fix

Please add this fix after my 27/31, your huge-tmpfs-recovery-tweak-shmem_getpage_gfp-to-fill-team.patch for later merging into it. Great catch by Mika Penttila, a bug which prevented some unusual cases from being recovered into huge pages as intended: an initially sparse head would be set

[PATCH mmotm 2/5] huge tmpfs: fix mlocked meminfo track huge unhuge mlocks fix

Please add this fix after huge-tmpfs-fix-mlocked-meminfo-track-huge-unhuge-mlocks.patch for later merging into it. I expect this to fix a build problem found by robot on an x86_64 randconfig. I was not able to reproduce the error, but I'm growing to realize that different optimizers behave

[PATCH mmotm 2/5] huge tmpfs: fix mlocked meminfo track huge unhuge mlocks fix

Please add this fix after huge-tmpfs-fix-mlocked-meminfo-track-huge-unhuge-mlocks.patch for later merging into it. I expect this to fix a build problem found by robot on an x86_64 randconfig. I was not able to reproduce the error, but I'm growing to realize that different optimizers behave

[PATCH mmotm 1/5] huge tmpfs: try to allocate huge pages split into a team fix

Please replace the huge-tmpfs-try-to-allocate-huge-pages-split-into-a-team-fix.patch you added to your tree by this one: nothing wrong with Stephen's, but in this case I think the source is better off if we simply remove that BUILD_BUG() instead of adding an IS_ENABLED(): fixes build problem seen

[PATCH mmotm 1/5] huge tmpfs: try to allocate huge pages split into a team fix

Please replace the huge-tmpfs-try-to-allocate-huge-pages-split-into-a-team-fix.patch you added to your tree by this one: nothing wrong with Stephen's, but in this case I think the source is better off if we simply remove that BUILD_BUG() instead of adding an IS_ENABLED(): fixes build problem seen

  1   2   3   4   5   >