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,
> > swap: Swa
> > There's
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,
> > swap: Swa
> > There's
On Thu, 28 Jun 2018 at 21:03, Luis R. Rodriguez wrote:
>
> On Thu, Jun 28, 2018 at 05:45:14PM +0200, Vincent Guittot wrote:
> > /proc/sys/kernel/sched_time_avg_ms entry is not used anywhere.
> > Remove it
> >
> > Cc: Ingo Molnar
> > Cc: Peter Zijlstra
> > Cc: Kees Cook
> > Cc: "Luis R.
On Thu, 28 Jun 2018 at 21:03, Luis R. Rodriguez wrote:
>
> On Thu, Jun 28, 2018 at 05:45:14PM +0200, Vincent Guittot wrote:
> > /proc/sys/kernel/sched_time_avg_ms entry is not used anywhere.
> > Remove it
> >
> > Cc: Ingo Molnar
> > Cc: Peter Zijlstra
> > Cc: Kees Cook
> > Cc: "Luis R.
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e0dd1440
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e0dd1440
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
On Fri, Jun 29, 2018 at 03:18:18AM +0530, Himanshu Jha wrote:
> On Thu, Jun 28, 2018 at 03:13:32PM +0300, Stefan Popa wrote:
> > The AD5758 is a single channel DAC with 16-bit precision which uses the
> > SPI interface that operates at clock rates up to 50MHz.
> >
> > The output can be configured
On Fri, Jun 29, 2018 at 03:18:18AM +0530, Himanshu Jha wrote:
> On Thu, Jun 28, 2018 at 03:13:32PM +0300, Stefan Popa wrote:
> > The AD5758 is a single channel DAC with 16-bit precision which uses the
> > SPI interface that operates at clock rates up to 50MHz.
> >
> > The output can be configured
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1759737f80
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109168df80
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109168df80
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
Hello,
syzbot found the following crash on:
HEAD commit:90368a37fbbe Merge tag 'printk-for-4.18-rc3' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1759737f80
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
Hi all,
On Wed, 20 Jun 2018 13:54:58 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> lib/percpu_ida.c
>
> between commit:
>
> acf3ff616ee2 ("scsi: Remove percpu_ida")
>
> from the scsi tree and commit:
>
> 0c4d6e08c775
Hi all,
On Wed, 20 Jun 2018 13:54:58 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> lib/percpu_ida.c
>
> between commit:
>
> acf3ff616ee2 ("scsi: Remove percpu_ida")
>
> from the scsi tree and commit:
>
> 0c4d6e08c775
On June 29, 2018 6:44:39 AM GMT+02:00, Manivannan Sadhasivam
wrote:
>Hi Peter,
>
>On Fri, Jun 29, 2018 at 06:13:31AM +0200, Peter Rosin wrote:
>> Hi!
>>
>> I don't know for sure, but over here the arch/arm64/boot/dts/actions
>folder has no pinctrl nodes at all (v4.18-rc2). So, what is this
On June 29, 2018 6:44:39 AM GMT+02:00, Manivannan Sadhasivam
wrote:
>Hi Peter,
>
>On Fri, Jun 29, 2018 at 06:13:31AM +0200, Peter Rosin wrote:
>> Hi!
>>
>> I don't know for sure, but over here the arch/arm64/boot/dts/actions
>folder has no pinctrl nodes at all (v4.18-rc2). So, what is this
On 06/29/2018 01:55 AM, Karim Eshapa wrote:
> Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
> as GFP_KERNEL may sleep according to slab allocator.
This is a threaded interrupt. Sleeping is OK.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/staging/iio/adc/ad7280a.c | 2 +-
> 1 file
On 06/29/2018 01:55 AM, Karim Eshapa wrote:
> Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
> as GFP_KERNEL may sleep according to slab allocator.
This is a threaded interrupt. Sleeping is OK.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/staging/iio/adc/ad7280a.c | 2 +-
> 1 file
This patch implements the 'pattern_set', 'pattern_get' and 'pattern_clear'
interfaces to support SC27XX LED breathing mode.
Signed-off-by: Baolin Wang
---
Changes from v2:
- No updates.
Changes from v1:
- No updates.
---
drivers/leds/leds-sc27xx-bltc.c | 160
From: Bjorn Andersson
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class drivers can implement
if they support such functionality as well as a new device
This patch implements the 'pattern_set', 'pattern_get' and 'pattern_clear'
interfaces to support SC27XX LED breathing mode.
Signed-off-by: Baolin Wang
---
Changes from v2:
- No updates.
Changes from v1:
- No updates.
---
drivers/leds/leds-sc27xx-bltc.c | 160
From: Bjorn Andersson
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class drivers can implement
if they support such functionality as well as a new device
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in:
drivers/staging/typec/Kconfig
between commit:
e16711c32bca ("staging/typec: fix tcpci_rt1711h build errors")
from the usb.current tree and commit:
990da41530b3 ("staging: typec: tcpci: move tcpci drivers out of
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in:
drivers/staging/typec/Kconfig
between commit:
e16711c32bca ("staging/typec: fix tcpci_rt1711h build errors")
from the usb.current tree and commit:
990da41530b3 ("staging: typec: tcpci: move tcpci drivers out of
On June 28, 2018 8:10:41 PM GMT+02:00, Manivannan Sadhasivam
wrote:
>Add Actions Semi OWL family S900 I2C driver.
>
>Signed-off-by: Manivannan Sadhasivam
>---
> drivers/i2c/busses/Kconfig | 7 +
> drivers/i2c/busses/Makefile | 1 +
> drivers/i2c/busses/i2c-owl.c | 471
On June 28, 2018 8:10:41 PM GMT+02:00, Manivannan Sadhasivam
wrote:
>Add Actions Semi OWL family S900 I2C driver.
>
>Signed-off-by: Manivannan Sadhasivam
>---
> drivers/i2c/busses/Kconfig | 7 +
> drivers/i2c/busses/Makefile | 1 +
> drivers/i2c/busses/i2c-owl.c | 471
Hi Peter,
On Fri, Jun 29, 2018 at 06:13:31AM +0200, Peter Rosin wrote:
> On June 28, 2018 8:10:36 PM GMT+02:00, Manivannan Sadhasivam
> wrote:
> >This patchset adds I2C controller support for Actions Semi S900 SoC.
> >This driver has been structured in a way such that there will be only
> >one
Hi Peter,
On Fri, Jun 29, 2018 at 06:13:31AM +0200, Peter Rosin wrote:
> On June 28, 2018 8:10:36 PM GMT+02:00, Manivannan Sadhasivam
> wrote:
> >This patchset adds I2C controller support for Actions Semi S900 SoC.
> >This driver has been structured in a way such that there will be only
> >one
On Thu, Jun 28, 2018 at 06:24:59PM -0500, Steve French wrote:
> On Thu, Jun 28, 2018 at 6:21 PM ronnie sahlberg
> wrote:
> >
> > On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
> > wrote:
> > > On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> > >> Ronnie
On Thu, Jun 28, 2018 at 06:24:59PM -0500, Steve French wrote:
> On Thu, Jun 28, 2018 at 6:21 PM ronnie sahlberg
> wrote:
> >
> > On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
> > wrote:
> > > On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> > >> Ronnie
On Thu, Jun 28, 2018 at 03:06:46PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 05:38:33AM -0700, Paul E. McKenney wrote:
> > Please let me try again.
> >
> > The approach you are suggesting, clever though it is, disables a check
>
>
>
On Thu, Jun 28, 2018 at 03:06:46PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 05:38:33AM -0700, Paul E. McKenney wrote:
> > Please let me try again.
> >
> > The approach you are suggesting, clever though it is, disables a check
>
>
>
On Tue, Jun 26, 2018 at 6:21 AM, Thomas Gleixner wrote:
> The posix timer ti_overrun handling is broken because the forwarding
> functions can return a huge number of overruns which does not fit in an
> int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can turn
> into random
On Tue, Jun 26, 2018 at 6:21 AM, Thomas Gleixner wrote:
> The posix timer ti_overrun handling is broken because the forwarding
> functions can return a huge number of overruns which does not fit in an
> int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can turn
> into random
On Tue, Jun 26, 2018 at 6:21 AM, Thomas Gleixner wrote:
> The posix timer overrun handling is broken because the forwarding functions
> can return a huge number of overruns which does not fit in an int. As a
> consequence timer_getoverrun(2) and siginfo::si_overrun can turn into
> random number
On Tue, Jun 26, 2018 at 6:21 AM, Thomas Gleixner wrote:
> The posix timer overrun handling is broken because the forwarding functions
> can return a huge number of overruns which does not fit in an int. As a
> consequence timer_getoverrun(2) and siginfo::si_overrun can turn into
> random number
Hi Linus,
> -Original Message-
> From: Linus Walleij [mailto:linus.wall...@linaro.org]
> Sent: Thursday, June 28, 2018 11:44 PM
> To: Naga Sureshkumar Relli
> Cc: Boris Brezillon ; Richard Weinberger
> ;
> David Woodhouse ; Brian Norris
> ; Mark Vasut ; Florian
> Fainelli
> ; Markus
Hi Linus,
> -Original Message-
> From: Linus Walleij [mailto:linus.wall...@linaro.org]
> Sent: Thursday, June 28, 2018 11:44 PM
> To: Naga Sureshkumar Relli
> Cc: Boris Brezillon ; Richard Weinberger
> ;
> David Woodhouse ; Brian Norris
> ; Mark Vasut ; Florian
> Fainelli
> ; Markus
On Thu, 28 Jun 2018, Christoph Hellwig wrote:
> On Mon, Jun 25, 2018 at 09:46:11PM +1000, Finn Thain wrote:
> > A 32-bit mask is used by default because a NuBus slot has 32
> > address/data lines and a NuBus board is free to use all of them.
>
> Looks good:
Thanks for looking it over. But did
On Thu, 28 Jun 2018, Christoph Hellwig wrote:
> On Mon, Jun 25, 2018 at 09:46:11PM +1000, Finn Thain wrote:
> > A 32-bit mask is used by default because a NuBus slot has 32
> > address/data lines and a NuBus board is free to use all of them.
>
> Looks good:
Thanks for looking it over. But did
On June 28, 2018 8:10:36 PM GMT+02:00, Manivannan Sadhasivam
wrote:
>This patchset adds I2C controller support for Actions Semi S900 SoC.
>This driver has been structured in a way such that there will be only
>one controller driver for the whole OWL family series (S500, S700 and
>S900 SoCs).
>
On June 28, 2018 8:10:36 PM GMT+02:00, Manivannan Sadhasivam
wrote:
>This patchset adds I2C controller support for Actions Semi S900 SoC.
>This driver has been structured in a way such that there will be only
>one controller driver for the whole OWL family series (S500, S700 and
>S900 SoCs).
>
On 2018/6/29 11:35, Randy Dunlap wrote:
> On 06/28/2018 08:33 PM, YueHaibing wrote:
>> Signed-off-by: YueHaibing
>> ---
>> lib/string.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hi,
>
> This isn't a typo. "iff" means "if and only if".
ok, my poor english, thank you.
>
On 2018/6/29 11:35, Randy Dunlap wrote:
> On 06/28/2018 08:33 PM, YueHaibing wrote:
>> Signed-off-by: YueHaibing
>> ---
>> lib/string.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hi,
>
> This isn't a typo. "iff" means "if and only if".
ok, my poor english, thank you.
>
On 06/28/2018 08:33 PM, YueHaibing wrote:
> Signed-off-by: YueHaibing
> ---
> lib/string.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hi,
This isn't a typo. "iff" means "if and only if".
> diff --git a/lib/string.c b/lib/string.c
> index 2c0900a..23ed944 100644
> ---
On 06/28/2018 08:33 PM, YueHaibing wrote:
> Signed-off-by: YueHaibing
> ---
> lib/string.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hi,
This isn't a typo. "iff" means "if and only if".
> diff --git a/lib/string.c b/lib/string.c
> index 2c0900a..23ed944 100644
> ---
Some i.MX SoCs have GPIO clock gate in CCM, accessing
GPIO registers needs to enable GPIO clock gate first,
i.MX GPIO driver will enable clock gate if there is
clock property in GPIO node of dtb, add optional property
to i.MX GPIO binding doc.
Signed-off-by: Anson Huang
---
Some i.MX SoCs have GPIO clock gate in CCM, accessing
GPIO registers needs to enable GPIO clock gate first,
i.MX GPIO driver will enable clock gate if there is
clock property in GPIO node of dtb, add optional property
to i.MX GPIO binding doc.
Signed-off-by: Anson Huang
---
Signed-off-by: YueHaibing
---
lib/string.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/string.c b/lib/string.c
index 2c0900a..23ed944 100644
--- a/lib/string.c
+++ b/lib/string.c
@@ -609,7 +609,7 @@ EXPORT_SYMBOL(strsep);
* @s1: one string
* @s2: another string
Signed-off-by: YueHaibing
---
lib/string.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/string.c b/lib/string.c
index 2c0900a..23ed944 100644
--- a/lib/string.c
+++ b/lib/string.c
@@ -609,7 +609,7 @@ EXPORT_SYMBOL(strsep);
* @s1: one string
* @s2: another string
For devices with a class, we create a "glue" directory between
the parent device and the new device with the class name.
This directory is never "explicitely" removed when empty however,
this is left to the implicit sysfs removal done by kobjects when
they are released on the last kobject_put().
For devices with a class, we create a "glue" directory between
the parent device and the new device with the class name.
This directory is never "explicitely" removed when empty however,
this is left to the implicit sysfs removal done by kobjects when
they are released on the last kobject_put().
On Fri, Jun 29, 2018 at 07:22:22AM +0900, Akira Yokosawa wrote:
> On 2018/06/28 08:21:40 -0700, Paul E. McKenney wrote:
> [...]
> >
> > While I am at it, here is the current scorecard:
> >
> > e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy
> > atomicity
> > c21fcc6594f1
On Fri, Jun 29, 2018 at 07:22:22AM +0900, Akira Yokosawa wrote:
> On 2018/06/28 08:21:40 -0700, Paul E. McKenney wrote:
> [...]
> >
> > While I am at it, here is the current scorecard:
> >
> > e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy
> > atomicity
> > c21fcc6594f1
On 06/28/2018 04:50 PM, Ray Jui wrote:
Hi Guenter/Florian,
On 6/27/2018 11:55 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:47:21AM -0700, Ray Jui wrote:
On 6/27/2018 11:42 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:38:48AM -0700, Ray Jui wrote:
On 6/27/2018 11:33 AM,
On 06/28/2018 04:50 PM, Ray Jui wrote:
Hi Guenter/Florian,
On 6/27/2018 11:55 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:47:21AM -0700, Ray Jui wrote:
On 6/27/2018 11:42 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:38:48AM -0700, Ray Jui wrote:
On 6/27/2018 11:33 AM,
On Mon, May 28, 2018 at 11:01:33AM -0700, Ray Jui wrote:
> Update the SP805 binding document to add optional 'timeout-sec'
> devicetree property
>
> Signed-off-by: Ray Jui
> Reviewed-by: Rob Herring
Reviewed-by: Guenter Roeck
> ---
> Documentation/devicetree/bindings/watchdog/arm,sp805.txt
On Mon, May 28, 2018 at 11:01:33AM -0700, Ray Jui wrote:
> Update the SP805 binding document to add optional 'timeout-sec'
> devicetree property
>
> Signed-off-by: Ray Jui
> Reviewed-by: Rob Herring
Reviewed-by: Guenter Roeck
> ---
> Documentation/devicetree/bindings/watchdog/arm,sp805.txt
On Mon, May 28, 2018 at 11:01:32AM -0700, Ray Jui wrote:
> Consolidate two SP805 binding documents "arm,sp805.txt" and
> "sp805-wdt.txt" into "arm,sp805.txt" that matches the naming of the
> desired compatible string to be used
>
> Signed-off-by: Ray Jui
> Reviewed-by: Rob Herring
For the
On Mon, May 28, 2018 at 11:01:32AM -0700, Ray Jui wrote:
> Consolidate two SP805 binding documents "arm,sp805.txt" and
> "sp805-wdt.txt" into "arm,sp805.txt" that matches the naming of the
> desired compatible string to be used
>
> Signed-off-by: Ray Jui
> Reviewed-by: Rob Herring
For the
iled against -next.
This currently does not compile correctly
against next-20180628
---
$ make drivers/staging/gasket/
CALLscripts/checksyscalls.sh
DESCEND objtool
CC drivers/staging/gasket/gasket_core.o
drivers/staging/gasket/gasket_core.c: In function ‘gasket_mm_unmap_region’:
driv
iled against -next.
This currently does not compile correctly
against next-20180628
---
$ make drivers/staging/gasket/
CALLscripts/checksyscalls.sh
DESCEND objtool
CC drivers/staging/gasket/gasket_core.o
drivers/staging/gasket/gasket_core.c: In function ‘gasket_mm_unmap_region’:
driv
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. in early_pfn_valid(), if pfn and
pfn+1 are in the same memblock region, we can record the last returned
memblock
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. if pfn and pfn+1 are in the same
memblock region, we can simply pfn++ instead of doing the binary search
in
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. in early_pfn_valid(), if pfn and
pfn+1 are in the same memblock region, we can record the last returned
memblock
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. if pfn and pfn+1 are in the same
memblock region, we can simply pfn++ instead of doing the binary search
in
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But it causes
possible panic bug. So Daniel Vacek reverted it later.
But as suggested by Daniel Vacek, it is fine to using memblock to skip
gaps and finding next
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. in early_pfn_valid(), we can record
the last returned memblock region. If current pfn and last pfn are in the
same
This helper is to find the memory region index of input pfn.
Signed-off-by: Jia He
---
include/linux/memblock.h | 2 ++
mm/memblock.c| 9 +
2 files changed, 11 insertions(+)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index ca59883..b0f0307 100644
---
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But it causes
possible panic bug. So Daniel Vacek reverted it later.
But as suggested by Daniel Vacek, it is fine to using memblock to skip
gaps and finding next
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But there is
still some room for improvement. E.g. in early_pfn_valid(), we can record
the last returned memblock region. If current pfn and last pfn are in the
same
This helper is to find the memory region index of input pfn.
Signed-off-by: Jia He
---
include/linux/memblock.h | 2 ++
mm/memblock.c| 9 +
2 files changed, 11 insertions(+)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index ca59883..b0f0307 100644
---
Make CONFIG_HAVE_MEMBLOCK_PFN_VALID a new config option so it can move
memblock_next_valid_pfn to generic code file. All the latter optimizations
are based on this config.
The memblock initialization time on arm/arm64 can benefit from this.
Signed-off-by: Jia He
---
arch/arm/Kconfig | 4
Make CONFIG_HAVE_MEMBLOCK_PFN_VALID a new config option so it can move
memblock_next_valid_pfn to generic code file. All the latter optimizations
are based on this config.
The memblock initialization time on arm/arm64 can benefit from this.
Signed-off-by: Jia He
---
arch/arm/Kconfig | 4
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") tried to optimize the loop in memmap_init_zone(). But
there is still some room for improvement.
Patch 1 introduce new config to make codes more generic
Patch 2 remain the memblock_next_valid_pfn on arm and
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") tried to optimize the loop in memmap_init_zone(). But
there is still some room for improvement.
Patch 1 introduce new config to make codes more generic
Patch 2 remain the memblock_next_valid_pfn on arm and
Under some circumstances (such as when using kobject debugging)
a gluedir whose kref is 0 might remain in the class kset for
a long time. The reason is that we don't actively remove glue
dirs when they become empty, but instead rely on the implicit
removal done by kobject_release(), which can
Under some circumstances (such as when using kobject debugging)
a gluedir whose kref is 0 might remain in the class kset for
a long time. The reason is that we don't actively remove glue
dirs when they become empty, but instead rely on the implicit
removal done by kobject_release(), which can
We use usual inode size, it is 256 bytes.
Yes, this commit is in my repository.
But there is a bug in this patch.
Let me show you,
Here is the bug: " return ALIGN(inodes, (info.block_size / info.inode_size));"
In my reproduce,
info.block_size = 1024, (it is legal)
info.inode_size =256,
the
We use usual inode size, it is 256 bytes.
Yes, this commit is in my repository.
But there is a bug in this patch.
Let me show you,
Here is the bug: " return ALIGN(inodes, (info.block_size / info.inode_size));"
In my reproduce,
info.block_size = 1024, (it is legal)
info.inode_size =256,
the
On (06/28/18 12:54), Petr Mladek wrote:
>
> On Thu 2018-06-28 11:39:02, Sergey Senozhatsky wrote:
> > On (06/27/18 16:08), Petr Mladek wrote:
> > >
> > > kernel/printk/printk.c | 57
> > > +++-
> > > kernel/printk/printk_safe.c | 58
> > >
On (06/28/18 12:54), Petr Mladek wrote:
>
> On Thu 2018-06-28 11:39:02, Sergey Senozhatsky wrote:
> > On (06/27/18 16:08), Petr Mladek wrote:
> > >
> > > kernel/printk/printk.c | 57
> > > +++-
> > > kernel/printk/printk_safe.c | 58
> > >
On (06/28/18 11:41), Petr Mladek wrote:
> >
> > A side note: This nesting also handles recursive printk-s for us.
> >
> > NMI:
> > printk_nmi_enter
> > ftrace_dump
> > printk_nmi_direct_enter
> > vprintk_func
> >spin_lock(logbuf_lock)
> > vprintk_store
> >
On (06/28/18 11:41), Petr Mladek wrote:
> >
> > A side note: This nesting also handles recursive printk-s for us.
> >
> > NMI:
> > printk_nmi_enter
> > ftrace_dump
> > printk_nmi_direct_enter
> > vprintk_func
> >spin_lock(logbuf_lock)
> > vprintk_store
> >
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
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
Matthew Wilcox writes:
> On Wed, Jun 27, 2018 at 11:18:39PM -0700, Andrew Morton wrote:
>> On Thu, 28 Jun 2018 13:35:15 +0800 "Huang\, Ying"
>> wrote:
>> > No problem. I will rebase the patchset on your latest -mm tree, or the
>> > next version to be released?
>>
>> We need to figure that
Matthew Wilcox writes:
> On Wed, Jun 27, 2018 at 11:18:39PM -0700, Andrew Morton wrote:
>> On Thu, 28 Jun 2018 13:35:15 +0800 "Huang\, Ying"
>> wrote:
>> > No problem. I will rebase the patchset on your latest -mm tree, or the
>> > next version to be released?
>>
>> We need to figure that
> On Jun 28, 2018, at 5:18 PM, Linus Torvalds
> wrote:
>
>> On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>>
>> The idea is that, if someone screws up and sticks a number like
>> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
>> (when they actually mean
> On Jun 28, 2018, at 5:18 PM, Linus Torvalds
> wrote:
>
>> On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>>
>> The idea is that, if someone screws up and sticks a number like
>> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
>> (when they actually mean
On 6/28/18 12:10 PM, Yang Shi wrote:
On 6/28/18 4:51 AM, Michal Hocko wrote:
On Wed 27-06-18 10:23:39, Yang Shi wrote:
On 6/27/18 12:24 AM, Michal Hocko wrote:
On Tue 26-06-18 18:03:34, Yang Shi wrote:
On 6/26/18 12:43 AM, Peter Zijlstra wrote:
On Mon, Jun 25, 2018 at 05:06:23PM
On 6/28/18 12:10 PM, Yang Shi wrote:
On 6/28/18 4:51 AM, Michal Hocko wrote:
On Wed 27-06-18 10:23:39, Yang Shi wrote:
On 6/27/18 12:24 AM, Michal Hocko wrote:
On Tue 26-06-18 18:03:34, Yang Shi wrote:
On 6/26/18 12:43 AM, Peter Zijlstra wrote:
On Mon, Jun 25, 2018 at 05:06:23PM
- On Jun 28, 2018, at 8:18 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>>
>> The idea is that, if someone screws up and sticks a number like
>> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
>> (when
- On Jun 28, 2018, at 8:18 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>>
>> The idea is that, if someone screws up and sticks a number like
>> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
>> (when
On Thu, Jun 28, 2018 at 6:35 AM Fabio Estevam wrote:
>
> Hi Andrey,
>
> On Thu, Jun 28, 2018 at 1:37 AM, Andrey Smirnov
> wrote:
> > There's already a USB PHY with reg of zero on that bus - usbphy0, used
> > by usbotg (included from imx51.dtsi). Move usbh1phy to @1 avoid
> > address collision.
>
On Thu, Jun 28, 2018 at 6:35 AM Fabio Estevam wrote:
>
> Hi Andrey,
>
> On Thu, Jun 28, 2018 at 1:37 AM, Andrey Smirnov
> wrote:
> > There's already a USB PHY with reg of zero on that bus - usbphy0, used
> > by usbotg (included from imx51.dtsi). Move usbh1phy to @1 avoid
> > address collision.
>
On 6/27/2018 1:18 PM, Richard Weinberger wrote:
Am Mittwoch, 27. Juni 2018, 15:12:48 CEST schrieb Michal Hocko:
On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
wrote:
Is there a way for a user process to mark memory as 'sensitive' or
On 6/27/2018 1:18 PM, Richard Weinberger wrote:
Am Mittwoch, 27. Juni 2018, 15:12:48 CEST schrieb Michal Hocko:
On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
wrote:
Is there a way for a user process to mark memory as 'sensitive' or
Hi,
I stumbled across this patch since I'm currently poking around with
early thermal bringup on a platform and this patch has been integrated
in our development tree.
I'm seeing some unexpected behaviors, which could entirely due to
wrong expectation from my side. I only have some basic working
Hi,
I stumbled across this patch since I'm currently poking around with
early thermal bringup on a platform and this patch has been integrated
in our development tree.
I'm seeing some unexpected behaviors, which could entirely due to
wrong expectation from my side. I only have some basic working
1 - 100 of 1130 matches
Mail list logo
