Hi Ulf,
On 11 June 2018 at 15:15, Ulf Hansson wrote:
> On 8 June 2018 at 10:18, Chunyan Zhang wrote:
>> From: Chunyan Zhang
>>
>> This patch adds the initial support of Secure Digital Host Controller
>> Interface compliant controller - R11 found in some latest Spreadtrum
>> chipsets.
>>
>> R11
Hi Ulf,
On 11 June 2018 at 15:15, Ulf Hansson wrote:
> On 8 June 2018 at 10:18, Chunyan Zhang wrote:
>> From: Chunyan Zhang
>>
>> This patch adds the initial support of Secure Digital Host Controller
>> Interface compliant controller - R11 found in some latest Spreadtrum
>> chipsets.
>>
>> R11
Current ISH driver only registers suspend/resume PM callbacks which don't
support hibernation (suspend to disk). Basically after hiberation, the ISH
can't resume properly and user may not see sensor events
(for example: screen rotation may not work).
User will not see a crash or panic or anything
Current ISH driver only registers suspend/resume PM callbacks which don't
support hibernation (suspend to disk). Basically after hiberation, the ISH
can't resume properly and user may not see sensor events
(for example: screen rotation may not work).
User will not see a crash or panic or anything
On Tue, 12 Jun 2018, Gwendal Grignou wrote:
> On Sun, Jun 10, 2018 at 11:08 PM Lee Jones wrote:
> >
> > On Fri, 08 Jun 2018, Benson Leung wrote:
> >
> > >
> > > On Fri, Jun 08, 2018 at 04:48:06PM +0200, Arnd Bergmann wrote:
> > > > This function is no longer called, so we get a harmless
> > > >
On Tue, 12 Jun 2018, Gwendal Grignou wrote:
> On Sun, Jun 10, 2018 at 11:08 PM Lee Jones wrote:
> >
> > On Fri, 08 Jun 2018, Benson Leung wrote:
> >
> > >
> > > On Fri, Jun 08, 2018 at 04:48:06PM +0200, Arnd Bergmann wrote:
> > > > This function is no longer called, so we get a harmless
> > > >
Hi everyone,
I wrote a patch for this issue.
There was a discussion about prechecking approach, but I finally found
out it's hard to make change on memblock after numa_init, so I take
another apporach (see patch description).
I'm glad if you check that it works for you.
Thanks,
Naoya Horiguchi
Hi everyone,
I wrote a patch for this issue.
There was a discussion about prechecking approach, but I finally found
out it's hard to make change on memblock after numa_init, so I take
another apporach (see patch description).
I'm glad if you check that it works for you.
Thanks,
Naoya Horiguchi
Add const to the declaration of various local variables of type
kempld_platform_data for which the referenced value is always only
dereferenced or passed to a const parameter, to record the fact that
kempld_platform_data_generic is declared as const.
The semantic match that finds this issue is as
Add const to the declaration of various local variables of type
kempld_platform_data for which the referenced value is always only
dereferenced or passed to a const parameter, to record the fact that
kempld_platform_data_generic is declared as const.
The semantic match that finds this issue is as
FYI, we noticed the following commit (built with gcc-5):
commit: 4808e7a5dc055fd8776e6b59e02775730ea716f6 ("watchdog/softlockup: Replace
"watchdog/%u" threads with cpu_stop_work")
url:
https://github.com/0day-ci/linux/commits/Peter-Zijlstra/kthread-smpboot-More-fixes/20180613-003329
in
FYI, we noticed the following commit (built with gcc-5):
commit: 4808e7a5dc055fd8776e6b59e02775730ea716f6 ("watchdog/softlockup: Replace
"watchdog/%u" threads with cpu_stop_work")
url:
https://github.com/0day-ci/linux/commits/Peter-Zijlstra/kthread-smpboot-More-fixes/20180613-003329
in
On Tue, Jun 12, 2018 at 03:40:41PM -0700, John Stultz wrote:
> Hey all,
> I noticed recently that linus/master (plus patches) stopped booting
> to UI on HiKey960, and I bisected the issue down to:
> 92170b62f1c1 ("debugfs: inode: debugfs_create_dir uses mode permission
> from parent")
>
> On
On Tue, Jun 12, 2018 at 03:40:41PM -0700, John Stultz wrote:
> Hey all,
> I noticed recently that linus/master (plus patches) stopped booting
> to UI on HiKey960, and I bisected the issue down to:
> 92170b62f1c1 ("debugfs: inode: debugfs_create_dir uses mode permission
> from parent")
>
> On
On Tue, Jun 12, 2018 at 9:49 PM Greg Kroah-Hartman
wrote:
>
> The revert is fine, I'll work on the kvm debugfs file stuff for 4.19.
Yeah, I did two fairly brute-force fixes for two different issues
(the only common thread was kvm - testing the first fix was what then
got me to the debugfs
On Tue, Jun 12, 2018 at 9:49 PM Greg Kroah-Hartman
wrote:
>
> The revert is fine, I'll work on the kvm debugfs file stuff for 4.19.
Yeah, I did two fairly brute-force fixes for two different issues
(the only common thread was kvm - testing the first fix was what then
got me to the debugfs
On Tue, Jun 12, 2018 at 08:52:08PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 8:26 PM Linus Torvalds
> wrote:
> >
> > Ok, so commit 95cde3c59966 ("debugfs: inode: debugfs_create_dir uses
> > mode permission from parent") breaks lkvm, and I think qemu-kvm too.
> >
> > The commit looks
On Tue, Jun 12, 2018 at 08:52:08PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 8:26 PM Linus Torvalds
> wrote:
> >
> > Ok, so commit 95cde3c59966 ("debugfs: inode: debugfs_create_dir uses
> > mode permission from parent") breaks lkvm, and I think qemu-kvm too.
> >
> > The commit looks
On Tue, Jun 12, 2018 at 08:26:46PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 8:00 PM Linus Torvalds
> wrote:
> >
> > Yeah, the biusection seems to actually be diving into Greg's device pulls.
> >
> > Odd. I'm not seeing why that would break kvm, but maybe there's
> > something in the
On Tue, Jun 12, 2018 at 08:26:46PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 8:00 PM Linus Torvalds
> wrote:
> >
> > Yeah, the biusection seems to actually be diving into Greg's device pulls.
> >
> > Odd. I'm not seeing why that would break kvm, but maybe there's
> > something in the
* Janusz Krzysztofik [180613 01:18]:
> On Wednesday, June 13, 2018 12:23:56 AM CEST Dmitry Torokhov wrote:
> > Hi Janusz,
> >
> > On Sat, Jun 09, 2018 at 04:02:15PM +0200, Janusz Krzysztofik wrote:
> > > GPIO lookup table for ams-delta-serio device was introduced by commit
> > > 0486738928bf
* Janusz Krzysztofik [180613 01:18]:
> On Wednesday, June 13, 2018 12:23:56 AM CEST Dmitry Torokhov wrote:
> > Hi Janusz,
> >
> > On Sat, Jun 09, 2018 at 04:02:15PM +0200, Janusz Krzysztofik wrote:
> > > GPIO lookup table for ams-delta-serio device was introduced by commit
> > > 0486738928bf
On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote:
> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5
> conflicts (v3.18.112-22-gb0582263e3c9)
>
> Full Boot Summary:
>
On Tue, Jun 12, 2018 at 02:58:16PM -0600, Shuah Khan wrote:
> On 06/12/2018 10:46 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.108 release.
> > There are 31 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Jun 12, 2018 at 02:58:16PM -0600, Shuah Khan wrote:
> On 06/12/2018 10:46 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.108 release.
> > There are 31 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote:
> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5
> conflicts (v3.18.112-22-gb0582263e3c9)
>
> Full Boot Summary:
>
On Tue, May 08, 2018 at 04:50:16PM +0800, Lidong Chen wrote:
> The userspace may invoke ibv_reg_mr and ibv_dereg_mr by different threads.
> If when ibv_dereg_mr invoke and the thread which invoked ibv_reg_mr has
> exited, get_pid_task will return NULL, ib_umem_release does not decrease
>
On Tue, May 08, 2018 at 04:50:16PM +0800, Lidong Chen wrote:
> The userspace may invoke ibv_reg_mr and ibv_dereg_mr by different threads.
> If when ibv_dereg_mr invoke and the thread which invoked ibv_reg_mr has
> exited, get_pid_task will return NULL, ib_umem_release does not decrease
>
On Tue, Jun 12, 2018 at 09:08:27PM -0700, John Stultz wrote:
> On Tue, Jun 12, 2018 at 6:02 PM, John Stultz wrote:
> > Hey Tejun,
> > With the current linus/master, I'm able to fairly regularly trip
> > OOPSes (two examples below) in mem_cgroup_protected(), which seems to
> > be new. I haven't
On Tue, Jun 12, 2018 at 09:08:27PM -0700, John Stultz wrote:
> On Tue, Jun 12, 2018 at 6:02 PM, John Stultz wrote:
> > Hey Tejun,
> > With the current linus/master, I'm able to fairly regularly trip
> > OOPSes (two examples below) in mem_cgroup_protected(), which seems to
> > be new. I haven't
Hi Michael, Stephen,
We are adding ACPI support in our Linux based platform.
At present our clock hierarchy using common clock framework through DTS.
Now we required ACPI support in common clock framework to upgrade our platform.
For example, clk_get API called in many drivers to get clock
Hi Michael, Stephen,
We are adding ACPI support in our Linux based platform.
At present our clock hierarchy using common clock framework through DTS.
Now we required ACPI support in common clock framework to upgrade our platform.
For example, clk_get API called in many drivers to get clock
* John Stultz [180612 22:15]:
> Hey Folks,
> I noticed with linus/master wifi wasn't coming up on HiKey960. I
> bisected it down and it seems to be due to:
>
> 60f36637bbbd ("wlcore: sdio: allow pm to handle sdio power") and
> 728a9dc61f13 ("wlcore: sdio: Fix flakey SDIO runtime PM handling")
* John Stultz [180612 22:15]:
> Hey Folks,
> I noticed with linus/master wifi wasn't coming up on HiKey960. I
> bisected it down and it seems to be due to:
>
> 60f36637bbbd ("wlcore: sdio: allow pm to handle sdio power") and
> 728a9dc61f13 ("wlcore: sdio: Fix flakey SDIO runtime PM handling")
On Tue, Jun 12, 2018 at 6:02 PM, John Stultz wrote:
> Hey Tejun,
> With the current linus/master, I'm able to fairly regularly trip
> OOPSes (two examples below) in mem_cgroup_protected(), which seems to
> be new. I haven't managed to trigger this sort of thing with v4.17.
>
> I've not had
On Tue, Jun 12, 2018 at 6:02 PM, John Stultz wrote:
> Hey Tejun,
> With the current linus/master, I'm able to fairly regularly trip
> OOPSes (two examples below) in mem_cgroup_protected(), which seems to
> be new. I haven't managed to trigger this sort of thing with v4.17.
>
> I've not had
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/exofs/super.c b/fs/exofs/super.c
index f3e17a9..75b5db0 100644
--- a/fs/exofs/super.c
+++ b/fs/exofs/super.c
@@ -118,7 +118,7 @@ static int parse_options(char *options, struct
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/exofs/super.c b/fs/exofs/super.c
index f3e17a9..75b5db0 100644
--- a/fs/exofs/super.c
+++ b/fs/exofs/super.c
@@ -118,7 +118,7 @@ static int parse_options(char *options, struct
There are some cases can cause memory leak when parsing
option 'osdname'.
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/exofs/super.c b/fs/exofs/super.c
index 719a315..f3e17a9 100644
--- a/fs/exofs/super.c
+++
There are some cases can cause memory leak when parsing
option 'osdname'.
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/exofs/super.c b/fs/exofs/super.c
index 719a315..f3e17a9 100644
--- a/fs/exofs/super.c
+++
On Tue, Jun 12, 2018 at 8:26 PM Linus Torvalds
wrote:
>
> Ok, so commit 95cde3c59966 ("debugfs: inode: debugfs_create_dir uses
> mode permission from parent") breaks lkvm, and I think qemu-kvm too.
>
> The commit looks like the RightThing(tm) to do, but we do not break
> existing work-flows, no
On Tue, Jun 12, 2018 at 8:26 PM Linus Torvalds
wrote:
>
> Ok, so commit 95cde3c59966 ("debugfs: inode: debugfs_create_dir uses
> mode permission from parent") breaks lkvm, and I think qemu-kvm too.
>
> The commit looks like the RightThing(tm) to do, but we do not break
> existing work-flows, no
On Tuesday 12 June 2018 08:05 PM, J, KEERTHY wrote:
>
>
> On 6/12/2018 6:39 PM, Linus Walleij wrote:
>> On Wed, Jun 6, 2018 at 11:18 AM, Keerthy wrote:
>>
>>> Currently IRQ resource fetching is done at the very end of probe.
>>> In case the of IRQ resource not being ready, we defer probe
>>>
On Tuesday 12 June 2018 08:05 PM, J, KEERTHY wrote:
>
>
> On 6/12/2018 6:39 PM, Linus Walleij wrote:
>> On Wed, Jun 6, 2018 at 11:18 AM, Keerthy wrote:
>>
>>> Currently IRQ resource fetching is done at the very end of probe.
>>> In case the of IRQ resource not being ready, we defer probe
>>>
This is needed in case of PROBE_DEFER if IRQ resource is not yet ready.
Signed-off-by: Keerthy
---
Tested for GPIO Interrupts on da850-lcdk board.
Changes in v3:
Changed type of bank_irq to int from unsigned
drivers/gpio/gpio-davinci.c | 29 +++--
1 file
Currently the driver assumes that the interrupts are continuous
and does platform_get_irq only once and assumes the rest are continuous,
instead call platform_get_irq for all the interrupts and store them
in an array for later use.
Signed-off-by: Keerthy
---
Tested for GPIO Interrupts on
This is needed in case of PROBE_DEFER if IRQ resource is not yet ready.
Signed-off-by: Keerthy
---
Tested for GPIO Interrupts on da850-lcdk board.
Changes in v3:
Changed type of bank_irq to int from unsigned
drivers/gpio/gpio-davinci.c | 29 +++--
1 file
Currently the driver assumes that the interrupts are continuous
and does platform_get_irq only once and assumes the rest are continuous,
instead call platform_get_irq for all the interrupts and store them
in an array for later use.
Signed-off-by: Keerthy
---
Tested for GPIO Interrupts on
On Tue, Jun 12, 2018 at 3:12 PM, John Stultz wrote:
> Hey Folks,
> I noticed with linus/master wifi wasn't coming up on HiKey960. I
> bisected it down and it seems to be due to:
>
> 60f36637bbbd ("wlcore: sdio: allow pm to handle sdio power") and
> 728a9dc61f13 ("wlcore: sdio: Fix flakey SDIO
On Tue, Jun 12, 2018 at 3:12 PM, John Stultz wrote:
> Hey Folks,
> I noticed with linus/master wifi wasn't coming up on HiKey960. I
> bisected it down and it seems to be due to:
>
> 60f36637bbbd ("wlcore: sdio: allow pm to handle sdio power") and
> 728a9dc61f13 ("wlcore: sdio: Fix flakey SDIO
On 06/13/2018 01:12 AM, Matthias Kaehlcke wrote:
> Hi,
>
> On Tue, Jun 12, 2018 at 10:10:51AM +0530, Rajendra Nayak wrote:
>> The RPMh Power domain driver aggregates the corner votes from various
>> consumers for the ARC resources and communicates it to RPMh.
>>
>> We also add data for all
On 06/13/2018 01:12 AM, Matthias Kaehlcke wrote:
> Hi,
>
> On Tue, Jun 12, 2018 at 10:10:51AM +0530, Rajendra Nayak wrote:
>> The RPMh Power domain driver aggregates the corner votes from various
>> consumers for the ARC resources and communicates it to RPMh.
>>
>> We also add data for all
On Tue, Jun 12, 2018 at 8:00 PM Linus Torvalds
wrote:
>
> Yeah, the biusection seems to actually be diving into Greg's device pulls.
>
> Odd. I'm not seeing why that would break kvm, but maybe there's
> something in the device core layer that really messed it up.
>
> I'll continue to bisect to
On Tue, Jun 12, 2018 at 8:00 PM Linus Torvalds
wrote:
>
> Yeah, the biusection seems to actually be diving into Greg's device pulls.
>
> Odd. I'm not seeing why that would break kvm, but maybe there's
> something in the device core layer that really messed it up.
>
> I'll continue to bisect to
On 06/13/2018 12:36 AM, Rob Herring wrote:
> On Tue, Jun 12, 2018 at 10:10:51AM +0530, Rajendra Nayak wrote:
>> The RPMh Power domain driver aggregates the corner votes from various
>> consumers for the ARC resources and communicates it to RPMh.
>>
>> We also add data for all power domains on
On 06/13/2018 12:36 AM, Rob Herring wrote:
> On Tue, Jun 12, 2018 at 10:10:51AM +0530, Rajendra Nayak wrote:
>> The RPMh Power domain driver aggregates the corner votes from various
>> consumers for the ARC resources and communicates it to RPMh.
>>
>> We also add data for all power domains on
On Tue, Jun 12, 2018 at 7:51 PM Wanpeng Li wrote:
> >
> > Bisecting. But that's unrelated to the recent kvm build breakage.
>
> Yeah, it happens before the KVM GIT PULL on Linus's tree, you will see
> the warning above unless you lauch the guest w/ root user, maybe other
> subsystems'
On Tue, Jun 12, 2018 at 7:51 PM Wanpeng Li wrote:
> >
> > Bisecting. But that's unrelated to the recent kvm build breakage.
>
> Yeah, it happens before the KVM GIT PULL on Linus's tree, you will see
> the warning above unless you lauch the guest w/ root user, maybe other
> subsystems'
On Wed, 13 Jun 2018 at 10:42, Linus Torvalds
wrote:
>
> On Tue, Jun 12, 2018 at 7:18 PM Linus Torvalds
> wrote:
> >
> > The attached patch _may_ be the right thing to do. It's not pretty.
>
> .. and when I decided to actually do some minimal kvm testing with
> that patch, I notice that we've
On Wed, 13 Jun 2018 at 10:42, Linus Torvalds
wrote:
>
> On Tue, Jun 12, 2018 at 7:18 PM Linus Torvalds
> wrote:
> >
> > The attached patch _may_ be the right thing to do. It's not pretty.
>
> .. and when I decided to actually do some minimal kvm testing with
> that patch, I notice that we've
Hi Rafael,
On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote:
On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote:
--703623056e64c488
Content-Type: text/plain; charset="UTF-8"
On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki
wrote:
On Mon, Jun 11, 2018 at
Hi Rafael,
On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote:
On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote:
--703623056e64c488
Content-Type: text/plain; charset="UTF-8"
On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki
wrote:
On Mon, Jun 11, 2018 at
On Tue, Jun 12, 2018 at 7:18 PM Linus Torvalds
wrote:
>
> The attached patch _may_ be the right thing to do. It's not pretty.
.. and when I decided to actually do some minimal kvm testing with
that patch, I notice that we've apparently broken kvm entirely during
this merge window, and I just get
On Tue, Jun 12, 2018 at 7:18 PM Linus Torvalds
wrote:
>
> The attached patch _may_ be the right thing to do. It's not pretty.
.. and when I decided to actually do some minimal kvm testing with
that patch, I notice that we've apparently broken kvm entirely during
this merge window, and I just get
Hi all,
Note: please do *not* add any v4.19 material to your linux-next included
branches until after v4.18-rc1 has been released.
Changes since 20180612:
The drivers-x86 tree lost its build failure.
Non-merge commits (relative to Linus' tree): 928
1119 files changed, 21702 insertions
Hi all,
Note: please do *not* add any v4.19 material to your linux-next included
branches until after v4.18-rc1 has been released.
Changes since 20180612:
The drivers-x86 tree lost its build failure.
Non-merge commits (relative to Linus' tree): 928
1119 files changed, 21702 insertions
On Tue, Jun 12, 2018 at 7:03 AM Paolo Bonzini wrote:
>
> * x86: many bugfixes, implement more Hyper-V super powers,
Uhhuh, I didn't notice this initially, because my basic sanity tests
are with everything enabled, but this breaks the build:
ERROR: "ms_hyperv" [arch/x86/kvm/kvm-intel.ko]
On Tue, Jun 12, 2018 at 7:03 AM Paolo Bonzini wrote:
>
> * x86: many bugfixes, implement more Hyper-V super powers,
Uhhuh, I didn't notice this initially, because my basic sanity tests
are with everything enabled, but this breaks the build:
ERROR: "ms_hyperv" [arch/x86/kvm/kvm-intel.ko]
2018-06-12 9:32 GMT+09:00 Laura Abbott :
>
> In preparation for some upcoming work, allow module-common.lds
> to be run through the preprocessor.
>
> Signed-off-by: Laura Abbott
> ---
> scripts/.gitignore | 1 +
> scripts/Makefile
2018-06-12 9:32 GMT+09:00 Laura Abbott :
>
> In preparation for some upcoming work, allow module-common.lds
> to be run through the preprocessor.
>
> Signed-off-by: Laura Abbott
> ---
> scripts/.gitignore | 1 +
> scripts/Makefile
On Tue, Jun 12, 2018 at 01:40:22PM -0700, Brian Norris wrote:
> Hi Rob,
>
> On Tue, Jun 12, 2018 at 01:10:11PM -0600, Rob Herring wrote:
> > On Thu, Jun 07, 2018 at 11:12:13AM -0700, Matthias Kaehlcke wrote:
> > > The cros_ec_throttler monitors events from the Chrome OS Embedded
> > > Controller
On Tue, Jun 12, 2018 at 01:40:22PM -0700, Brian Norris wrote:
> Hi Rob,
>
> On Tue, Jun 12, 2018 at 01:10:11PM -0600, Rob Herring wrote:
> > On Thu, Jun 07, 2018 at 11:12:13AM -0700, Matthias Kaehlcke wrote:
> > > The cros_ec_throttler monitors events from the Chrome OS Embedded
> > > Controller
On Tue, 2018-06-12 at 18:51 -0600, Rob Herring wrote:
> On Tue, Jun 12, 2018 at 4:40 PM, Mars Cheng wrote:
> > This adds dt-binding documentation for Mediatek MT6765. Only
> > include very basic items, gic, uart timer and cpu.
>
> Check your subject...
Hi Rob
oops, my bad... will correct this
On Tue, 2018-06-12 at 18:51 -0600, Rob Herring wrote:
> On Tue, Jun 12, 2018 at 4:40 PM, Mars Cheng wrote:
> > This adds dt-binding documentation for Mediatek MT6765. Only
> > include very basic items, gic, uart timer and cpu.
>
> Check your subject...
Hi Rob
oops, my bad... will correct this
Hi Rob
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt6765-evb.dts
> > @@ -0,0 +1,39 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (c) 2018 MediaTek Inc.
> > + * Author: Mars.C
> > + *
> > + * This program is free software; you can redistribute it and/or
Hi Rob
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt6765-evb.dts
> > @@ -0,0 +1,39 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (c) 2018 MediaTek Inc.
> > + * Author: Mars.C
> > + *
> > + * This program is free software; you can redistribute it and/or
On Tue, Jun 12, 2018 at 01:00:14PM -0700, Brian Norris wrote:
> Hi,
>
> On Tue, Jun 12, 2018 at 10:11:40AM -0700, Matthias Kaehlcke wrote:
> > On Mon, Jun 11, 2018 at 06:49:13PM -0700, Brian Norris wrote:
> > > On Thu, Jun 07, 2018 at 11:12:12AM -0700, Matthias Kaehlcke wrote:
> > > > The purpose
On Tue, Jun 12, 2018 at 01:00:14PM -0700, Brian Norris wrote:
> Hi,
>
> On Tue, Jun 12, 2018 at 10:11:40AM -0700, Matthias Kaehlcke wrote:
> > On Mon, Jun 11, 2018 at 06:49:13PM -0700, Brian Norris wrote:
> > > On Thu, Jun 07, 2018 at 11:12:12AM -0700, Matthias Kaehlcke wrote:
> > > > The purpose
On Tue, Jun 12, 2018 at 4:36 PM Kees Cook wrote:
>
> - Treewide conversions of allocators to use either 2-factor argument
> variant when available, or array_size() and array3_size() as needed (Kees)
Ok, some of this smells just a tad too much of automation, but I've
done the pull and it's
On Tue, Jun 12, 2018 at 4:36 PM Kees Cook wrote:
>
> - Treewide conversions of allocators to use either 2-factor argument
> variant when available, or array_size() and array3_size() as needed (Kees)
Ok, some of this smells just a tad too much of automation, but I've
done the pull and it's
On Tue, Jun 12 2018, Paul E. McKenney wrote:
> On Tue, Jun 12, 2018 at 06:11:50PM -0700, Linus Torvalds wrote:
>> On Tue, Jun 12, 2018 at 6:02 PM Paul E. McKenney
>> wrote:
>> >
>> > We did review this one, and Neil did make requested changes to the comment
>> > header and documentation.
>>
>>
On Tue, Jun 12 2018, Paul E. McKenney wrote:
> On Tue, Jun 12, 2018 at 06:11:50PM -0700, Linus Torvalds wrote:
>> On Tue, Jun 12, 2018 at 6:02 PM Paul E. McKenney
>> wrote:
>> >
>> > We did review this one, and Neil did make requested changes to the comment
>> > header and documentation.
>>
>>
On Tue, Jun 12, 2018 at 06:11:50PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 6:02 PM Paul E. McKenney
> wrote:
> >
> > We did review this one, and Neil did make requested changes to the comment
> > header and documentation.
>
> Oh, I checked the commit for "acked-by" from you and
On Tue, Jun 12, 2018 at 06:11:50PM -0700, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 6:02 PM Paul E. McKenney
> wrote:
> >
> > We did review this one, and Neil did make requested changes to the comment
> > header and documentation.
>
> Oh, I checked the commit for "acked-by" from you and
Daniel Jordan writes:
> On Tue, Jun 12, 2018 at 09:23:19AM +0800, Huang, Ying wrote:
>> Daniel Jordan writes:
>> >> +#else
>> >> +static inline int __swap_duplicate_cluster(swp_entry_t *entry,
>> >
>> > This doesn't need inline.
>>
>> Why not? This is just a one line stub.
>
> Forgot to
Daniel Jordan writes:
> On Tue, Jun 12, 2018 at 09:23:19AM +0800, Huang, Ying wrote:
>> Daniel Jordan writes:
>> >> +#else
>> >> +static inline int __swap_duplicate_cluster(swp_entry_t *entry,
>> >
>> > This doesn't need inline.
>>
>> Why not? This is just a one line stub.
>
> Forgot to
If the WSMT ACPI table is present and indicates that a fixed communication
buffer should be used, use the firmware-specified buffer instead of
allocating a buffer in memory for communications between the dcdbas driver
and firmare.
Signed-off-by: Stuart Hayes
---
v2 Bumped driver version to
If the WSMT ACPI table is present and indicates that a fixed communication
buffer should be used, use the firmware-specified buffer instead of
allocating a buffer in memory for communications between the dcdbas driver
and firmare.
Signed-off-by: Stuart Hayes
---
v2 Bumped driver version to
On Mon, Jun 11, 2018 at 5:52 AM, Ricardo Ribalda Delgado
wrote:
> Standard TTY port that can be loaded/unloaded via serdev sysfs. This
> serdev driver can only be used by serdev controllers that are compatible
> with ttyport.
I'm hesitant to expose a tty device on top of serdev to userspace that
On Mon, Jun 11, 2018 at 5:52 AM, Ricardo Ribalda Delgado
wrote:
> Standard TTY port that can be loaded/unloaded via serdev sysfs. This
> serdev driver can only be used by serdev controllers that are compatible
> with ttyport.
I'm hesitant to expose a tty device on top of serdev to userspace that
On 6/13/2018 6:36 AM, J, KEERTHY wrote:
On 6/13/2018 1:36 AM, Grygorii Strashko wrote:
On 06/12/2018 02:59 AM, Keerthy wrote:
Currently the driver assumes that the interrupts are continuous
and does platform_get_irq only once and assumes the rest are continuous,
instead call
On 6/13/2018 6:36 AM, J, KEERTHY wrote:
On 6/13/2018 1:36 AM, Grygorii Strashko wrote:
On 06/12/2018 02:59 AM, Keerthy wrote:
Currently the driver assumes that the interrupts are continuous
and does platform_get_irq only once and assumes the rest are continuous,
instead call
On Wednesday, June 13, 2018 12:23:56 AM CEST Dmitry Torokhov wrote:
> Hi Janusz,
>
> On Sat, Jun 09, 2018 at 04:02:15PM +0200, Janusz Krzysztofik wrote:
> > GPIO lookup table for ams-delta-serio device was introduced by commit
> > 0486738928bf ("ARM: OMAP1: ams-delta: add GPIO lookup tables").
>
...instead of open coding file operations followed by custom ->open()
callbacks per each attribute.
Peng Donglin (2):
ARM: dump: Convert to use DEFINE_SHOW_ATTRIBUTE macro
ARM64: dump: Convert to use DEFINE_SHOW_ATTRIBUTE macro
arch/arm/mm/ptdump_debugfs.c | 13 +
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Peng Donglin
---
arch/arm64/mm/ptdump_debugfs.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/arch/arm64/mm/ptdump_debugfs.c b/arch/arm64/mm/ptdump_debugfs.c
index 02b18f8..24d786f 100644
On Wednesday, June 13, 2018 12:23:56 AM CEST Dmitry Torokhov wrote:
> Hi Janusz,
>
> On Sat, Jun 09, 2018 at 04:02:15PM +0200, Janusz Krzysztofik wrote:
> > GPIO lookup table for ams-delta-serio device was introduced by commit
> > 0486738928bf ("ARM: OMAP1: ams-delta: add GPIO lookup tables").
>
...instead of open coding file operations followed by custom ->open()
callbacks per each attribute.
Peng Donglin (2):
ARM: dump: Convert to use DEFINE_SHOW_ATTRIBUTE macro
ARM64: dump: Convert to use DEFINE_SHOW_ATTRIBUTE macro
arch/arm/mm/ptdump_debugfs.c | 13 +
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Peng Donglin
---
arch/arm64/mm/ptdump_debugfs.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/arch/arm64/mm/ptdump_debugfs.c b/arch/arm64/mm/ptdump_debugfs.c
index 02b18f8..24d786f 100644
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Peng Donglin
---
arch/arm/mm/ptdump_debugfs.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/arch/arm/mm/ptdump_debugfs.c b/arch/arm/mm/ptdump_debugfs.c
index be8d87b..79002fe 100644
---
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Peng Donglin
---
arch/arm/mm/ptdump_debugfs.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/arch/arm/mm/ptdump_debugfs.c b/arch/arm/mm/ptdump_debugfs.c
index be8d87b..79002fe 100644
---
1 - 100 of 1386 matches
Mail list logo
