Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, > Am 24.09.2016 um 02:31 schrieb Sebastian Reichel : > > On Fri, Sep 23, 2016 at 05:47:26PM -0500, Rob Herring wrote: >> On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: >>> commit b98abe52fa8e ("Input: add common DT binding for touchscreens") >>>

Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, > Am 24.09.2016 um 02:31 schrieb Sebastian Reichel : > > On Fri, Sep 23, 2016 at 05:47:26PM -0500, Rob Herring wrote: >> On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: >>> commit b98abe52fa8e ("Input: add common DT binding for touchscreens") >>> introduced common DT

[PATCH 2/2] mfd: ab8500-debugfs: remove unused function

We get 1 warning when building kernel with W=1: drivers/mfd/ab8500-debugfs.c:1395:6: warning: no previous prototype for 'ab8500_dump_all_banks_to_mem' [-Wmissing-prototypes] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie

[PATCH 2/2] mfd: ab8500-debugfs: remove unused function

We get 1 warning when building kernel with W=1: drivers/mfd/ab8500-debugfs.c:1395:6: warning: no previous prototype for 'ab8500_dump_all_banks_to_mem' [-Wmissing-prototypes] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie ---

[PATCH 1/2] mfd: ab8500-debugfs: add function declaration

We get 1 warning when building kernel with W=1: drivers/mfd/ab8500-debugfs.c:1587:28: warning: no previous prototype for 'suspend_test_wake_cause_interrupt_is_mine' [-Wmissing-prototypes] In fact, this function need be declared in a header files. So this patch adds function declaration in

[PATCH 1/2] mfd: ab8500-debugfs: add function declaration

We get 1 warning when building kernel with W=1: drivers/mfd/ab8500-debugfs.c:1587:28: warning: no previous prototype for 'suspend_test_wake_cause_interrupt_is_mine' [-Wmissing-prototypes] In fact, this function need be declared in a header files. So this patch adds function declaration in

[PATCH] memstick: r592: add function declaration

We get 1 warning when building kernel with W=1: drivers/memstick/host/r592.c:50:13: warning: no previous prototype for 'memstick_debug_get_tpc_name' [-Wmissing-prototypes] In fact, this function need be declared in a header files. So this patch adds function declaration in

[PATCH] memstick: r592: add function declaration

We get 1 warning when building kernel with W=1: drivers/memstick/host/r592.c:50:13: warning: no previous prototype for 'memstick_debug_get_tpc_name' [-Wmissing-prototypes] In fact, this function need be declared in a header files. So this patch adds function declaration in

[PATCH] [media] coda: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/media/platform/coda/coda-h264.c:21:5: warning: no previous prototype for 'coda_h264_padding' [-Wmissing-prototypes] In fact, this function is declared in drivers/media/platform/coda/coda.h, so this patch adds missing header dependencies.

[PATCH] [media] coda: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/media/platform/coda/coda-h264.c:21:5: warning: no previous prototype for 'coda_h264_padding' [-Wmissing-prototypes] In fact, this function is declared in drivers/media/platform/coda/coda.h, so this patch adds missing header dependencies.

Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, > Am 24.09.2016 um 00:47 schrieb Rob Herring : > > On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: >> commit b98abe52fa8e ("Input: add common DT binding for touchscreens") >> introduced common DT bindings for touchscreens [1] and a helper function to >>

Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, > Am 24.09.2016 um 00:47 schrieb Rob Herring : > > On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: >> commit b98abe52fa8e ("Input: add common DT binding for touchscreens") >> introduced common DT bindings for touchscreens [1] and a helper function to >> parse the DT. >>

[PATCH 6/6] mISDN: remove unused function

We get 1 warning when building kernel with W=1: drivers/isdn/mISDN/layer2.c:463:1: warning: no previous declaration for 'IsRR' [-Wmissing-declarations] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie ---

[PATCH 6/6] mISDN: remove unused function

We get 1 warning when building kernel with W=1: drivers/isdn/mISDN/layer2.c:463:1: warning: no previous declaration for 'IsRR' [-Wmissing-declarations] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie ---

[PATCH 5/6] mISDN: mark symbols static where possible

