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

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 v3 1/2] mm/sparse: add sparse_init_nid()

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

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 v1 0/6] perf cs-etm: Fix tracing packet handling and minor refactoring

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

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 v2 1/3] arm64: dts: actions: Enable clock controller for S700

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

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 v5 0/7] add virt-dma support for imx-sdma

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

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

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

> 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 v3 1/2] mm/sparse: add sparse_init_nid()

> 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

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 v1] ARM: dts: imx6sl-evk: keep sw4 always on

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

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

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 v2 5/6] mm: track gup pages with page->dma_pinned_* fields

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

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

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

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

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

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 V2] ARM: dts: imx6: correct anatop regulators range

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

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

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

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

[PATCH v3 0/2] sparse_init rewrite

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

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

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

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 v3 2/2] iio: adc: Add Spreadtrum SC27XX PMICs ADC support

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

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 3/3] dt-bindings: clock: Modify Actions Soc clock bindings

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

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

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

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

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

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

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

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 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

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

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 v2 1/2] mm/sparse: add sparse_init_nid()

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

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 upstream] KASAN: slab-out-of-bounds Read in getname_kernel

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

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 v2 2/2] mm/sparse: start using sparse_init_nid(), and remove old code

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

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] arm: dts: socfpga: denali needs nand_x_clk too

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

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

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

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

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

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

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

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 v2 1/2] mm/sparse: add sparse_init_nid()

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-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] kbuild: check for /sbin/depmod installed

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

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

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

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"

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

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

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

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 v1] ARM: dts: imx6sl-evk: keep sw4 always on

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

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

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

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

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

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

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

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

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

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 2/2] regulator: uniphier: add regulator driver for UniPhier SoC

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

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

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

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

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

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

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

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

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

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

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

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

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 2/6] mm: introduce page->dma_pinned_flags, _count

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

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 4/6] mm/fs: add a sync_mode param for clear_page_dirty_for_io()

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

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

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

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

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

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

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

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

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

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

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

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

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

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,

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

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

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

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

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

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

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