On Fri, Jun 22, 2018 at 02:32:34PM +0800, Anson Huang wrote:
> i.MX6SLL has GPIO clock gates in CCM CCGR, add
> clock property for GPIO driver to make sure all
> GPIO banks work as expected.
>
> Signed-off-by: Anson Huang
I tried to create a topic branch for this patch with dependent clk
branch
On Fri, Jun 22, 2018 at 02:32:34PM +0800, Anson Huang wrote:
> i.MX6SLL has GPIO clock gates in CCM CCGR, add
> clock property for GPIO driver to make sure all
> GPIO banks work as expected.
>
> Signed-off-by: Anson Huang
I tried to create a topic branch for this patch with dependent clk
branch
Hi Rob
On 07/12/18 03:45, Rob Herring wrote:
> On Tue, Jul 10, 2018 at 04:36:57PM +, Yixun Lan wrote:
>> Add two clock bindings IDs which provided by the MMC clock controller,
>> These two clocks will be used by MMC or NAND driver.
>
> I count 3 ids.
I will update this
>
>>
>>
Hi Rob
On 07/12/18 03:45, Rob Herring wrote:
> On Tue, Jul 10, 2018 at 04:36:57PM +, Yixun Lan wrote:
>> Add two clock bindings IDs which provided by the MMC clock controller,
>> These two clocks will be used by MMC or NAND driver.
>
> I count 3 ids.
I will update this
>
>>
>>
Hi Rob
see my comments
On 07/12/18 03:43, Rob Herring wrote:
> On Tue, Jul 10, 2018 at 04:36:56PM +, Yixun Lan wrote:
>> Document the MMC sub clock controller driver, the potential consumer
>> of this driver is MMC or NAND.
>
> So you all have decided to properly model this now?
>
Yes, ;-)
Hi Rob
see my comments
On 07/12/18 03:43, Rob Herring wrote:
> On Tue, Jul 10, 2018 at 04:36:56PM +, Yixun Lan wrote:
>> Document the MMC sub clock controller driver, the potential consumer
>> of this driver is MMC or NAND.
>
> So you all have decided to properly model this now?
>
Yes, ;-)
On Wed, Jul 11, 2018 at 09:22:37PM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 13:56:39 -0700
> Joel Fernandes wrote:
>
> > > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args)
> > > > \
> > > > extern struct tracepoint __tracepoint_##name;
On Wed, Jul 11, 2018 at 09:22:37PM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 13:56:39 -0700
> Joel Fernandes wrote:
>
> > > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args)
> > > > \
> > > > extern struct tracepoint __tracepoint_##name;
>MyungJo, I am trying to understand the relationship of PM QOS with
>devfreq drivers. I don't see any relation of PM QOS api's with devfreq drivers
>directly as there are no QOS apis used in the devfreq framework.
>
>The only explanation I have is that PM QOS has direct relationship
>with CPUFREQ
>MyungJo, I am trying to understand the relationship of PM QOS with
>devfreq drivers. I don't see any relation of PM QOS api's with devfreq drivers
>directly as there are no QOS apis used in the devfreq framework.
>
>The only explanation I have is that PM QOS has direct relationship
>with CPUFREQ
Add DT code to explicitly configure PAD_AUD3_BB_CK and avoid relying
on defaults.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Cc:
It looks like I made a nasty typo in the original patch which resulted
in missing watchdog device. Fix it.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc:
Add DT code to explicitly configure PAD_AUD3_BB_CK and avoid relying
on defaults.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Cc:
It looks like I made a nasty typo in the original patch which resulted
in missing watchdog device. Fix it.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc:
Shawn:
Here's a couple of fixes for things I missed in the
[original-submission]. Sorry about the inconvenience.
Thanks,
Andrey Smirnov
[original-submission]
lkml.kernel.org/r/20180711050704.11492-1-andrew.smir...@gmail.com
Andrey Smirnov (2):
ARM: dts: imx51-zii-scu3-esb: Add switch IRQ
Shawn:
Here's a couple of fixes for things I missed in the
[original-submission]. Sorry about the inconvenience.
Thanks,
Andrey Smirnov
[original-submission]
lkml.kernel.org/r/20180711050704.11492-1-andrew.smir...@gmail.com
Andrey Smirnov (2):
ARM: dts: imx51-zii-scu3-esb: Add switch IRQ
On Wed, Jul 11, 2018 at 02:53:22PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > - rcu_read_lock_sched_notrace(); \
> > - it_func_ptr = rcu_dereference_sched((tp)->funcs); \
> > +
On Fri, Jul 6, 2018 at 12:25 PM Thomas Gleixner wrote:
>
> The kvmclock parameter is init data and the other variables are not
> modified after init.
LGTM:
Reviewed-by: Pavel Tatashin
On Wed, Jul 11, 2018 at 02:53:22PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > - rcu_read_lock_sched_notrace(); \
> > - it_func_ptr = rcu_dereference_sched((tp)->funcs); \
> > +
On Fri, Jul 6, 2018 at 12:25 PM Thomas Gleixner wrote:
>
> The kvmclock parameter is init data and the other variables are not
> modified after init.
LGTM:
Reviewed-by: Pavel Tatashin
Hi,
On 12 July 2018 at 03:37, Stephen Rothwell wrote:
> Hi all,
>
> It looks like part of the xfs tree (the iomap-4.19-merge branch) that
> was merge into the gfs2 tree has been rebased and the gfs2 tree has not
> been updated to cope. The rebase commits are exactly the same patches
> (though I
Hi,
On 12 July 2018 at 03:37, Stephen Rothwell wrote:
> Hi all,
>
> It looks like part of the xfs tree (the iomap-4.19-merge branch) that
> was merge into the gfs2 tree has been rebased and the gfs2 tree has not
> been updated to cope. The rebase commits are exactly the same patches
> (though I
On 07/11/2018 08:50 AM, Arnd Bergmann wrote:
> Another driver turned up that is missing linux/mod_devicetable.h after
> the device IDs are split out from linux/platform_device.h:
>
> drivers/extcon/extcon-max3355.c:127:34: error: array type has incomplete
> element type 'struct of_device_id'
>
On 07/11/2018 08:50 AM, Arnd Bergmann wrote:
> Another driver turned up that is missing linux/mod_devicetable.h after
> the device IDs are split out from linux/platform_device.h:
>
> drivers/extcon/extcon-max3355.c:127:34: error: array type has incomplete
> element type 'struct of_device_id'
>
On Wed, Jul 11, 2018 at 09:33:45AM -0700, Stephen Boyd wrote:
> Quoting Shawn Guo (2018-07-11 01:43:03)
> > On Fri, Jul 06, 2018 at 01:58:46PM -0700, Stephen Boyd wrote:
> > > Quoting Anson Huang (2018-06-21 23:32:33)
> > > > According to Reference Manual Rev.0, 06/2017,
> > > > there are GPIO
On Wed, Jul 11, 2018 at 09:33:45AM -0700, Stephen Boyd wrote:
> Quoting Shawn Guo (2018-07-11 01:43:03)
> > On Fri, Jul 06, 2018 at 01:58:46PM -0700, Stephen Boyd wrote:
> > > Quoting Anson Huang (2018-06-21 23:32:33)
> > > > According to Reference Manual Rev.0, 06/2017,
> > > > there are GPIO
In addition to what Paolo's noticed, may be change printk to pr_info()
while editing around it:
> -
> printk(KERN_INFO "kvm-clock: Using msrs %x and %x",
> msr_kvm_system_time, msr_kvm_wall_clock);
>
> + hv_clock = (struct pvclock_vsyscall_time_info *)hv_clock_mem;
>
In addition to what Paolo's noticed, may be change printk to pr_info()
while editing around it:
> -
> printk(KERN_INFO "kvm-clock: Using msrs %x and %x",
> msr_kvm_system_time, msr_kvm_wall_clock);
>
> + hv_clock = (struct pvclock_vsyscall_time_info *)hv_clock_mem;
>
LGTM
On 2018/7/12 5:02, Matthew Wilcox wrote:
> Return NULL instead of ERR_PTR when we can't allocate a FID. The ENOSPC
> return value was getting all the way back to userspace, and that's
> confusing for a userspace program which isn't expecting read() to tell it
> there's no space left on the
On Fri, Jul 6, 2018 at 12:26 PM Thomas Gleixner wrote:
>
> There is no requirement for wall_clock data to be page aligned or page
> sized.
>
Reviewed-by: Pavel Tatashin
LGTM
On 2018/7/12 5:02, Matthew Wilcox wrote:
> Return NULL instead of ERR_PTR when we can't allocate a FID. The ENOSPC
> return value was getting all the way back to userspace, and that's
> confusing for a userspace program which isn't expecting read() to tell it
> there's no space left on the
On Fri, Jul 6, 2018 at 12:26 PM Thomas Gleixner wrote:
>
> There is no requirement for wall_clock data to be page aligned or page
> sized.
>
Reviewed-by: Pavel Tatashin
On Wed, Jul 11, 2018 at 04:37:27PM -0700, Paul E. McKenney wrote:
> On Wed, Jul 11, 2018 at 02:32:59PM -0700, Paul E. McKenney wrote:
> > On Wed, Jul 11, 2018 at 11:11:19PM +0200, Christian Borntraeger wrote:
> > >
> > >
> > > On 07/11/2018 10:27 PM, Paul E. McKenney wrote:
> > > > On Wed, Jul
On Wed, Jul 11, 2018 at 04:37:27PM -0700, Paul E. McKenney wrote:
> On Wed, Jul 11, 2018 at 02:32:59PM -0700, Paul E. McKenney wrote:
> > On Wed, Jul 11, 2018 at 11:11:19PM +0200, Christian Borntraeger wrote:
> > >
> > >
> > > On 07/11/2018 10:27 PM, Paul E. McKenney wrote:
> > > > On Wed, Jul
2018-07-09 20:39 GMT+09:00 Dirk Gouders :
> Dirk Gouders writes:
>
>> Dirk Gouders writes:
>>
>>> Masahiro Yamada writes:
>>>
syncconfig updates the .config only when sym_change_count > 0, i.e.
any change in config symbols has been detected.
Not only symbols but also
2018-07-09 20:39 GMT+09:00 Dirk Gouders :
> Dirk Gouders writes:
>
>> Dirk Gouders writes:
>>
>>> Masahiro Yamada writes:
>>>
syncconfig updates the .config only when sym_change_count > 0, i.e.
any change in config symbols has been detected.
Not only symbols but also
> So this still will have some overhead when kvmclock is not in use, but
> bringing it down to zero would be a massive trainwreck and even more
> indirections.
Hi Thomas,
In my opinion, having kvmclock page in __initdata for boot cpu, and
setup it in init_hypervisor_platform(). Later, switch to
> So this still will have some overhead when kvmclock is not in use, but
> bringing it down to zero would be a massive trainwreck and even more
> indirections.
Hi Thomas,
In my opinion, having kvmclock page in __initdata for boot cpu, and
setup it in init_hypervisor_platform(). Later, switch to
Hi Rob,
On Wed, 11 Jul 2018 10:12:06 -0600 Rob Herring wrote:
> On Fri, Jul 06, 2018 at 03:20:47PM +0800, Jisheng Zhang wrote:
> > Synopsys SDHCI compatible DesignWare Cores Mobile Storage Host
> > Controller can support eMMC/SD/SDIO. Add the bindings.
> >
> > Signed-off-by: Jisheng Zhang
> >
Hi Rob,
On Wed, 11 Jul 2018 10:12:06 -0600 Rob Herring wrote:
> On Fri, Jul 06, 2018 at 03:20:47PM +0800, Jisheng Zhang wrote:
> > Synopsys SDHCI compatible DesignWare Cores Mobile Storage Host
> > Controller can support eMMC/SD/SDIO. Add the bindings.
> >
> > Signed-off-by: Jisheng Zhang
> >
On Wed, Jul 11, 2018 at 6:45 PM, Laura Abbott wrote:
>> +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK
>> +#define MIN_STACK_LEFT 256
>> +
>> +void __used stackleak_check_alloca(unsigned long size)
>> +{
>> + unsigned long sp, stack_left;
>> +
>> + sp = current_stack_pointer;
>> +
>> +
On Wed, Jul 11, 2018 at 6:45 PM, Laura Abbott wrote:
>> +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK
>> +#define MIN_STACK_LEFT 256
>> +
>> +void __used stackleak_check_alloca(unsigned long size)
>> +{
>> + unsigned long sp, stack_left;
>> +
>> + sp = current_stack_pointer;
>> +
>> +
Some drivers could call serial8250_do_set_divisor() to complete its
own set_divisor routine. Export this symbol for code reusing.
Signed-off-by: Jisheng Zhang
Reviewed-by: Andy Shevchenko
---
drivers/tty/serial/8250/8250_port.c | 5 +++--
include/linux/serial_8250.h | 3 +++
2 files
Some drivers could call serial8250_do_set_divisor() to complete its
own set_divisor routine. Export this symbol for code reusing.
Signed-off-by: Jisheng Zhang
Reviewed-by: Andy Shevchenko
---
drivers/tty/serial/8250/8250_port.c | 5 +++--
include/linux/serial_8250.h | 3 +++
2 files
On (07/11/18 15:17), Steven Rostedt wrote:
> +bool ignore_console_lock_warning __read_mostly;
> +EXPORT_SYMBOL(ignore_console_lock_warning);
OK. So, to recap,
We made is_console_locked() EXPORT_SYMBOL recently [it's still in linux-next],
so people could use WARN_CONSOLE_UNLOCKED in more places;
On (07/11/18 15:17), Steven Rostedt wrote:
> +bool ignore_console_lock_warning __read_mostly;
> +EXPORT_SYMBOL(ignore_console_lock_warning);
OK. So, to recap,
We made is_console_locked() EXPORT_SYMBOL recently [it's still in linux-next],
so people could use WARN_CONSOLE_UNLOCKED in more places;
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
Now the preparation is done, it's easy to add the feature support.
This patch firstly tries to get the fractional divisor width during
probe,
On Thu, 2018-06-28 at 13:41 +0930, Joel Stanley wrote:
> On 27 June 2018 at 08:55, Benjamin Herrenschmidt
> wrote:
> > This adds a few more tracepoints that have proven useful when
> > debugging issues with the FSI bus.
> >
> > Signed-off-by: Benjamin Herrenschmidt
>
> Reviewed-by: Joel
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
Now the preparation is done, it's easy to add the feature support.
This patch firstly tries to get the fractional divisor width during
probe,
On Thu, 2018-06-28 at 13:41 +0930, Joel Stanley wrote:
> On 27 June 2018 at 08:55, Benjamin Herrenschmidt
> wrote:
> > This adds a few more tracepoints that have proven useful when
> > debugging issues with the FSI bus.
> >
> > Signed-off-by: Benjamin Herrenschmidt
>
> Reviewed-by: Joel
Add these two hooks so that they can be overridden with driver specific
implementations.
Signed-off-by: Jisheng Zhang
Reviewed-by: Andy Shevchenko
---
drivers/tty/serial/8250/8250_core.c | 4
drivers/tty/serial/8250/8250_port.c | 27 +++
Add these two hooks so that they can be overridden with driver specific
implementations.
Signed-off-by: Jisheng Zhang
Reviewed-by: Andy Shevchenko
---
drivers/tty/serial/8250/8250_core.c | 4
drivers/tty/serial/8250/8250_port.c | 27 +++
From: Peng Hao
Windows I/O, such as the real-time clock. The address register (port
0x70 in the RTC case) can use coalesced I/O, cutting the number of
userspace exits by half when reading or writing the RTC.
Guest access rtc like this: write register index to 0x70, then write or
read data from
From: Peng Hao
Windows I/O, such as the real-time clock. The address register (port
0x70 in the RTC case) can use coalesced I/O, cutting the number of
userspace exits by half when reading or writing the RTC.
Guest access rtc like this: write register index to 0x70, then write or
read data from
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
patch1 introduces necessary hooks to 8250 core.
patch2 exports serial8250_do_set_divisor()
patch3 implements the fractional divisor support for
For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
valid divisor latch fraction register. The fractional divisor width is
4bits ~ 6bits.
patch1 introduces necessary hooks to 8250 core.
patch2 exports serial8250_do_set_divisor()
patch3 implements the fractional divisor support for
On Thu, 12 Jul 2018 01:40:41 + "Lu, Aaron" wrote:
> Thanks Andrew.
> I think the credit goes to Dave Hansen
Oh. In that case, I take it all back. The patch sucks!
On Thu, 12 Jul 2018 01:40:41 + "Lu, Aaron" wrote:
> Thanks Andrew.
> I think the credit goes to Dave Hansen
Oh. In that case, I take it all back. The patch sucks!
On 07/11/2018 05:03 PM, Kees Cook wrote:
From: Laura Abbott
This adds support for the STACKLEAK gcc plugin to arm64 by implementing
stackleak_check_alloca(), based heavily on the x86 version, and adding the
two helpers used by the stackleak common code: current_top_of_stack() and
On 07/11/2018 05:03 PM, Kees Cook wrote:
From: Laura Abbott
This adds support for the STACKLEAK gcc plugin to arm64 by implementing
stackleak_check_alloca(), based heavily on the x86 version, and adding the
two helpers used by the stackleak common code: current_top_of_stack() and
On 7/11/18 5:48 PM, Hugh Dickins wrote:
__split_huge_pmd_locked() must check if the cleared huge pmd was dirty,
and propagate that to PageDirty: otherwise, data may be lost when a huge
tmpfs page is modified then split then reclaimed.
How has this taken so long to be noticed? Because there
On 7/11/18 5:48 PM, Hugh Dickins wrote:
__split_huge_pmd_locked() must check if the cleared huge pmd was dirty,
and propagate that to PageDirty: otherwise, data may be lost when a huge
tmpfs page is modified then split then reclaimed.
How has this taken so long to be noticed? Because there
On Wed, 2018-07-11 at 14:35 -0700, Andrew Morton wrote:
> On Wed, 11 Jul 2018 13:58:55 +0800 Aaron Lu wrote:
>
> > [550 lines of changelog]
>
> OK, I'm convinced ;) That was a lot of work - thanks for being exhaustive.
Thanks Andrew.
I think the credit goes to Dave Hansen since he has been
On Wed, 2018-07-11 at 14:35 -0700, Andrew Morton wrote:
> On Wed, 11 Jul 2018 13:58:55 +0800 Aaron Lu wrote:
>
> > [550 lines of changelog]
>
> OK, I'm convinced ;) That was a lot of work - thanks for being exhaustive.
Thanks Andrew.
I think the credit goes to Dave Hansen since he has been
On Thu, 12 Jul 2018 at 08:07, Vitaly Kuznetsov wrote:
>
> When we switched from doing rdmsr() to reading FS/GS base values from
> current->thread we completely forgot about legacy 32-bit userspaces which
> we still support in KVM (why?). task->thread.{fsbase,gsbase} are only
> synced for 64-bit
On Thu, 12 Jul 2018 at 08:07, Vitaly Kuznetsov wrote:
>
> When we switched from doing rdmsr() to reading FS/GS base values from
> current->thread we completely forgot about legacy 32-bit userspaces which
> we still support in KVM (why?). task->thread.{fsbase,gsbase} are only
> synced for 64-bit
Hi all,
It looks like part of the xfs tree (the iomap-4.19-merge branch) that
was merge into the gfs2 tree has been rebased and the gfs2 tree has not
been updated to cope. The rebase commits are exactly the same patches
(though I didn't check to see if any of the commit messages had changed).
Hi all,
It looks like part of the xfs tree (the iomap-4.19-merge branch) that
was merge into the gfs2 tree has been rebased and the gfs2 tree has not
been updated to cope. The rebase commits are exactly the same patches
(though I didn't check to see if any of the commit messages had changed).
On 2018년 07월 12일 10:30, Chanwoo Choi wrote:
> On 2018년 07월 12일 00:50, Arnd Bergmann wrote:
>> Another driver turned up that is missing linux/mod_devicetable.h after
>> the device IDs are split out from linux/platform_device.h:
>>
>> drivers/extcon/extcon-max3355.c:127:34: error: array type has
On 2018년 07월 12일 10:30, Chanwoo Choi wrote:
> On 2018년 07월 12일 00:50, Arnd Bergmann wrote:
>> Another driver turned up that is missing linux/mod_devicetable.h after
>> the device IDs are split out from linux/platform_device.h:
>>
>> drivers/extcon/extcon-max3355.c:127:34: error: array type has
On 2018년 07월 12일 00:50, Arnd Bergmann wrote:
> Another driver turned up that is missing linux/mod_devicetable.h after
> the device IDs are split out from linux/platform_device.h:
>
> drivers/extcon/extcon-max3355.c:127:34: error: array type has incomplete
> element type 'struct of_device_id'
>
On 2018년 07월 12일 00:50, Arnd Bergmann wrote:
> Another driver turned up that is missing linux/mod_devicetable.h after
> the device IDs are split out from linux/platform_device.h:
>
> drivers/extcon/extcon-max3355.c:127:34: error: array type has incomplete
> element type 'struct of_device_id'
>
On Wed, 11 Jul 2018 17:31:00 -0700
Joel Fernandes wrote:
> On Wed, Jul 11, 2018 at 09:06:49AM -0400, Steven Rostedt wrote:
> > On Wed, 11 Jul 2018 14:56:47 +0200
> > Peter Zijlstra wrote:
> >
> > > On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > > > static inline void
On Wed, 11 Jul 2018 17:31:00 -0700
Joel Fernandes wrote:
> On Wed, Jul 11, 2018 at 09:06:49AM -0400, Steven Rostedt wrote:
> > On Wed, 11 Jul 2018 14:56:47 +0200
> > Peter Zijlstra wrote:
> >
> > > On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > > > static inline void
On Wed, 11 Jul 2018 13:56:39 -0700
Joel Fernandes wrote:
> > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > > extern struct tracepoint __tracepoint_##name; \
> > > static inline void trace_##name(proto) \
> > > {
On Wed, 11 Jul 2018 13:56:39 -0700
Joel Fernandes wrote:
> > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > > extern struct tracepoint __tracepoint_##name; \
> > > static inline void trace_##name(proto) \
> > > {
On Wed, Jul 11, 2018 at 08:40:08PM +0800, Baoquan He wrote:
>Please try this v3 patch:
>
>From 9850d3de9c02e570dc7572069a9749a8add4c4c7 Mon Sep 17 00:00:00 2001
>From: Baoquan He
>Date: Wed, 11 Jul 2018 20:31:51 +0800
>Subject: [PATCH v3] mm, page_alloc: find movable zone after kernel text
>
>In
On Wed, Jul 11, 2018 at 08:40:08PM +0800, Baoquan He wrote:
>Please try this v3 patch:
>
>From 9850d3de9c02e570dc7572069a9749a8add4c4c7 Mon Sep 17 00:00:00 2001
>From: Baoquan He
>Date: Wed, 11 Jul 2018 20:31:51 +0800
>Subject: [PATCH v3] mm, page_alloc: find movable zone after kernel text
>
>In
Hi Stephen,
On Thu, Jul 12, 2018 at 5:41 AM Stephen Rothwell wrote:
>
> Hi Shawn,
>
> Commit
>
> 3a27f1ac04df ("ARM: dts: imx6ul: add GPIO clocks")
>
> is missing a Signed-off-by from its committer.
Thanks for spotting that. I just fixed it. Thanks.
Shawn
Hi Stephen,
On Thu, Jul 12, 2018 at 5:41 AM Stephen Rothwell wrote:
>
> Hi Shawn,
>
> Commit
>
> 3a27f1ac04df ("ARM: dts: imx6ul: add GPIO clocks")
>
> is missing a Signed-off-by from its committer.
Thanks for spotting that. I just fixed it. Thanks.
Shawn
Hi Lorenzo,
Thanks a lot.
Best Regards,
Xiaowei Song.
> -邮件原件-
> 发件人: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com]
> 发送时间: 2018年7月11日 19:33
> 收件人: Songxiaowei (Kirin_DRV)
> 抄送: Wangbinghui ; bhelg...@google.com;
> robh...@kernel.org; linux-...@vger.kernel.org;
Hi Rob,
Thanks for the response.
On Thu, 12 Jul 2018, at 05:34, Rob Herring wrote:
> On Wed, Jul 11, 2018 at 03:01:19PM +0930, Andrew Jeffery wrote:
> > Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
> > provide remote management of (primarily) server platforms. BMCs are
Hi Lorenzo,
Thanks a lot.
Best Regards,
Xiaowei Song.
> -邮件原件-
> 发件人: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com]
> 发送时间: 2018年7月11日 19:33
> 收件人: Songxiaowei (Kirin_DRV)
> 抄送: Wangbinghui ; bhelg...@google.com;
> robh...@kernel.org; linux-...@vger.kernel.org;
Hi Rob,
Thanks for the response.
On Thu, 12 Jul 2018, at 05:34, Rob Herring wrote:
> On Wed, Jul 11, 2018 at 03:01:19PM +0930, Andrew Jeffery wrote:
> > Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
> > provide remote management of (primarily) server platforms. BMCs are
__split_huge_pmd_locked() must check if the cleared huge pmd was dirty,
and propagate that to PageDirty: otherwise, data may be lost when a huge
tmpfs page is modified then split then reclaimed.
How has this taken so long to be noticed? Because there was no problem
when the huge page is written
__split_huge_pmd_locked() must check if the cleared huge pmd was dirty,
and propagate that to PageDirty: otherwise, data may be lost when a huge
tmpfs page is modified then split then reclaimed.
How has this taken so long to be noticed? Because there was no problem
when the huge page is written
Linus Torvalds wrote:
> All your documentation (both commit logs, man-pages and in-kernel
> actual docs you add) only talk about "what".
>
> They don't talk about _why_.
>
> I can imagine why's. But I think that the "why" is actually way mnore
> important than the what. At no point did I see a
Linus Torvalds wrote:
> All your documentation (both commit logs, man-pages and in-kernel
> actual docs you add) only talk about "what".
>
> They don't talk about _why_.
>
> I can imagine why's. But I think that the "why" is actually way mnore
> important than the what. At no point did I see a
On Wed, Jul 11, 2018 at 03:12:56PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 11:21:47AM -0700, Joel Fernandes wrote:
> > One note, I have to check for lockdep recursion in the code that calls
> > the trace events API and bail out if we're in lockdep recursion
>
> I'm not seeing any
On Wed, Jul 11, 2018 at 03:12:56PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 11:21:47AM -0700, Joel Fernandes wrote:
> > One note, I have to check for lockdep recursion in the code that calls
> > the trace events API and bail out if we're in lockdep recursion
>
> I'm not seeing any
Le mer. 11 juill. 2018, à 15 h 56, Steven Rostedt
a écrit :
>
> On Wed, 11 Jul 2018 15:34:30 -0400
> Francis Deslauriers wrote:
>
> > Hi Steven,
> > I tested it and it prevents the kernel crash I am witnessing.
> > As for the side-effect that Masami mentioned regarding not being able to
> >
Le mer. 11 juill. 2018, à 15 h 56, Steven Rostedt
a écrit :
>
> On Wed, 11 Jul 2018 15:34:30 -0400
> Francis Deslauriers wrote:
>
> > Hi Steven,
> > I tested it and it prevents the kernel crash I am witnessing.
> > As for the side-effect that Masami mentioned regarding not being able to
> >
On Wed, Jul 11, 2018 at 5:13 AM, Himanshu Jha
wrote:
> Bosch BME680 is a 4-in-1 sensor with temperature, pressure, humidity
> and gas sensing capability. It supports both I2C and SPI communication
> protocol for effective data communication.
>
> The device supports two modes:
>
> 1. Sleep mode
>
On Wed, Jul 11, 2018 at 5:13 AM, Himanshu Jha
wrote:
> Bosch BME680 is a 4-in-1 sensor with temperature, pressure, humidity
> and gas sensing capability. It supports both I2C and SPI communication
> protocol for effective data communication.
>
> The device supports two modes:
>
> 1. Sleep mode
>
On Wed, Jul 11, 2018 at 09:06:49AM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 14:56:47 +0200
> Peter Zijlstra wrote:
>
> > On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > > static inline void tracepoint_synchronize_unregister(void)
> > > {
> > > +
On Wed, Jul 11, 2018 at 09:06:49AM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 14:56:47 +0200
> Peter Zijlstra wrote:
>
> > On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
> > > static inline void tracepoint_synchronize_unregister(void)
> > > {
> > > +
On Wed, Jul 4, 2018 at 11:24 PM, Masahiro Yamada
wrote:
> Collect relevant code into the scripts/gcc-plugins directory.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> arch/Kconfig| 146
> +---
> scripts/gcc-plugins/Kconfig | 141
On Wed, Jul 4, 2018 at 11:24 PM, Masahiro Yamada
wrote:
> Collect relevant code into the scripts/gcc-plugins directory.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> arch/Kconfig| 146
> +---
> scripts/gcc-plugins/Kconfig | 141
On Wed, 2018-07-11 at 14:04 -0600, Rob Herring wrote:
> On Wed, Jul 11, 2018 at 03:01:19PM +0930, Andrew Jeffery wrote:
> > Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
> > provide remote management of (primarily) server platforms. BMCs are
> > often tightly coupled to
On Wed, 2018-07-11 at 14:04 -0600, Rob Herring wrote:
> On Wed, Jul 11, 2018 at 03:01:19PM +0930, Andrew Jeffery wrote:
> > Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
> > provide remote management of (primarily) server platforms. BMCs are
> > often tightly coupled to
101 - 200 of 1754 matches
Mail list logo