We get a few warnings when building kernel with W=1: drivers/isdn/mISDN/layer2.c:120:1: warning: no previous declaration for 'l2headersize' [-Wmissing-declarations] drivers/isdn/mISDN/layer2.c:127:1: warning: no previous declaration for 'l2addrsize' [-Wmissing-declarations]

[PATCH 5/6] mISDN: mark symbols static where possible

We get a few warnings when building kernel with W=1: drivers/isdn/mISDN/layer2.c:120:1: warning: no previous declaration for 'l2headersize' [-Wmissing-declarations] drivers/isdn/mISDN/layer2.c:127:1: warning: no previous declaration for 'l2addrsize' [-Wmissing-declarations]

[PATCH 4/6] isdn/hisax: clean function declaration in hscx.c up

We get 1 warning when building kernel with W=1: drivers/isdn/hisax/hscx.c:175:1: warning: no previous prototype for 'open_hscxstate' [-Wmissing-prototypes] In fact, this function is declared in drivers/isdn/hisax/elsa_ser.c, but should be declard in a header file, thus can be recognized in other

[PATCH 4/6] isdn/hisax: clean function declaration in hscx.c up

We get 1 warning when building kernel with W=1: drivers/isdn/hisax/hscx.c:175:1: warning: no previous prototype for 'open_hscxstate' [-Wmissing-prototypes] In fact, this function is declared in drivers/isdn/hisax/elsa_ser.c, but should be declard in a header file, thus can be recognized in other

[PATCH 3/6] isdn/hisax: add function declarations

We get a few warnings when building kernel with W=1: drivers/isdn/hisax/teles3.c:273:5: warning: no previous prototype for 'setup_teles3' [-Wmissing-prototypes] drivers/isdn/hisax/s0box.c:213:5: warning: no previous prototype for 'setup_s0box' [-Wmissing-prototypes]

[PATCH 3/6] isdn/hisax: add function declarations

We get a few warnings when building kernel with W=1: drivers/isdn/hisax/teles3.c:273:5: warning: no previous prototype for 'setup_teles3' [-Wmissing-prototypes] drivers/isdn/hisax/s0box.c:213:5: warning: no previous prototype for 'setup_s0box' [-Wmissing-prototypes]

[PATCH 2/6] isdn/hardware/eicon: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/isdn/hardware/eicon/diva.c:655:6: warning: no previous prototype for 'xdiFreeFile' [-Wmissing-prototypes] In fact, this function is declared in drivers/isdn/hardware/eicon/helpers.h, so this patch adds missing header dependencies.

[PATCH 2/6] isdn/hardware/eicon: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/isdn/hardware/eicon/diva.c:655:6: warning: no previous prototype for 'xdiFreeFile' [-Wmissing-prototypes] In fact, this function is declared in drivers/isdn/hardware/eicon/helpers.h, so this patch adds missing header dependencies.

[PATCH 1/6] isdn/eicon: add function declarations

We get a few warnings when building kernel with W=1: drivers/isdn/hardware/eicon/diddfunc.c:95:12: warning: no previous prototype for 'diddfunc_init' [-Wmissing-prototypes] drivers/isdn/hardware/eicon/s_4bri.c:128:6: warning: no previous prototype for 'start_qBri_hardware' [-Wmissing-prototypes]

[PATCH 1/6] isdn/eicon: add function declarations

We get a few warnings when building kernel with W=1: drivers/isdn/hardware/eicon/diddfunc.c:95:12: warning: no previous prototype for 'diddfunc_init' [-Wmissing-prototypes] drivers/isdn/hardware/eicon/s_4bri.c:128:6: warning: no previous prototype for 'start_qBri_hardware' [-Wmissing-prototypes]

[PATCH] HSI: omap_ssi_core: move function declaration to header file

We get 1 warning when building kernel with W=1: drivers/hsi/controllers/omap_ssi_core.c:181:6: warning: no previous prototype for 'ssi_waketest' [-Wmissing-prototypes] In fact, this function is declared in drivers/hsi/clients/ssi_protocol.c, but should be declared in a header file. So this patch

[PATCH] HSI: omap_ssi_core: move function declaration to header file

We get 1 warning when building kernel with W=1: drivers/hsi/controllers/omap_ssi_core.c:181:6: warning: no previous prototype for 'ssi_waketest' [-Wmissing-prototypes] In fact, this function is declared in drivers/hsi/clients/ssi_protocol.c, but should be declared in a header file. So this patch

[PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

At the hardware level, the J-Core PIT is integrated with the interrupt controller, but it is represented as its own device and has an independent programming interface. It provides a 12-bit countdown timer, which is not presently used, and a periodic timer. The interval length for the latter is

[PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

At the hardware level, the J-Core PIT is integrated with the interrupt controller, but it is represented as its own device and has an independent programming interface. It provides a 12-bit countdown timer, which is not presently used, and a periodic timer. The interval length for the latter is

[PATCH v7 1/2] of: add J-Core timer bindings

Signed-off-by: Rich Felker Acked-by: Rob Herring --- .../devicetree/bindings/timer/jcore,pit.txt| 24 ++ 1 file changed, 24 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt diff --git

[PATCH v7 0/2] J-Core timer support

This version has been updated to include specific changes requested in the last round of review, and to work around a problem discussed with Paul McKenney (See thread "rcu_sched stalls in idle task introduced in pre-4.8?" for details). Rich Felker (2): of: add J-Core timer bindings

[PATCH v7 1/2] of: add J-Core timer bindings

Signed-off-by: Rich Felker Acked-by: Rob Herring --- .../devicetree/bindings/timer/jcore,pit.txt| 24 ++ 1 file changed, 24 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt diff --git

[PATCH v7 0/2] J-Core timer support

This version has been updated to include specific changes requested in the last round of review, and to work around a problem discussed with Paul McKenney (See thread "rcu_sched stalls in idle task introduced in pre-4.8?" for details). Rich Felker (2): of: add J-Core timer bindings

[PATCH] firmware/broadcom: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/firmware/broadcom/bcm47xx_sprom.c:717:5: warning: no previous prototype for 'bcm47xx_sprom_register_fallbacks' [-Wmissing-prototypes] In fact, this function is declared in include/linux/bcm47xx_sprom.h, so this patch adds missing header

[PATCH] firmware/broadcom: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/firmware/broadcom/bcm47xx_sprom.c:717:5: warning: no previous prototype for 'bcm47xx_sprom_register_fallbacks' [-Wmissing-prototypes] In fact, this function is declared in include/linux/bcm47xx_sprom.h, so this patch adds missing header

[PATCH 3/3] dmaengine: imx-sdma: remove unused function

We get 1 warning when building kernel with W=1: drivers/dma/imx-sdma.c:673:13: warning: 'sdma_handle_channel_loop' defined but not used [-Wunused-function] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie

[PATCH 3/3] dmaengine: imx-sdma: remove unused function

We get 1 warning when building kernel with W=1: drivers/dma/imx-sdma.c:673:13: warning: 'sdma_handle_channel_loop' defined but not used [-Wunused-function] In fact, this function is called by no one and not exported, so this patch removes it. Signed-off-by: Baoyou Xie ---

[PATCH 2/3] dmaengine: pxa_dma: add function declaration

We get 1 warning when building kernel with W=1: drivers/dma/pxa_dma.c:1525:5: warning: no previous prototype for 'pxad_toggle_reserved_channel' [-Wmissing-prototypes] In fact, this function is undeclared in any header files. So this patch adds function declaration in

[PATCH 2/3] dmaengine: pxa_dma: add function declaration

We get 1 warning when building kernel with W=1: drivers/dma/pxa_dma.c:1525:5: warning: no previous prototype for 'pxad_toggle_reserved_channel' [-Wmissing-prototypes] In fact, this function is undeclared in any header files. So this patch adds function declaration in

UBSAN: Undefined behaviour in ./arch/arm/include/asm/bitops.h

With the patch "arm: ubsan: select ARCH_HAS_UBSAN_SANITIZE_ALL", I got following UBSAN warning on Exynos5422 SoC board. UBSAN: Undefined behaviour in ./arch/arm/include/asm/bitops.h:296:17 negation of -2147483648

UBSAN: Undefined behaviour in ./arch/arm/include/asm/bitops.h

With the patch "arm: ubsan: select ARCH_HAS_UBSAN_SANITIZE_ALL", I got following UBSAN warning on Exynos5422 SoC board. UBSAN: Undefined behaviour in ./arch/arm/include/asm/bitops.h:296:17 negation of -2147483648

[PATCH 1/3] dmaengine: virt-dma: move function declarations

We get 2 warnings when building kernel with W=1: drivers/dma/virt-dma.c:22:14: warning: no previous prototype for 'vchan_tx_submit' [-Wmissing-prototypes] drivers/dma/virt-dma.c:52:5: warning: no previous prototype for 'vchan_tx_desc_free' [-Wmissing-prototypes] In fact, these two functions are

[PATCH 1/3] dmaengine: virt-dma: move function declarations

We get 2 warnings when building kernel with W=1: drivers/dma/virt-dma.c:22:14: warning: no previous prototype for 'vchan_tx_submit' [-Wmissing-prototypes] drivers/dma/virt-dma.c:52:5: warning: no previous prototype for 'vchan_tx_desc_free' [-Wmissing-prototypes] In fact, these two functions are

[PATCH] dma-buf/sw_sync: mark sync_timeline_create() static

We get 1 warning when building kernel with W=1: drivers/dma-buf/sw_sync.c:87:23: warning: no previous prototype for 'sync_timeline_create' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. So this

[PATCH] dma-buf/sw_sync: mark sync_timeline_create() static

We get 1 warning when building kernel with W=1: drivers/dma-buf/sw_sync.c:87:23: warning: no previous prototype for 'sync_timeline_create' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. So this

[PATCH] clk: versatile: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/clk/versatile/clk-realview.c:54:13: warning: no previous prototype for 'realview_clk_init' [-Wmissing-prototypes] In fact, this function is declared in include/linux/platform_data/clk-realview.h, so this patch adds missing header

[PATCH] clk: versatile: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/clk/versatile/clk-realview.c:54:13: warning: no previous prototype for 'realview_clk_init' [-Wmissing-prototypes] In fact, this function is declared in include/linux/platform_data/clk-realview.h, so this patch adds missing header

[PATCH] crypto: sunxi-ss: mark sun4i_hash() static

We get 1 warning when building kernel with W=1: drivers/crypto/sunxi-ss/sun4i-ss-hash.c:168:5: warning: no previous prototype for 'sun4i_hash' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. So

[PATCH] crypto: sunxi-ss: mark sun4i_hash() static

We get 1 warning when building kernel with W=1: drivers/crypto/sunxi-ss/sun4i-ss-hash.c:168:5: warning: no previous prototype for 'sun4i_hash' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. So

[PATCH] random: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/char/random.c:2140:6: warning: no previous prototype for 'add_hwgenerator_randomness' [-Wmissing-prototypes] In fact, this function is declared in include/linux/hw_random.h, so this patch adds missing header dependencies. Signed-off-by:

[PATCH] random: add missing header dependencies

We get 1 warning when building kernel with W=1: drivers/char/random.c:2140:6: warning: no previous prototype for 'add_hwgenerator_randomness' [-Wmissing-prototypes] In fact, this function is declared in include/linux/hw_random.h, so this patch adds missing header dependencies. Signed-off-by:

Re: [PATCH cgroup/for-4.8-fixes] cgroup: fix invalid controller enable rejections with cgroup namespace

On Fri, Sep 23, 2016 at 05:00:03PM -0400, Tejun Heo wrote: > >From 9157056da8f8c4a6305f15619e269f164b63a6de Mon Sep 17 00:00:00 2001 > From: Tejun Heo > Date: Fri, 23 Sep 2016 16:55:49 -0400 > > On the v2 hierarchy, "cgroup.subtree_control" rejects controller > enables if the

[PATCH] drbd: mark symbols static where possible

We get 4 warnings when building kernel with W=1: drivers/block/drbd/drbd_worker.c:197:6: warning: no previous prototype for 'drbd_panic_after_delayed_completion_of_aborted_request' [-Wmissing-prototypes] drivers/block/drbd/drbd_receiver.c:1224:6: warning: no previous prototype for

Re: [PATCH cgroup/for-4.8-fixes] cgroup: fix invalid controller enable rejections with cgroup namespace

On Fri, Sep 23, 2016 at 05:00:03PM -0400, Tejun Heo wrote: > >From 9157056da8f8c4a6305f15619e269f164b63a6de Mon Sep 17 00:00:00 2001 > From: Tejun Heo > Date: Fri, 23 Sep 2016 16:55:49 -0400 > > On the v2 hierarchy, "cgroup.subtree_control" rejects controller > enables if the cgroup has

[PATCH] drbd: mark symbols static where possible

We get 4 warnings when building kernel with W=1: drivers/block/drbd/drbd_worker.c:197:6: warning: no previous prototype for 'drbd_panic_after_delayed_completion_of_aborted_request' [-Wmissing-prototypes] drivers/block/drbd/drbd_receiver.c:1224:6: warning: no previous prototype for

hi

Salutations http://flatcreekcrossingranch.com/mile.php?missing=1pubc8052vea Will C

hi

Salutations http://flatcreekcrossingranch.com/mile.php?missing=1pubc8052vea Will C

Re: [PATCH] samples: move blackfin gptimers-example from Documentation

On 09/23/2016 05:45 PM, Shuah Khan wrote: > Move blackfin gptimers-example to samples and remove the Documentation > Makefile. Update samples Kconfig and Makefile to build gptimers-example. > > Signed-off-by: Shuah Khan This patch isn't complete. CONFIG_BUILD_DOCSRC=1

Re: [PATCH] samples: move blackfin gptimers-example from Documentation

On 09/23/2016 05:45 PM, Shuah Khan wrote: > Move blackfin gptimers-example to samples and remove the Documentation > Makefile. Update samples Kconfig and Makefile to build gptimers-example. > > Signed-off-by: Shuah Khan This patch isn't complete. CONFIG_BUILD_DOCSRC=1 make fails without

Re: [PATCH 2/3] f2fs: support checkpoint error injection

On 2016/9/24 8:52, Jaegeuk Kim wrote: > On Sat, Sep 24, 2016 at 08:46:54AM +0800, Chao Yu wrote: >> Hi Jaegeuk, >> >> On 2016/9/24 7:53, Jaegeuk Kim wrote: >>> Hi Chao, >>> >>> The basic rule is to stop every operations once CP_ERROR_FLAG is set. >>> But, this patch simply breaks the rule. >>> For

Re: [PATCH 2/3] f2fs: support checkpoint error injection

On 2016/9/24 8:52, Jaegeuk Kim wrote: > On Sat, Sep 24, 2016 at 08:46:54AM +0800, Chao Yu wrote: >> Hi Jaegeuk, >> >> On 2016/9/24 7:53, Jaegeuk Kim wrote: >>> Hi Chao, >>> >>> The basic rule is to stop every operations once CP_ERROR_FLAG is set. >>> But, this patch simply breaks the rule. >>> For

[PATCH 3/3] mm: delete unnecessary and unsafe init_tlb_ubc()

init_tlb_ubc() looked unnecessary to me: tlb_ubc is statically initialized with zeroes in the init_task, and copied from parent to child while it is quiescent in arch_dup_task_struct(); so I went to delete it. But inserted temporary debug WARN_ONs in place of init_tlb_ubc() to check that it was

[PATCH 3/3] mm: delete unnecessary and unsafe init_tlb_ubc()

init_tlb_ubc() looked unnecessary to me: tlb_ubc is statically initialized with zeroes in the init_task, and copied from parent to child while it is quiescent in arch_dup_task_struct(); so I went to delete it. But inserted temporary debug WARN_ONs in place of init_tlb_ubc() to check that it was

[PATCH 2/3] huge tmpfs: fix Committed_AS leak

Under swapping load on huge tmpfs, /proc/meminfo's Committed_AS grows bigger and bigger: just a cosmetic issue for most users, but disabling for those who run without overcommit (/proc/sys/vm/overcommit_memory 2). shmem_uncharge() was forgetting to unaccount __vm_enough_memory's charge, and

[PATCH 2/3] huge tmpfs: fix Committed_AS leak

Under swapping load on huge tmpfs, /proc/meminfo's Committed_AS grows bigger and bigger: just a cosmetic issue for most users, but disabling for those who run without overcommit (/proc/sys/vm/overcommit_memory 2). shmem_uncharge() was forgetting to unaccount __vm_enough_memory's charge, and

[PATCH 1/3] shmem: fix tmpfs to handle the huge= option properly

From: Toshi Kani shmem_get_unmapped_area() checks SHMEM_SB(sb)->huge incorrectly, which leads to a reversed effect of "huge=" mount option. Fix the check in shmem_get_unmapped_area(). Note, the default value of SHMEM_SB(sb)->huge remains as SHMEM_HUGE_NEVER. User will need

[PATCH 1/3] shmem: fix tmpfs to handle the huge= option properly

From: Toshi Kani shmem_get_unmapped_area() checks SHMEM_SB(sb)->huge incorrectly, which leads to a reversed effect of "huge=" mount option. Fix the check in shmem_get_unmapped_area(). Note, the default value of SHMEM_SB(sb)->huge remains as SHMEM_HUGE_NEVER. User will need to specify "huge="

drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bd5dbcb4be37ce97b115bf9e8d48ae75f0d8a9a2 commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 4

drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: bd5dbcb4be37ce97b115bf9e8d48ae75f0d8a9a2 commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 4

Re: [PATCH] mm: warn about allocations which stall for too long

Michal Hocko wrote: > On Fri 23-09-16 23:36:22, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned > > > int order, > > > else > > > no_progress_loops++; > > > > > > + /* Make sure we know about allocations which

Re: [PATCH] mm: warn about allocations which stall for too long

Michal Hocko wrote: > On Fri 23-09-16 23:36:22, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned > > > int order, > > > else > > > no_progress_loops++; > > > > > > + /* Make sure we know about allocations which

Re: [RFC] remove unnecessary condition in remove_inode_hugepages

On 2016/9/24 1:19, Mike Kravetz wrote: > On 09/22/2016 06:53 PM, zhong jiang wrote: >> At present, we need to call hugetlb_fix_reserve_count when >> hugetlb_unrserve_pages fails, >> and PagePrivate will decide hugetlb reserves counts. >> >> we obtain the page from page cache. and use page both

Re: [RFC] remove unnecessary condition in remove_inode_hugepages

On 2016/9/24 1:19, Mike Kravetz wrote: > On 09/22/2016 06:53 PM, zhong jiang wrote: >> At present, we need to call hugetlb_fix_reserve_count when >> hugetlb_unrserve_pages fails, >> and PagePrivate will decide hugetlb reserves counts. >> >> we obtain the page from page cache. and use page both

Re: [RFC] fs: add userspace critical mounts event support

On 06/09/2016 16:04, Luis R. Rodriguez wrote: > They claim that without it there is the race between /lib/firmware > being ready and driver asking for the firmware. Hope it's understood by now. > I was told there were quite a bit of out-of-tree hacks to address > this without using the usermode

Re: [RFC] fs: add userspace critical mounts event support

On 06/09/2016 16:04, Luis R. Rodriguez wrote: > They claim that without it there is the race between /lib/firmware > being ready and driver asking for the firmware. Hope it's understood by now. > I was told there were quite a bit of out-of-tree hacks to address > this without using the usermode

Re: Regression in 4.8 - CPU speed set very low

On 09/18/2016 09:54 PM, Larry Finger wrote: On 09/14/2016 11:00 AM, Larry Finger wrote: On 09/09/2016 12:39 PM, Larry Finger wrote: I have found a regression in kernel 4.8-rc2 that causes the speed of my laptop with an Intel(R) Core(TM) i7-4600M CPU @ 2.90GHz to suddenly have a maximum cpu

Re: Regression in 4.8 - CPU speed set very low

On 09/18/2016 09:54 PM, Larry Finger wrote: On 09/14/2016 11:00 AM, Larry Finger wrote: On 09/09/2016 12:39 PM, Larry Finger wrote: I have found a regression in kernel 4.8-rc2 that causes the speed of my laptop with an Intel(R) Core(TM) i7-4600M CPU @ 2.90GHz to suddenly have a maximum cpu

drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags'

Hi Linus, 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: 78bbf153fa96e5e40234b7b05567602535645460 commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 5 weeks

drivers/gpio/gpiolib.c:3215: undefined reference to `of_get_named_gpiod_flags'

Hi Linus, 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: 78bbf153fa96e5e40234b7b05567602535645460 commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 5 weeks

Re: [RFC] fs: add userspace critical mounts event support

On 03/09/2016 11:10, Dmitry Torokhov wrote: > I was thinking if we kernel could post > "conditions" (maybe simple stings) that it waits for, and userspace > could unlock these "conditions". One of them might be "firmware > available". On idea offered by Josh Triplett that seems to overlap with

Re: [RFC] fs: add userspace critical mounts event support

On 03/09/2016 11:10, Dmitry Torokhov wrote: > I was thinking if we kernel could post > "conditions" (maybe simple stings) that it waits for, and userspace > could unlock these "conditions". One of them might be "firmware > available". On idea offered by Josh Triplett that seems to overlap with

Re: [PATCH v2] clk: hisilicon: add CRG driver for Hi3798CV200 SoC

在 2016/9/24 1:47, Rob Herring 写道: > On Sun, Sep 18, 2016 at 03:30:21PM +0800, Jiancheng Xue wrote: >> Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset >> Generator) module generates clock and reset signals used >> by other module blocks on SoC. >> >> Signed-off-by: Jiancheng Xue

Re: [PATCH v2] clk: hisilicon: add CRG driver for Hi3798CV200 SoC

在 2016/9/24 1:47, Rob Herring 写道: > On Sun, Sep 18, 2016 at 03:30:21PM +0800, Jiancheng Xue wrote: >> Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset >> Generator) module generates clock and reset signals used >> by other module blocks on SoC. >> >> Signed-off-by: Jiancheng Xue >> --- >>

[PATCH -tip] locking/rtmutex: Reduce top-waiter blocking on a lock

By applying well known spin-on-lock-owner techniques, we can avoid the blocking overhead during the process of when the task is trying to take the rtmutex. The idea is that as long as the owner is running, there is a fair chance it'll release the lock soon, and thus a task trying to acquire the

[PATCH -tip] locking/rtmutex: Reduce top-waiter blocking on a lock

By applying well known spin-on-lock-owner techniques, we can avoid the blocking overhead during the process of when the task is trying to take the rtmutex. The idea is that as long as the owner is running, there is a fair chance it'll release the lock soon, and thus a task trying to acquire the

Re: [PATCH v3 0/2] Exynos IOMMU: proper runtime PM support (use device dependencies)

On Friday, September 23, 2016 03:50:02 PM Lukas Wunner wrote: > On Fri, Sep 23, 2016 at 02:49:20PM +0200, Rafael J. Wysocki wrote: > > On Tuesday, September 20, 2016 10:51:13 AM Marek Szyprowski wrote: > > > On 2016-09-19 23:45, Tobias Jakobi wrote: > > > > I did some tests with the new version

Re: [PATCH v3 0/2] Exynos IOMMU: proper runtime PM support (use device dependencies)

On Friday, September 23, 2016 03:50:02 PM Lukas Wunner wrote: > On Fri, Sep 23, 2016 at 02:49:20PM +0200, Rafael J. Wysocki wrote: > > On Tuesday, September 20, 2016 10:51:13 AM Marek Szyprowski wrote: > > > On 2016-09-19 23:45, Tobias Jakobi wrote: > > > > I did some tests with the new version

Re: modules still have .debug_* (was Re: [PATCH 0/3] ARC unwinder switch to .eh_frame)

On Fri, Sep 23, 2016 at 3:38 AM, Alexey Brodkin wrote: > On Thu, 2016-09-22 at 15:37 -0700, Daniel Mentz wrote: >> Sorry, that was a misunderstanding. Buildroot routinely runs the strip >> command on .ko files before installing them on the target. I was only >>

Re: modules still have .debug_* (was Re: [PATCH 0/3] ARC unwinder switch to .eh_frame)

On Fri, Sep 23, 2016 at 3:38 AM, Alexey Brodkin wrote: > On Thu, 2016-09-22 at 15:37 -0700, Daniel Mentz wrote: >> Sorry, that was a misunderstanding. Buildroot routinely runs the strip >> command on .ko files before installing them on the target. I was only >> looking at the .ko files *after*

Re: [PATCH] f2fs: remove dirty inode pages in error path

On 2016/9/24 5:11, Jaegeuk Kim wrote: > When getting EIO while handling orphan inodes, we can get some dirty node > pages. Then, f2fs_write_node_pages() called by iput(node_inode) will try > to flush node pages. But in this case, we should prevent to do that, since > we will try again from the

Re: [PATCH] f2fs: remove dirty inode pages in error path

On 2016/9/24 5:11, Jaegeuk Kim wrote: > When getting EIO while handling orphan inodes, we can get some dirty node > pages. Then, f2fs_write_node_pages() called by iput(node_inode) will try > to flush node pages. But in this case, we should prevent to do that, since > we will try again from the

Re: [PATCH 2/3] f2fs: support checkpoint error injection

On Sat, Sep 24, 2016 at 08:46:54AM +0800, Chao Yu wrote: > Hi Jaegeuk, > > On 2016/9/24 7:53, Jaegeuk Kim wrote: > > Hi Chao, > > > > The basic rule is to stop every operations once CP_ERROR_FLAG is set. > > But, this patch simply breaks the rule. > > For example, f2fs_write_data_page()

Re: [PATCH 2/3] f2fs: support checkpoint error injection

On Sat, Sep 24, 2016 at 08:46:54AM +0800, Chao Yu wrote: > Hi Jaegeuk, > > On 2016/9/24 7:53, Jaegeuk Kim wrote: > > Hi Chao, > > > > The basic rule is to stop every operations once CP_ERROR_FLAG is set. > > But, this patch simply breaks the rule. > > For example, f2fs_write_data_page()

Re: [PATCH 2/3] f2fs: support checkpoint error injection

Hi Jaegeuk, On 2016/9/24 7:53, Jaegeuk Kim wrote: > Hi Chao, > > The basic rule is to stop every operations once CP_ERROR_FLAG is set. > But, this patch simply breaks the rule. > For example, f2fs_write_data_page() currently exits with mapping_set_error(). > So this patch incurs missing dentry

Re: [PATCH 2/3] f2fs: support checkpoint error injection

Hi Jaegeuk, On 2016/9/24 7:53, Jaegeuk Kim wrote: > Hi Chao, > > The basic rule is to stop every operations once CP_ERROR_FLAG is set. > But, this patch simply breaks the rule. > For example, f2fs_write_data_page() currently exits with mapping_set_error(). > So this patch incurs missing dentry

Re: linux-next: Tree for Sep 21

Hi Linus, On Fri, 23 Sep 2016 11:24:04 -0700 Linus Torvalds wrote: > > On Tue, Sep 20, 2016 at 11:08 PM, Stephen Rothwell > wrote: > > > > Changes since 20160920: > > [...] > > Non-merge commits (relative to Linus' tree): 11180 > > 8424

Re: linux-next: Tree for Sep 21

Hi Linus, On Fri, 23 Sep 2016 11:24:04 -0700 Linus Torvalds wrote: > > On Tue, Sep 20, 2016 at 11:08 PM, Stephen Rothwell > wrote: > > > > Changes since 20160920: > > [...] > > Non-merge commits (relative to Linus' tree): 11180 > > 8424 files changed, 456474 insertions(+), 237951

Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

On Fri, Sep 23, 2016 at 05:47:26PM -0500, Rob Herring wrote: > On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: > > commit b98abe52fa8e ("Input: add common DT binding for touchscreens") > > introduced common DT bindings for touchscreens [1] and a helper function to > > parse

Re: [PATCH v3 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

On Fri, Sep 23, 2016 at 05:47:26PM -0500, Rob Herring wrote: > On Fri, Sep 23, 2016 at 02:41:09PM +0200, H. Nikolaus Schaller wrote: > > commit b98abe52fa8e ("Input: add common DT binding for touchscreens") > > introduced common DT bindings for touchscreens [1] and a helper function to > > parse

Re: [PATCH v2 0/4] ACPI / watchdog: Add support for WDAT (Watchdog Action Table)

On Tuesday, September 20, 2016 03:30:50 PM Mika Westerberg wrote: > Hi, > > The WDAT (Watchdog Action Table) is a special ACPI table introduced by > Microsoft [1] that abstracts the watchdog hardware from the OS. Windows > uses this table for its watchdog implementation instead of a native iTCO >

Re: [PATCH v2 0/4] ACPI / watchdog: Add support for WDAT (Watchdog Action Table)

On Tuesday, September 20, 2016 03:30:50 PM Mika Westerberg wrote: > Hi, > > The WDAT (Watchdog Action Table) is a special ACPI table introduced by > Microsoft [1] that abstracts the watchdog hardware from the OS. Windows > uses this table for its watchdog implementation instead of a native iTCO >

  1   2   3   4   5   6   7   8   9   10   >