[PATCH 1/2] ARM: dts: pxa: add pincontrol helpers

2018-07-01 Thread Robert Jarzmik
Add 3 helpers so that pincontrol definitions for pxa25x and pxa27x are easier, and can be easily converted from old mfp mach-pxa code to devicetree. An example of such conversion would be : static unsigned long mioa701_pin_config[] = { GPIO32_MMC_CLK, GPIO92_MMC_DAT_0,

[PATCH 2/2] ARM: dts: pxa: add mioa701 board description

2018-07-01 Thread Robert Jarzmik
Add device-tree description of the Mitac MIO A701 board. This is aimed at replacing mioa701.c board file, and once stabilized, the leftover, such as the suspend resume mechanics will rely on a new IPL, and not the legacy Windows CE one. Signed-off-by: Robert Jarzmik --- This patch deserves some

Re: [PATCH v2 0/6] mm/fs: gup: don't unmap or drop filesystem buffers

2018-07-01 Thread John Hubbard
On 07/01/2018 05:56 PM, john.hubb...@gmail.com wrote: > From: John Hubbard > There were some typos in patches #4 and #5, which I've fixed locally. Let me know if anyone would like me to repost with those right away, otherwise I'll wait for other review besides the kbuild test robot. Meanwhile,

[PATCH v5 3/6] fs/dcache: Enable automatic pruning of negative dentries

2018-07-01 Thread Waiman Long
It is not good enough to have a soft limit for the number of negative dentries in the system and print a warning if that limit is exceeded. We need to do something about it when this happens. This patch enables automatic pruning of negative dentries when the soft limit is going to be exceeded.

[PATCH v5 4/6] fs/dcache: Spread negative dentry pruning across multiple CPUs

2018-07-01 Thread Waiman Long
Doing negative dentry pruning using schedule_delayed_work() will typically concentrate the pruning effort on one particular CPU. That is not fair to the tasks running on that CPU. In addition, it is possible that one CPU can have all its negative dentries pruned away while the others can still

[PATCH v5 1/6] fs/dcache: Track & report number of negative dentries

2018-07-01 Thread Waiman Long
The current dentry number tracking code doesn't distinguish between positive & negative dentries. It just reports the total number of dentries in the LRU lists. As excessive number of negative dentries can have an impact on system performance, it will be wise to track the number of positive and

Re: [PATCH 2/2] mm: set PG_dma_pinned on get_user_pages*()

2018-07-01 Thread Leon Romanovsky
On Thu, Jun 28, 2018 at 11:17:43AM +0200, Jan Kara wrote: > On Wed 27-06-18 19:42:01, John Hubbard wrote: > > On 06/27/2018 10:02 AM, Jan Kara wrote: > > > On Wed 27-06-18 08:57:18, Jason Gunthorpe wrote: > > >> On Wed, Jun 27, 2018 at 02:42:55PM +0200, Jan Kara wrote: > > >>> On Wed 27-06-18

[PATCH v5 6/6] fs/dcache: Make negative dentry limit enforcement sysctl parameter

2018-07-01 Thread Waiman Long
It can be useful to make negative dentry limit enformcement a runtime tuning parameter instead of just a boot time option. This allows system administrator to disable limit enforcement in normal use, but turn it on under certain circumstances. A new /proc/sys/fs/enforce-neg-dentry-limit sysctl

[PATCH v5 5/6] fs/dcache: Allow optional enforcement of negative dentry limit

2018-07-01 Thread Waiman Long
If a rogue application that generates a large number of negative dentries is running, the automatic negative dentries pruning process may not be fast enough to clear up the negative dentries in time. In this case, it is possible that negative dentries will use up most of the available memory in

[PATCH v5 0/6] fs/dcache: Track & limit # of negative dentries

2018-07-01 Thread Waiman Long
v4->v5: - Backed to the latest 4.18 kernel and modify the code accordingly. Patch 1 "Relocate dentry_kill() after lock_parent()" is now no longer necessary. - Make tracking and limiting of negative dentries an user configurable option (CONFIG_DCACHE_TRACK_NEG_ENTRY) so that users

[PATCH v5 2/6] fs/dcache: Make negative dentry tracking configurable

2018-07-01 Thread Waiman Long
The negative dentry tracking is made a configurable option so that users who don't care about negative dentry tracking will have the option to disable it. The new config option DCACHE_TRACK_NEG_ENTRY is disabled by default. If this option is enabled, a new kernel parameter "neg_dentry_pc=<%>"

Re: [PATCH -mm -v4 03/21] mm, THP, swap: Support PMD swap mapping in swap_duplicate()

2018-07-01 Thread Huang, Ying
Matthew Wilcox writes: > On Fri, Jun 22, 2018 at 11:51:33AM +0800, Huang, Ying wrote: >> +++ b/mm/swap_state.c >> @@ -433,7 +433,7 @@ struct page *__read_swap_cache_async(swp_entry_t entry, >> gfp_t gfp_mask, >> /* >> * Swap entry may have been freed since our caller

Re: [PATCH -mm -v4 00/21] mm, THP, swap: Swapout/swapin THP in one piece

2018-07-01 Thread Huang, Ying
Matthew Wilcox writes: > On Fri, Jun 29, 2018 at 09:17:16AM +0800, Huang, Ying wrote: >> Matthew Wilcox writes: >> > I'll take a look. Honestly, my biggest problem with this patch set is >> > overuse of tagging: >> > >> > 59832 Jun 22 Huang, Ying ( 131) [PATCH -mm -v4 00/21] mm, THP,

[lkp-robot] [x86/kernel] b1ff47aace: WARNING:at_kernel/jump_label.c:#__jump_label_update

2018-07-01 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: b1ff47aacea95e5be1bedf2aee740395b52f4591 ("[PATCH 5/5] x86/kernel: jump_table: use relative references") url:

Re: [PATCH v2 5/6] mm: track gup pages with page->dma_pinned_* fields

2018-07-01 Thread John Hubbard
On 07/01/2018 07:58 PM, kbuild test robot wrote: > Hi John, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.18-rc3] > [cannot apply to next-20180629] > [if your patch is applied to the wrong git tree,

Re: [PATCH v7 3/6] kernel/reboot.c: export pm_power_off_prepare

2018-07-01 Thread Oleksij Rempel
Hi Rafael, it is two weeks since this email. Probably it was lost some where in the space time continuum. Can you please respond to it :) On 17.06.2018 09:05, Shawn Guo wrote: > On Tue, Jun 12, 2018 at 04:33:05PM +0200, Rafael J. Wysocki wrote: >> On Tuesday, June 12, 2018 2:42:12 PM CEST

drivers/android/.tmp_gl_binder.o:undefined reference to `__user_bad'

2018-07-01 Thread kbuild test robot
Hi Martijn, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 021c91791a5e7e85c567452f1be3e4c2c6cb6063 commit: 1190b4e38f97023154e6b3bef61b251aa5f970d0 ANDROID: binder: remove 32-bit binder interface. date: 7 weeks

Re: [PATCH 1/1] ARM: dts: imx6ull: add operating points

2018-07-01 Thread Viresh Kumar
On 29-06-18, 16:52, Sébastien Szymanski wrote: > i.MX6ULL has different operating ranges than i.MX6UL so add the > operating points for the i.MX6ULL and removed them form board device s/removed/remove/ s/form/from/ > trees. A 25mV offset is added to the minimum allowed values like for the >

linux-next: Tree for Jul 2

2018-07-01 Thread Stephen Rothwell
Hi all, Changes since 20180629: New tree: siox The btrfs-kdave tree lost its build failure. The fbdev tree lost its build failure. The net-next tree gained conflicts against the net and rdma trees. The akpm-current tree still had its build failure for which I reverted a commit. Non-merge

Re: [PATCH RFC tip/core/rcu 1/2] rcu: Defer reporting RCU-preempt quiescent states when disabled

2018-07-01 Thread Joel Fernandes
On Sun, Jul 01, 2018 at 08:11:32PM -0700, Paul E. McKenney wrote: > On Sun, Jul 01, 2018 at 05:35:53PM -0700, Joel Fernandes wrote: > > On Sun, Jul 01, 2018 at 03:27:49PM -0700, Paul E. McKenney wrote: > > [...] > > > > > +/* > > > > > + * Report a deferred quiescent state if needed and safe to do

Re: [PATCH v2 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

2018-07-01 Thread John Hubbard
On 07/01/2018 07:47 PM, kbuild test robot wrote: > Hi John, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.18-rc3] > [cannot apply to next-20180629] > [if your patch is applied to the wrong git tree, please drop

Re: [PATCH v2 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

2018-07-01 Thread John Hubbard
On 07/01/2018 07:11 PM, kbuild test robot wrote: > Hi John, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.18-rc3] > [cannot apply to next-20180629] > [if your patch is applied to the wrong git tree,

Re: [PATCH v2] stop_machine: Disable preemption when waking two stopper threads

2018-07-01 Thread Pavan Kondeti
Hi Issac, On Fri, Jun 29, 2018 at 01:55:12PM -0700, Isaac J. Manjarres wrote: > When cpu_stop_queue_two_works() begins to wake the stopper > threads, it does so without preemption disabled, which leads > to the following race condition: > > The source CPU calls cpu_stop_queue_two_works(), with

Re: [PATCH v5 2/2] arm64: KVM: export the capability to set guest SError syndrome

2018-07-01 Thread gengdongjiu
Hi James, On 2018/6/29 23:58, James Morse wrote: > Hi Dongjiu Geng, > > This patch doesn't apply on v4.18-rc2. > > Documentation/virtual/kvm/api.txt already has a 8.18 section. I guess you > based > this on v4.17. Yes, indeed I based on v4.17. > > For posting patches, please use the latest

Re: [Update] Regression in 4.18 - 32-bit PowerPC crashes on boot - bisected to commit 1d40a5ea01d5

2018-07-01 Thread Michael Ellerman
Linus Torvalds writes: > On Fri, Jun 29, 2018 at 1:42 PM Larry Finger > wrote: >> >> I have more information regarding this BUG. Line 700 of page-flags.h is the >> macro PAGE_TYPE_OPS(Table, table). For further debugging, I manually expanded >> the macro, and found that the bug line is

[PATCH 0/3] fix selftests compiling errors and warnings

2018-07-01 Thread Li Zhijian
Li Zhijian (3): selftests/android: fix compiling error selftests/android: initialize heap_type to avoid compiling warning selftests/gpio: unset OUTPUT for build tools/gpio tools/testing/selftests/android/ion/Makefile| 5 - tools/testing/selftests/android/ion/ionapp_export.c |

[PATCH 1/3] selftests/android: fix compiling error

2018-07-01 Thread Li Zhijian
lizhijian@haswell-OptiPlex-9020:/home/lizj/linux/tools/testing/selftests/android/ion$ make gcc -I. -I../../../../../drivers/staging/android/uapi/ -I../../../../../usr/include/ -Wall -O2 -gionapp_export.c ipcsocket.c ionutils.c -o ionapp_export gcc -I.

[PATCH 3/3] selftests/gpio: unset OUTPUT for build tools/gpio

2018-07-01 Thread Li Zhijian
when we execute 'make' to build selftests, the TOP Makefile build gpio like: selftests$ make ARCH= CROSS_COMPILE= OUTPUT=/home/lizj/linux/tools/testing/selftests/gpio -C gpio ... make[2]: Leaving directory '/home/lizj/linux/tools/gpio' gcc -O2 -g -std=gnu99 -Wall

[PATCH 2/3] selftests/android: initialize heap_type to avoid compiling warning

2018-07-01 Thread Li Zhijian
root@vm-lkp-nex04-8G-7 ~/linux-v4.18-rc2/tools/testing/selftests/android# make make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/root/linux-v4.18-rc2/tools/testing/selftests/android/ion' gcc -I.

[PATCH v2 3/4] PCI: mediatek: Add system pm support for MT2712 and MT7622

2018-07-01 Thread honghui.zhang
From: Honghui Zhang The MTCMOS of PCIe Host for MT2712 and MT7622 will be off when system suspend, and all the internal control register will be reset after system resume. The PCIe link should be re-established and the related control register values should be re-set after system resume.

[PATCH v2 1/4] PCI: mediatek: fixup mtk_pcie_find_port logical

2018-07-01 Thread honghui.zhang
From: Honghui Zhang The Mediatek's host controller has two slots, each with it's own control registers. The host driver need to identify which slot was connected in order to access the device's configuration space. There's problem for current host driver to find out which slot was connected to

[PATCH v2 4/4] PCI: mediatek: Add loadable kernel module support

2018-07-01 Thread honghui.zhang
From: Honghui Zhang Implement remove callback function for Mediatek PCIe driver to add loadable kernel module support. Signed-off-by: Honghui Zhang --- drivers/pci/controller/Kconfig | 2 +- drivers/pci/controller/pcie-mediatek.c | 60 +++--- 2 files

[PATCH v2 2/4] PCI: mediatek: enable msi after clock enabled

2018-07-01 Thread honghui.zhang
From: Honghui Zhang The clocks was not enabled when enable MSI. This patch fix this issue by calling mtk_pcie_enable_msi in mtk_pcie_startup_port_v2 since the clock was all enabled at that time. The function of mtk_pcie_startup_port_v2's define location is re-arranged to avoid

[PATCH v2 0/4] PCI: mediatek: fixup find_port, enable_msi and add pm, module support

2018-07-01 Thread honghui.zhang
From: Honghui Zhang This patchset includes misc patchs: The first patch fixup the mtk_pcie_find_port logical which will cause system could not touch the EP's configuration space which was connected to PCIe slot 1. The second patch fixup the enable msi logical, the operation to enable msi

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/01/18 at 11:28pm, Pavel Tatashin wrote: > > > So, on the first failure, we even stop trying to populate other > > > sections. No more memory to do so. > > > > This is the thing I worry about. In old sparse_mem_maps_populate_node() > > you can see, when not present or failed to populate, just

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
> > So, on the first failure, we even stop trying to populate other > > sections. No more memory to do so. > > This is the thing I worry about. In old sparse_mem_maps_populate_node() > you can see, when not present or failed to populate, just continue. This > is the main difference between yours

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/02/18 at 11:14am, Baoquan He wrote: > On 07/01/18 at 11:03pm, Pavel Tatashin wrote: > > > Ah, yes, I misunderstood it, sorry for that. > > > > > > Then I have only one concern, for vmemmap case, if one section doesn't > > > succeed to populate its memmap, do we need to skip all the remaining

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/01/18 at 11:03pm, Pavel Tatashin wrote: > > Ah, yes, I misunderstood it, sorry for that. > > > > Then I have only one concern, for vmemmap case, if one section doesn't > > succeed to populate its memmap, do we need to skip all the remaining > > sections in that node? > > Yes, in

Re: [PATCH RFC tip/core/rcu 1/2] rcu: Defer reporting RCU-preempt quiescent states when disabled

2018-07-01 Thread Paul E. McKenney
On Sun, Jul 01, 2018 at 05:35:53PM -0700, Joel Fernandes wrote: > On Sun, Jul 01, 2018 at 03:27:49PM -0700, Paul E. McKenney wrote: > [...] > > > > +/* > > > > + * Report a deferred quiescent state if needed and safe to do so. > > > > + * As with rcu_preempt_need_deferred_qs(), "safe" involves

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
> > + if (!usemap) { > > + pr_err("%s: usemap allocation failed", __func__); > > Wondering if we can provide more useful information for better debugging > if failed. E.g here tell on what nid the usemap allocation failed. > > > +

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
> Ah, yes, I misunderstood it, sorry for that. > > Then I have only one concern, for vmemmap case, if one section doesn't > succeed to populate its memmap, do we need to skip all the remaining > sections in that node? Yes, in sparse_populate_node() we have the following: 294 for (pnum =

Re: [PATCH RFC tip/core/rcu 1/2] rcu: Defer reporting RCU-preempt quiescent states when disabled

2018-07-01 Thread Paul E. McKenney
On Sun, Jul 01, 2018 at 05:37:32PM -0700, Joel Fernandes wrote: > On Sun, Jul 01, 2018 at 03:25:01PM -0700, Paul E. McKenney wrote: > [...] > > > > @@ -602,6 +589,66 @@ static void rcu_read_unlock_special(struct > > > > task_struct *t) > > > > } > > > > } > > > > > > > > +/* > > > > +

Re: [PATCH v2 5/6] mm: track gup pages with page->dma_pinned_* fields

2018-07-01 Thread kbuild test robot
Hi John, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.18-rc3] [cannot apply to next-20180629] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] f2fs: Replace strncpy with memcpy

2018-07-01 Thread Chao Yu
On 2018/7/2 10:16, Guenter Roeck wrote: > On 07/01/2018 06:53 PM, Chao Yu wrote: >> On 2018/7/2 4:57, Guenter Roeck wrote: >>> gcc 8.1.0 complains: >>> >>> fs/f2fs/namei.c: In function 'f2fs_update_extension_list': >>> fs/f2fs/namei.c:257:3: warning: >>> 'strncpy' output truncated before

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/01/18 at 10:04pm, Pavel Tatashin wrote: > +/* > + * Initialize sparse on a specific node. The node spans [pnum_begin, > pnum_end) > + * And number of present sections in this node is map_count. > + */ > +void __init sparse_init_nid(int nid, unsigned long pnum_begin, > +

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/01/18 at 10:43pm, Pavel Tatashin wrote: > On Sun, Jul 1, 2018 at 10:31 PM Baoquan He wrote: > > > > On 07/01/18 at 10:18pm, Pavel Tatashin wrote: > > > > Here, I think it might be not right to jump to 'failed' directly if one > > > > section of the node failed to populate memmap. I think

Re: [PATCH RESEND 0/3] K2G: mmc: Update mmc dt node to use

2018-07-01 Thread Kishon Vijay Abraham I
On Saturday 30 June 2018 04:29 AM, Santosh Shilimkar wrote: > On 6/27/2018 9:15 PM, Kishon Vijay Abraham I wrote: >> Santosh, >> >> On Friday 22 June 2018 03:46 PM, Kishon Vijay Abraham I wrote: >>> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc >>> binding. >>> >>> I've

[PATCH] x86: make Memory Management options more visible

2018-07-01 Thread Randy Dunlap
From: Randy Dunlap Currently for x86, the "Memory Management" kconfig options are displayed under "Processor type and features." This tends to make them hidden or difficult to find. This patch makes Memory Managment options a first-class menu by moving it away from "Processor type and

Re: [PATCH v2 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

2018-07-01 Thread kbuild test robot
Hi John, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.18-rc3] [cannot apply to next-20180629] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v2] kbuild: verify that $DEPMOD is installed

2018-07-01 Thread Randy Dunlap
From: Randy Dunlap Verify that 'depmod' ($DEPMOD) is installed. This is a partial revert of 620c231c7a7f (from 2012): ("kbuild: do not check for ancient modutils tools") Also update Documentation/process/changes.rst to refer to kmod instead of module-init-tools. Fixes kernel bugzilla

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
On Sun, Jul 1, 2018 at 10:31 PM Baoquan He wrote: > > On 07/01/18 at 10:18pm, Pavel Tatashin wrote: > > > Here, I think it might be not right to jump to 'failed' directly if one > > > section of the node failed to populate memmap. I think the original code > > > is only skipping the section which

Re: [PATCH v1 0/6] perf cs-etm: Fix tracing packet handling and minor refactoring

2018-07-01 Thread leo . yan
Hi Arnaldo, On Tue, Jun 19, 2018 at 03:19:43PM -0300, Arnaldo Carvalho de Melo wrote: > Em Tue, Jun 19, 2018 at 11:46:02AM -0600, Mathieu Poirier escreveu: > > On Sun, 17 Jun 2018 at 23:10, Leo Yan wrote: > > > > > > Due the current code is missing to handle cs-etm start tracing packet > > > and

Re: [PATCH v2 1/3] arm64: dts: actions: Enable clock controller for S700

2018-07-01 Thread Manivannan Sadhasivam
Hi, On Sun, Jul 01, 2018 at 07:50:01PM +0200, Saravanan Sekar wrote: > Hi Mani, > > > On 06/30/18 11:42, Manivannan Sadhasivam wrote: > > On Thu, Jun 28, 2018 at 09:18:03PM +0200, Saravanan Sekar wrote: > > > Added clock management controller for S700 > > > > > > Signed-off-by: Parthiban

Re: [PATCH v5 0/7] add virt-dma support for imx-sdma

2018-07-01 Thread Robin Gong
Hi Vinod, Do you have any comment for this patchset? Lucas and Sascha acked it and tty patch already merged in. On 二, 2018-06-26 at 17:04 +0200, Lucas Stach wrote: > Hi Robin, > > I've tested this whole series with the SDMA being used for SPI, UART > and SSI with no regressions spotted.

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 07/01/18 at 10:18pm, Pavel Tatashin wrote: > > Here, I think it might be not right to jump to 'failed' directly if one > > section of the node failed to populate memmap. I think the original code > > is only skipping the section which memmap failed to populate by marking > > it as not present

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
> Here, I think it might be not right to jump to 'failed' directly if one > section of the node failed to populate memmap. I think the original code > is only skipping the section which memmap failed to populate by marking > it as not present with "ms->section_mem_map = 0". > Hi Baoquan, Thank

Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Robin Gong
On 日, 2018-07-01 at 22:17 -0300, Fabio Estevam wrote: > On Sun, Jul 1, 2018 at 10:09 PM, Anson Huang > wrote: > > > > > On some new i.MX platforms, PFuze switches are used for supplying > > GPU/VPU > > or other non-critical modules only, these switches need to be > > turned off by > > runtime

Re: [PATCH v2 5/6] mm: track gup pages with page->dma_pinned_* fields

2018-07-01 Thread kbuild test robot
Hi John, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.18-rc3] [cannot apply to next-20180629] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

2018-07-01 Thread kbuild test robot
Hi John, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.18-rc3] [cannot apply to next-20180629] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
Hi Pavel, Thanks for your quick fix. You might have missed another comment to v2 patch 1/2 which is at the bottom. On 07/01/18 at 10:04pm, Pavel Tatashin wrote: > +/* > + * Initialize sparse on a specific node. The node spans [pnum_begin, > pnum_end) > + * And number of present sections in this

[PATCH V2] ARM: dts: imx6: correct anatop regulators range

2018-07-01 Thread Anson Huang
According to i.MX6 datasheet, the LDO_1P1's typical programming operating range is 1.0V to 1.2V, and the LDO_2P5's typical programming operating range is 2.25V to 2.75V, correct LDO_1P1 and LDO_2P5's regulator range settings for i.MX6 SoCs. Signed-off-by: Anson Huang --- changes since V1:

[PATCH v3 0/2] sparse_init rewrite

2018-07-01 Thread Pavel Tatashin
Changelog: v3 - v1 - Fixed two issues found by Baoquan He v1 - v2 - Addressed comments from Oscar Salvador In sparse_init() we allocate two large buffers to temporary hold usemap and memmap for the whole machine. However, we can avoid doing that if we changed sparse_init() to

[PATCH v3 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
sparse_init() requires to temporary allocate two large buffers: usemap_map and map_map. Baoquan He has identified that these buffers are so large that Linux is not bootable on small memory machines, such as a kdump boot. The buffers are especially large when CONFIG_X86_5LEVEL is set, as they are

[PATCH v3 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Pavel Tatashin
Change sprase_init() to only find the pnum ranges that belong to a specific node and call sprase_init_nid() for that range from sparse_init(). Delete all the code that became obsolete with this change. Signed-off-by: Pavel Tatashin --- include/linux/mm.h | 5 - mm/sparse-vmemmap.c | 39

Re: [PATCH v3 2/2] iio: adc: Add Spreadtrum SC27XX PMICs ADC support

2018-07-01 Thread Baolin Wang
On 1 July 2018 at 02:00, Jonathan Cameron wrote: > On Mon, 25 Jun 2018 09:47:54 +0800 > Baolin Wang wrote: > >> Hi Jonathan, >> >> On 24 June 2018 at 21:47, Jonathan Cameron >> wrote: >> > On Sun, 24 Jun 2018 14:30:09 +0100 >> > Jonathan Cameron wrote: >> > >> >> On Sun, 24 Jun 2018 17:13:00

Re: [PATCH v2 3/3] dt-bindings: clock: Modify Actions Soc clock bindings

2018-07-01 Thread Manivannan Sadhasivam
Hi Andreas, On Sun, Jul 01, 2018 at 07:58:15PM +0200, Andreas Färber wrote: > Hi, > > Am 01.07.2018 um 19:37 schrieb Manivannan Sadhasivam: > > On Sun, Jul 01, 2018 at 07:26:20PM +0200, Saravanan Sekar wrote: > >> Hi Mani > >> > >> > >> On 06/30/18 11:32, Manivannan Sadhasivam wrote: > >>> Hi

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Pavel Tatashin
> > Yes, if they are equal at 501, 'continue' to for loop. If nid is not > equal to nid_begin, we execute sparse_init_nid(), here should it be that > nid_begin is the current node, nid is next node? Nevermind, I forgot about the continue, I will fix it. Thank you again! Pavel

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Baoquan He
On 07/01/18 at 09:46pm, Pavel Tatashin wrote: > ~~~ > > Here, node id passed to sparse_init_nid() should be 'nid_begin', but not > > 'nid'. When you found out the current section's 'nid' is diferent than > > 'nid_begin', handle node 'nid_begin', then start to next node

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Pavel Tatashin
~~~ > Here, node id passed to sparse_init_nid() should be 'nid_begin', but not > 'nid'. When you found out the current section's 'nid' is diferent than > 'nid_begin', handle node 'nid_begin', then start to next node 'nid'. Thank you for reviewing this work. Here nid

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Pavel Tatashin
On Sun, Jul 1, 2018 at 9:34 PM Baoquan He wrote: > > Hi Pavel, > > On 06/29/18 at 11:09pm, Pavel Tatashin wrote: > > Change sprase_init() to only find the pnum ranges that belong to a specific > > node and call sprase_init_nid() for that range from sparse_init(). > > > > Delete all the code that

Re: [PATCH v2 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Pavel Tatashin
On Sun, Jul 1, 2018 at 9:29 PM Baoquan He wrote: > > On 06/29/18 at 11:09pm, Pavel Tatashin wrote: > > sparse_init() requires to temporary allocate two large buffers: > > usemap_map and map_map. Baoquan He has identified that these buffers are so > > large that Linux is not bootable on small

Re: [PATCH upstream] KASAN: slab-out-of-bounds Read in getname_kernel

2018-07-01 Thread Ian Kent
On Mon, 2018-07-02 at 09:10 +0800, Ian Kent wrote: > On Mon, 2018-07-02 at 00:04 +0200, tomas wrote: > > Hi, > > > > I've looked into this issue found by Syzbot and I made a patch: > > > > https://syzkaller.appspot.com/bug?id=d03abd8b42847f7f69b1d1d7f97208ae425b116 > > 3 > > Umm ... oops! > >

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Baoquan He
On 06/29/18 at 11:09pm, Pavel Tatashin wrote: > Change sprase_init() to only find the pnum ranges that belong to a specific > node and call sprase_init_nid() for that range from sparse_init(). > > Delete all the code that became obsolete with this change. > void __init sparse_init(void) > { > -

Re: [PATCH] arm: dts: socfpga: denali needs nand_x_clk too

2018-07-01 Thread Masahiro Yamada
Hi Dinh, 2018-06-27 23:55 GMT+09:00 Dinh Nguyen : > Hi Masahiro, > > On 06/26/2018 09:52 PM, Masahiro Yamada wrote: >> 2018-06-27 3:09 GMT+09:00 Miquel Raynal : >>> Hi Masahiro, >>> >>> On Tue, 26 Jun 2018 11:38:21 +0900, Masahiro Yamada >>> wrote: >>> 2018-06-25 23:55 GMT+09:00 Boris

Re: [PATCH v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

2018-07-01 Thread Baoquan He
Hi Pavel, On 06/29/18 at 11:09pm, Pavel Tatashin wrote: > Change sprase_init() to only find the pnum ranges that belong to a specific > node and call sprase_init_nid() for that range from sparse_init(). > > Delete all the code that became obsolete with this change. > @@ -617,87 +491,24 @@ void

[PATCH V2] mmc: core: cd_label must be last entry of mmc_gpio struct

2018-07-01 Thread Anson Huang
commit bfd694d5e21c ("mmc: core: Add tunable delay before detecting card after card is inserted") adds "u32 cd_debounce_delay_ms" to the last of mmc_gpio struct and cause "char cd_label[0]" NOT work as string pointer of card detect label, when "cat /proc/interrupts", the devname for card detect

Re: [PATCH v2 1/2] mm/sparse: add sparse_init_nid()

2018-07-01 Thread Baoquan He
On 06/29/18 at 11:09pm, Pavel Tatashin wrote: > sparse_init() requires to temporary allocate two large buffers: > usemap_map and map_map. Baoquan He has identified that these buffers are so > large that Linux is not bootable on small memory machines, such as a kdump > boot. These two temporary

Re: [PATCH] kbuild: check for /sbin/depmod installed

2018-07-01 Thread Masahiro Yamada
2018-07-02 2:12 GMT+09:00 Randy Dunlap : > From: Randy Dunlap > > Verify that 'depmod' ($DEPMOD) is installed. > This is a partial revert of 620c231c7a7f (from 2012): > ("kbuild: do not check for ancient modutils tools") > > Fixes kernel bugzilla #198965: >

RE: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Anson Huang
Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Monday, July 2, 2018 9:17 AM > To: Anson Huang > Cc: Shawn Guo ; Robin Gong ; > Mark Rutland ; open list:OPEN FIRMWARE AND > FLATTENED DEVICE TREE BINDINGS ; > linux-kernel ; Rob

[PATCH] regulator: Revert "regulator: pfuze100: add enable/disable for switch"

2018-07-01 Thread Fabio Estevam
From: Fabio Estevam This reverts commit 5fe156f1cab4f340ddb6283c993912be77594016. Commit 5fe156f1cab4 ("regulator: pfuze100: add enable/disable for switch") causes boot regression on some platforms such as imx6sl-evk and imx6sll-evk. After this commit the SW4 regulator will be turned off and

Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Fabio Estevam
On Sun, Jul 1, 2018 at 10:09 PM, Anson Huang wrote: > On some new i.MX platforms, PFuze switches are used for supplying GPU/VPU > or other non-critical modules only, these switches need to be turned off by > runtime PM to avoid very high power leakage, like on mScale850D. Ok, in this case I

Re: [PATCH V2 01/19] csky: Build infrastructure

2018-07-01 Thread Guo Ren
Hi Randy, On Sun, Jul 01, 2018 at 02:01:52PM -0700, Randy Dunlap wrote: > Hi, > Just a few comments... > Thx for your review. I'll fixup all of you mentioned and self-check again. Guo Ren

[PATCH] lib: rhashtable: Correct self-assignment in rhashtable.c

2018-07-01 Thread Rishabh Bhatnagar
In file lib/rhashtable.c line 777, skip variable is assigned to itself. The following error was observed: lib/rhashtable.c:777:41: warning: explicitly assigning value of variable of type 'int' to itself [-Wself-assign] error, forbidden warning: rhashtable.c:777 This error was found when compiling

Re: [PATCH 2/2] regulator: uniphier: add regulator driver for UniPhier SoC

2018-07-01 Thread Kunihiko Hayashi
Hi Mark, Thank you for your comments. On Fri, 29 Jun 2018 12:03:41 +0100 wrote: > On Fri, Jun 29, 2018 at 05:22:13PM +0900, Kunihiko Hayashi wrote: > > > +++ b/drivers/regulator/uniphier-regulator.c > > @@ -0,0 +1,251 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > +/* > > + * Regulator

Re: [PATCH upstream] KASAN: slab-out-of-bounds Read in getname_kernel

2018-07-01 Thread Ian Kent
On Mon, 2018-07-02 at 00:04 +0200, tomas wrote: > Hi, > > I've looked into this issue found by Syzbot and I made a patch: > > https://syzkaller.appspot.com/bug?id=d03abd8b42847f7f69b1d1d7f97208ae425b1163 Umm ... oops! Thanks for looking into this Tomas. > > > The autofs subsystem does not

Re: [PATCH] kernel/power: cast PAGE_SIZE to int when comparing with error code

2018-07-01 Thread cgxu519
Hi Rafael, Could you have a look at this simple patch? Thanks, Chengguang On 06/25/2018 01:30 PM, Chengguang Xu wrote: If PAGE_SIZE is unsigned type then negative error code will be larger than PAGE_SIZE. Signed-off-by: Chengguang Xu --- kernel/power/swap.c | 4 ++-- 1 file changed, 2

RE: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Anson Huang
Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Monday, July 2, 2018 9:05 AM > To: Anson Huang > Cc: Shawn Guo ; Robin Gong ; > Mark Rutland ; open list:OPEN FIRMWARE AND > FLATTENED DEVICE TREE BINDINGS ; > linux-kernel ; Rob

Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Fabio Estevam
On Sun, Jul 1, 2018 at 10:03 PM, Anson Huang wrote: > So that mean such kind of kernel patch will never be into kernel? Even if it > is a > necessary patch for fixing some other issues? I just wonder how this case > being > handled. What is the issue that 5fe156f1cab4f fixes? It is not clear

RE: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Anson Huang
Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Monday, July 2, 2018 9:00 AM > To: Anson Huang > Cc: Shawn Guo ; Robin Gong ; > Mark Rutland ; open list:OPEN FIRMWARE AND > FLATTENED DEVICE TREE BINDINGS ; > linux-kernel ; Rob

Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Fabio Estevam
Hi Anson, On Sun, Jul 1, 2018 at 9:57 PM, Anson Huang wrote: > Just want to know how to handle such case? The kernel patch will never > be applied or is there any way to make kernel patch and dtb patch applied > together to avoid any breakage? We always want to avoid breaking a working dtb

[PATCH v2 2/6] mm: introduce page->dma_pinned_flags, _count

2018-07-01 Thread john . hubbard
From: John Hubbard Add two struct page fields that, combined, are unioned with struct page->lru. There is no change in the size of struct page. These new fields are for type safety and clarity. Also add page flag accessors to test, set and clear the new page->dma_pinned_flags field. The

[PATCH v2 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

2018-07-01 Thread john . hubbard
From: John Hubbard Add a sync_mode parameter to clear_page_dirty_for_io(), to specify the writeback sync mode, and also pass in the appropriate value (WB_SYNC_NONE or WB_SYNC_ALL), from each filesystem location that calls it. This will be used in subsequent patches, to allow page_mkclean() to

[PATCH v2 6/6] mm: page_mkclean, ttu: handle pinned pages

2018-07-01 Thread john . hubbard
From: John Hubbard Update page_mkclean(), page_mkclean's callers, and try_to_unmap(), so that there is a choice: in some cases, skipped dma-pinned pages. In other cases (sync_mode == WB_SYNC_ALL), wait for those pages to become unpinned. This fixes some problems that came up when using devices

RE: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Anson Huang
Hi, Fabio Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Monday, July 2, 2018 8:55 AM > To: Anson Huang > Cc: Shawn Guo ; Robin Gong ; > Mark Rutland ; open list:OPEN FIRMWARE AND > FLATTENED DEVICE TREE BINDINGS ; >

[PATCH v2 3/6] mm: introduce zone_gup_lock, for dma-pinned pages

2018-07-01 Thread john . hubbard
From: John Hubbard The page->dma_pinned_flags and _count fields require lock protection. A lock at approximately the granularity of the zone_lru_lock is called for, but adding to the locking contention of zone_lru_lock is undesirable, because that is a pre-existing hot spot. Fortunately, these

[PATCH v2 5/6] mm: track gup pages with page->dma_pinned_* fields

2018-07-01 Thread john . hubbard
From: John Hubbard This patch sets and restores the new page->dma_pinned_flags and page->dma_pinned_count fields, but does not actually use them for anything yet. In order to use these fields at all, the page must be removed from any LRU list that it's on. The patch also adds some precautions

[PATCH v2 1/6] mm: get_user_pages: consolidate error handling

2018-07-01 Thread john . hubbard
From: John Hubbard An upcoming patch requires a way to operate on each page that any of the get_user_pages_*() variants returns. In preparation for that, consolidate the error handling for __get_user_pages(). This provides a single location (the "out:" label) for operating on the collected set

[PATCH v2 0/6] mm/fs: gup: don't unmap or drop filesystem buffers

2018-07-01 Thread john . hubbard
From: John Hubbard This fixes a few problems that came up when using devices (NICs, GPUs, for example) that want to have direct access to a chunk of system (CPU) memory, so that they can DMA to/from that memory. Problems [1] come up if that memory is backed by persistence storage; for example,

Re: [PATCH v1] ARM: dts: imx6sl-evk: keep sw4 always on

2018-07-01 Thread Fabio Estevam
Hi Anson, On Sun, Jul 1, 2018 at 9:53 PM, Anson Huang wrote: > Yes, I think we can revert it to avoid breakage. Didn't notice that some > i.MX platform do NOT have those critical switches always-on. Ok, thanks for confirming. I will send a revert patch then. Thanks

RE: [PATCH V3] ARM: dts: imx6sll-evk: make pfuze100 sw4 always on

2018-07-01 Thread Anson Huang
Hi, Shawn Anson Huang Best Regards! > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Sunday, July 1, 2018 9:33 PM > To: Anson Huang > Cc: s.ha...@pengutronix.de; ker...@pengutronix.de; Fabio Estevam > ; robh...@kernel.org; mark.rutl...@arm.com; >

  1   2   3   4   5   6   7   8   9   >