From: YueHaibing
[ Upstream commit b24dbfe9ce03d9f83306616f22fb0e04e8960abe ]
The dma_mapping_error() returns true or false, but we want
to return -ENOMEM if there was an error.
Fixes: 174fd2597b0b ("amd-xgbe: Implement split header receive support")
Signed-off-by: YueHaibing
Signed-off-by:
From: Sebastian Andrzej Siewior
[ Upstream commit 6f3fde684d0232e66ada3410f016a58e09a87689 ]
The USB completion callback does not disable interrupts while acquiring
the lock. We want to remove the local_irq_disable() invocation from
__usb_hcd_giveback_urb() and therefore it is required for the
From: Miao Zhong
[ Upstream commit 0d535967ac658966c6ade8f82b5799092f7d5441 ]
When PRI queue occurs overflow, driver should update the OVACKFLG to
the PRIQ consumer register, otherwise subsequent PRI requests will not
be processed.
Cc: Will Deacon
Cc: Robin Murphy
Signed-off-by: Miao Zhong
From: Vivek Gautam
[ Upstream commit d1e20222d5372e951bbb2fd3f6489ec4a6ea9b11 ]
Currently we check if the number of context banks is not equal to
num_context_interrupts. However, there are booloaders such as, one
on sdm845 that reserves few context banks and thus kernel views
less than the
From: Miao Zhong
[ Upstream commit 0d535967ac658966c6ade8f82b5799092f7d5441 ]
When PRI queue occurs overflow, driver should update the OVACKFLG to
the PRIQ consumer register, otherwise subsequent PRI requests will not
be processed.
Cc: Will Deacon
Cc: Robin Murphy
Signed-off-by: Miao Zhong
From: Vivek Gautam
[ Upstream commit d1e20222d5372e951bbb2fd3f6489ec4a6ea9b11 ]
Currently we check if the number of context banks is not equal to
num_context_interrupts. However, there are booloaders such as, one
on sdm845 that reserves few context banks and thus kernel views
less than the
From: Jean-Philippe Brucker
[ Upstream commit 29859aeb8a6ea17ba207933a81b6b77b4d4df81a ]
When run on a 64-bit system in selftest, the v7s driver may obtain page
table with physical addresses larger than 32-bit. Level-2 tables are 1KB
and are are allocated with slab, which doesn't accept the
From: Jean-Philippe Brucker
[ Upstream commit 29859aeb8a6ea17ba207933a81b6b77b4d4df81a ]
When run on a 64-bit system in selftest, the v7s driver may obtain page
table with physical addresses larger than 32-bit. Level-2 tables are 1KB
and are are allocated with slab, which doesn't accept the
From: "Erich E. Hoover"
[ Upstream commit 9a7faac3650216112e034b157289bf1a48a99e2d ]
Commit ff3f0789b3dc ("usb: dwc3: use BIT() macro where possible")
changed DWC3_DEPCFG_STREAM_EVENT_EN from bit 13 to bit 12.
Spotted this cleanup typo while looking at diffs between 4.9.35 and
4.14.16 for a
From: "Erich E. Hoover"
[ Upstream commit 9a7faac3650216112e034b157289bf1a48a99e2d ]
Commit ff3f0789b3dc ("usb: dwc3: use BIT() macro where possible")
changed DWC3_DEPCFG_STREAM_EVENT_EN from bit 13 to bit 12.
Spotted this cleanup typo while looking at diffs between 4.9.35 and
4.14.16 for a
Commit ca917f9fe1a0fab added use of usleep_range() but not
the corresponding "include ". The result is
with Chrome OS won't build because warnings are forced
to be errors:
mnt/host/source/src/third_party/kernel/v4.4/sound/soc/codecs/max98373.c:734:2:
error: implicit declaration of function
Commit ca917f9fe1a0fab added use of usleep_range() but not
the corresponding "include ". The result is
with Chrome OS won't build because warnings are forced
to be errors:
mnt/host/source/src/third_party/kernel/v4.4/sound/soc/codecs/max98373.c:734:2:
error: implicit declaration of function
On Tue, Sep 04, 2018 at 12:43:56PM -0400, Steven Rostedt wrote:
>On Sun, 2 Sep 2018 13:03:43 +
>Sasha Levin wrote:
>
>> [
>> Note, this only fixes the symptom. The real fix was not to call
>> this function when tracing_on was already one. But this still makes
>> the code more robust, so
On Tue, Sep 04, 2018 at 12:43:56PM -0400, Steven Rostedt wrote:
>On Sun, 2 Sep 2018 13:03:43 +
>Sasha Levin wrote:
>
>> [
>> Note, this only fixes the symptom. The real fix was not to call
>> this function when tracing_on was already one. But this still makes
>> the code more robust, so
On Mon, Sep 03, 2018 at 12:16:26PM +0100, Mark Brown wrote:
>On Sun, Sep 02, 2018 at 01:03:55PM +, Sasha Levin wrote:
>> From: Akshu Agrawal
>>
>> [ Upstream commit 9fb4c2bf130b922c77c16a8368732699799c40de ]
>>
>> Take into account the base delay set in pointer callback.
>>
>> There are cases
On Mon, Sep 03, 2018 at 12:16:26PM +0100, Mark Brown wrote:
>On Sun, Sep 02, 2018 at 01:03:55PM +, Sasha Levin wrote:
>> From: Akshu Agrawal
>>
>> [ Upstream commit 9fb4c2bf130b922c77c16a8368732699799c40de ]
>>
>> Take into account the base delay set in pointer callback.
>>
>> There are cases
On Mon, Sep 03, 2018 at 09:16:32AM +0200, Sebastian Andrzej Siewior wrote:
>On 2018-09-02 13:03:27 [+], Sasha Levin wrote:
>> From: Sebastian Andrzej Siewior
>>
>> [ Upstream commit 320905baa1dbddd3991c287432176d536e1d5b79 ]
>>
>> The USB completion callback does not disable interrupts while
On Mon, Sep 03, 2018 at 09:16:32AM +0200, Sebastian Andrzej Siewior wrote:
>On 2018-09-02 13:03:27 [+], Sasha Levin wrote:
>> From: Sebastian Andrzej Siewior
>>
>> [ Upstream commit 320905baa1dbddd3991c287432176d536e1d5b79 ]
>>
>> The USB completion callback does not disable interrupts while
On Sat, 2018-08-04 at 11:01 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Xiao Liang
>
> [ Upstream commit 822fb18a82abaf4ee7058793d95d340f5dab7bfc ]
>
> When loading module manually, after call
On Sat, 2018-08-04 at 11:01 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Xiao Liang
>
> [ Upstream commit 822fb18a82abaf4ee7058793d95d340f5dab7bfc ]
>
> When loading module manually, after call
On 09/06/2018 07:09 AM, Quentin Perret wrote:
Hi Dietmar,
On Wednesday 05 Sep 2018 at 23:56:43 (-0700), Dietmar Eggemann wrote:
On 08/20/2018 02:44 AM, Quentin Perret wrote:
Expose the Energy Model (read-only) of all performance domains in sysfs
for convenience. To do so, add a kobject to the
On 09/06/2018 07:09 AM, Quentin Perret wrote:
Hi Dietmar,
On Wednesday 05 Sep 2018 at 23:56:43 (-0700), Dietmar Eggemann wrote:
On 08/20/2018 02:44 AM, Quentin Perret wrote:
Expose the Energy Model (read-only) of all performance domains in sysfs
for convenience. To do so, add a kobject to the
Hi Charles,
I love your patch! Yet something to improve:
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Charles,
I love your patch! Yet something to improve:
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 09/06/2018 02:29 AM, Quentin Perret wrote:
Hi Dietmar,
On Wednesday 05 Sep 2018 at 23:06:38 (-0700), Dietmar Eggemann wrote:
On 08/20/2018 02:44 AM, Quentin Perret wrote:
In order to ensure a minimal performance impact on non-energy-aware
systems, introduce a static_key guarding the access
On 09/06/2018 02:29 AM, Quentin Perret wrote:
Hi Dietmar,
On Wednesday 05 Sep 2018 at 23:06:38 (-0700), Dietmar Eggemann wrote:
On 08/20/2018 02:44 AM, Quentin Perret wrote:
In order to ensure a minimal performance impact on non-energy-aware
systems, introduce a static_key guarding the access
The pinctrl properties on the IOMUXC node get overwritten by the
carrier board level device tree, hence the pinctrl_reset_moci
pinctrl does not get applied.
Associate the pinctrl_reset_moci pinctrl with the PCIe node where
we also make use of the pin as a reset GPIO.
Since the pin is muxed as a
The pinctrl properties on the IOMUXC node get overwritten by the
carrier board level device tree, hence the pinctrl_reset_moci
pinctrl does not get applied.
Associate the pinctrl_reset_moci pinctrl with the PCIe node where
we also make use of the pin as a reset GPIO.
Since the pin is muxed as a
From: Randy Dunlap
If there is no System.map file for "make modules_install",
scripts/depmod.sh will silently exit with success, having done
nothing. Since this is an unexpected situation, change it to
report a Warning for the missing file. The behavior is not
changed except for the Warning
From: Randy Dunlap
If there is no System.map file for "make modules_install",
scripts/depmod.sh will silently exit with success, having done
nothing. Since this is an unexpected situation, change it to
report a Warning for the missing file. The behavior is not
changed except for the Warning
Hi Peter,
On 9/6/2018 7:47 AM, Peter Zijlstra wrote:
> On Thu, Aug 16, 2018 at 01:16:07PM -0700, Reinette Chatre wrote:
>
>> +static inline int x86_perf_rdpmc_ctr_get(struct perf_event *event)
>> +{
>> +lockdep_assert_irqs_disabled();
>> +
>> +return IS_ERR_OR_NULL(event) ? -1 :
Hi Peter,
On 9/6/2018 7:47 AM, Peter Zijlstra wrote:
> On Thu, Aug 16, 2018 at 01:16:07PM -0700, Reinette Chatre wrote:
>
>> +static inline int x86_perf_rdpmc_ctr_get(struct perf_event *event)
>> +{
>> +lockdep_assert_irqs_disabled();
>> +
>> +return IS_ERR_OR_NULL(event) ? -1 :
Hi Juri,
On 08/23/2018 11:54 PM, Juri Lelli wrote:
On 23/08/18 18:52, Dietmar Eggemann wrote:
Hi,
On 08/21/2018 01:54 AM, Miguel de Dios wrote:
On 08/17/2018 11:27 AM, Steve Muckle wrote:
From: John Dias
[...]
I tried to catch this issue on my Arm64 Juno board using pi_test (and a
Hi Juri,
On 08/23/2018 11:54 PM, Juri Lelli wrote:
On 23/08/18 18:52, Dietmar Eggemann wrote:
Hi,
On 08/21/2018 01:54 AM, Miguel de Dios wrote:
On 08/17/2018 11:27 AM, Steve Muckle wrote:
From: John Dias
[...]
I tried to catch this issue on my Arm64 Juno board using pi_test (and a
Hello RT Folks!
I'm pleased to announce the 3.18.121-rt106 stable release.
This release is just an update to the new stable 3.18.121 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Hello RT Folks!
I'm pleased to announce the 3.18.121-rt106 stable release.
This release is just an update to the new stable 3.18.121 version
and no RT specific changes have been made.
You can get this release via the git tree at:
The geni_se_clk_freq_match() has some strange semantics. Specifically
it is defined with two modes:
1. It can find a clock that's an exact multiple of the requested rate
2. It can find a non-exact match but it can't handle multiples then
...but callers should always be able to handle a clock
The function clk_round_rate() is defined to return a "long", not an
"unsigned long". That's because it might return a negative error
code. Change the call in geni_se_clk_tbl_get() to check for errors.
While we're at it, get rid of a useless init of "freq".
NOTE: overall the idea that we should
The geni_se_clk_freq_match() has some strange semantics. Specifically
it is defined with two modes:
1. It can find a clock that's an exact multiple of the requested rate
2. It can find a non-exact match but it can't handle multiples then
...but callers should always be able to handle a clock
The function clk_round_rate() is defined to return a "long", not an
"unsigned long". That's because it might return a negative error
code. Change the call in geni_se_clk_tbl_get() to check for errors.
While we're at it, get rid of a useless init of "freq".
NOTE: overall the idea that we should
On 2018-09-06 06:16, Sai Prakash Ranjan wrote:
On 9/5/2018 4:52 AM, Venkata Narendra Kumar Gutta wrote:
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by:
On 2018-09-06 06:16, Sai Prakash Ranjan wrote:
On 9/5/2018 4:52 AM, Venkata Narendra Kumar Gutta wrote:
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by:
On Fri, 3 Aug 2018 16:40:21 +0200 Jürg Billeter wrote:
> PR_SET_KILLABLE clears the SIGNAL_UNKILLABLE flag. This allows
> CLONE_NEWPID tasks to restore normal signal behavior, opting out of the
> special signal protection for init processes. This prctl does not allow
> setting the
On Fri, 3 Aug 2018 16:40:21 +0200 Jürg Billeter wrote:
> PR_SET_KILLABLE clears the SIGNAL_UNKILLABLE flag. This allows
> CLONE_NEWPID tasks to restore normal signal behavior, opting out of the
> special signal protection for init processes. This prctl does not allow
> setting the
/for-next]
> > [also build test WARNING on v4.19-rc2 next-20180906]
> > [if your patch is applied to the wrong git tree, please drop us a note to
> > help improve the system]
> >
> > url:
> > https://github.com/0day-ci/linux/commits/Douglas-Anderson/soc-qcom-gen
/for-next]
> > [also build test WARNING on v4.19-rc2 next-20180906]
> > [if your patch is applied to the wrong git tree, please drop us a note to
> > help improve the system]
> >
> > url:
> > https://github.com/0day-ci/linux/commits/Douglas-Anderson/soc-qcom-gen
Hi
On Thu, Sep 6, 2018 at 3:35 PM, kbuild test robot wrote:
> Hi Douglas,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on agross/for-next]
> [also build test WARNING on v4.19-rc2 next-20180906]
> [if your patch is applied to the w
Hi
On Thu, Sep 6, 2018 at 3:35 PM, kbuild test robot wrote:
> Hi Douglas,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on agross/for-next]
> [also build test WARNING on v4.19-rc2 next-20180906]
> [if your patch is applied to the w
Hi Douglas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on agross/for-next]
[also build test WARNING on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Hi Douglas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on agross/for-next]
[also build test WARNING on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
On 2018-09-06 05:38, Sai Prakash Ranjan wrote:
On 9/5/2018 4:52 AM, Venkata Narendra Kumar Gutta wrote:
+static const struct of_device_id qcom_llcc_edac_match_table[] = {
+ { .compatible = "qcom,llcc-edac" },
+ { },
+};
+
Hi Venkata,
Devicetree binding for llcc is updated, but
On 2018-09-06 05:38, Sai Prakash Ranjan wrote:
On 9/5/2018 4:52 AM, Venkata Narendra Kumar Gutta wrote:
+static const struct of_device_id qcom_llcc_edac_match_table[] = {
+ { .compatible = "qcom,llcc-edac" },
+ { },
+};
+
Hi Venkata,
Devicetree binding for llcc is updated, but
Hi Roman,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Roman,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
When a build is run from something like a cron job, the user's $PATH is
rather minimal, of note, not including /usr/sbin in my own case. Because
of that, an automated rpm package build ultimately fails to find
libperf-jvmti.so, because somewhere within the build, this happens...
/bin/sh:
When a build is run from something like a cron job, the user's $PATH is
rather minimal, of note, not including /usr/sbin in my own case. Because
of that, an automated rpm package build ultimately fails to find
libperf-jvmti.so, because somewhere within the build, this happens...
/bin/sh:
Hey Tycho - I'm finally getting around to reviewing this patch set. I
don't have access to previous review comments while I'm doing this
review so I hope I'm not revisiting too many previous discussions.
On 2018-09-06 09:28:55, Tycho Andersen wrote:
> This patch introduces a means for syscalls
Hey Tycho - I'm finally getting around to reviewing this patch set. I
don't have access to previous review comments while I'm doing this
review so I hope I'm not revisiting too many previous discussions.
On 2018-09-06 09:28:55, Tycho Andersen wrote:
> This patch introduces a means for syscalls
Almost all spi drivers assign spi master->dev.of_node from
its parent platform device without additional refcounting.
It seems of_node_get() in pic32_spi_probe() is unnecessary
and there is no corresponding of_node_put().
Found by Linux Driver Verification project (linuxtesting.org).
Almost all spi drivers assign spi master->dev.of_node from
its parent platform device without additional refcounting.
It seems of_node_get() in pic32_spi_probe() is unnecessary
and there is no corresponding of_node_put().
Found by Linux Driver Verification project (linuxtesting.org).
Hi Peter,
On Thu, 6 Sep 2018 12:49:39 +0200 Peter Oberparleiter
wrote:
>
> I've attached a quick fix that should address both problems. I'd
> appreciate if this patch could get some testing before I post proper fix
> patches.
I have added that into linux-next today ... I will let you know this
Hi Peter,
On Thu, 6 Sep 2018 12:49:39 +0200 Peter Oberparleiter
wrote:
>
> I've attached a quick fix that should address both problems. I'd
> appreciate if this patch could get some testing before I post proper fix
> patches.
I have added that into linux-next today ... I will let you know this
On 09/06/2018 03:39 PM, Sean Christopherson wrote:
On Thu, Sep 06, 2018 at 03:20:46PM -0500, Brijesh Singh wrote:
On 09/06/2018 02:47 PM, Sean Christopherson wrote:
...
Yes, the auxiliary array will dumped into the regular .bss when
CONFIG_AMD_MEM_ENCRYPT=n. Typically it will be few k,
On 09/06/2018 03:39 PM, Sean Christopherson wrote:
On Thu, Sep 06, 2018 at 03:20:46PM -0500, Brijesh Singh wrote:
On 09/06/2018 02:47 PM, Sean Christopherson wrote:
...
Yes, the auxiliary array will dumped into the regular .bss when
CONFIG_AMD_MEM_ENCRYPT=n. Typically it will be few k,
On 09/05/2018 12:42 AM, Michal Hocko wrote:
> On Tue 04-09-18 15:59:34, Shuah Khan wrote:
> [...]
>> This will support the following workload requirements:
>>
>> - reserving one or more NUMA memory nodes for class of critical tasks that
>> require
>> guaranteed memory availability.
>> - isolate
On 09/05/2018 12:42 AM, Michal Hocko wrote:
> On Tue 04-09-18 15:59:34, Shuah Khan wrote:
> [...]
>> This will support the following workload requirements:
>>
>> - reserving one or more NUMA memory nodes for class of critical tasks that
>> require
>> guaranteed memory availability.
>> - isolate
It looks like line 352 needs to be indented more.
julia
-- Forwarded message --
Date: Fri, 7 Sep 2018 05:47:25 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: drivers/gpu/drm/amd/display/dc/core/dc_resource.c:352:1-14: code
aligned with following
It looks like line 352 needs to be indented more.
julia
-- Forwarded message --
Date: Fri, 7 Sep 2018 05:47:25 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: drivers/gpu/drm/amd/display/dc/core/dc_resource.c:352:1-14: code
aligned with following
Commit-ID: e2c631ba75a7e727e8db0a9d30a06bfd434adb3a
Gitweb: https://git.kernel.org/tip/e2c631ba75a7e727e8db0a9d30a06bfd434adb3a
Author: Peter Zijlstra
AuthorDate: Wed, 5 Sep 2018 10:41:58 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 6 Sep 2018 23:38:35 +0200
clocksource: Revert
Commit-ID: e2c631ba75a7e727e8db0a9d30a06bfd434adb3a
Gitweb: https://git.kernel.org/tip/e2c631ba75a7e727e8db0a9d30a06bfd434adb3a
Author: Peter Zijlstra
AuthorDate: Wed, 5 Sep 2018 10:41:58 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 6 Sep 2018 23:38:35 +0200
clocksource: Revert
On Thu, Sep 06, 2018 at 08:57:38PM +, Nadav Amit wrote:
> at 1:25 PM, Peter Zijlstra wrote:
>
> > On Thu, Sep 06, 2018 at 07:58:40PM +, Nadav Amit wrote:
> >>> With that CR3 trickery, we can rid ourselves of the text_mutex
> >>> requirement, since concurrent text_poke is 'safe'. That
On Thu, Sep 06, 2018 at 08:57:38PM +, Nadav Amit wrote:
> at 1:25 PM, Peter Zijlstra wrote:
>
> > On Thu, Sep 06, 2018 at 07:58:40PM +, Nadav Amit wrote:
> >>> With that CR3 trickery, we can rid ourselves of the text_mutex
> >>> requirement, since concurrent text_poke is 'safe'. That
On Fri, 7 Sep 2018, Stephen Rothwell wrote:
> Commit
>
> 760902b24960 ("clocksource: Revert "Remove kthread"")
>
> is missing a Signed-off-by from its committer. Reverts are commits, too.
Duh. Fixed.
Thanks for spotting!
tglx
On Fri, 7 Sep 2018, Stephen Rothwell wrote:
> Commit
>
> 760902b24960 ("clocksource: Revert "Remove kthread"")
>
> is missing a Signed-off-by from its committer. Reverts are commits, too.
Duh. Fixed.
Thanks for spotting!
tglx
On Thu, Sep 06, 2018 at 01:37:14PM -0700, Reinette Chatre wrote:
> On 9/6/2018 1:29 PM, Peter Zijlstra wrote:
> > On Thu, Sep 06, 2018 at 01:05:05PM -0700, Reinette Chatre wrote:
> >> When I separate the above into the two functions it just becomes either:
> >>
On Thu, Sep 06, 2018 at 01:37:14PM -0700, Reinette Chatre wrote:
> On 9/6/2018 1:29 PM, Peter Zijlstra wrote:
> > On Thu, Sep 06, 2018 at 01:05:05PM -0700, Reinette Chatre wrote:
> >> When I separate the above into the two functions it just becomes either:
> >>
On 09/05/2018 06:58 PM, Huang, Ying wrote:
> Hi, Christopher,
>
> Christopher Lameter writes:
>
>> On Tue, 4 Sep 2018, Daniel Jordan wrote:
>>
>>> - Promoting huge page usage: With memory sizes becoming ever larger, huge
>>> pages are becoming more and more important to reduce TLB misses and
On 09/05/2018 06:58 PM, Huang, Ying wrote:
> Hi, Christopher,
>
> Christopher Lameter writes:
>
>> On Tue, 4 Sep 2018, Daniel Jordan wrote:
>>
>>> - Promoting huge page usage: With memory sizes becoming ever larger, huge
>>> pages are becoming more and more important to reduce TLB misses and
From: Marcel Ziswiler
This patch enables support to read the ECC level from the NAND flash
using ESMT SLC NAND ID byte 5 information as documented e.g. in the
following data sheet:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/F59L1G81LA(2Y).pdf
Signed-off-by: Marcel Ziswiler
---
From: Marcel Ziswiler
Reorder NAND manufacturer IDs for clarity.
Signed-off-by: Marcel Ziswiler
---
Changes in v2:
- Subject prefix s/nand:/rawnand:/ as well as upper-case: s/nand/NAND/
and s/id/ID/ in the commit log as suggested by Miquèl.
- Reordering the macro definitions too as
From: Marcel Ziswiler
This patch enables support to read the ECC level from the NAND flash
using ESMT SLC NAND ID byte 5 information as documented e.g. in the
following data sheet:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/F59L1G81LA(2Y).pdf
Signed-off-by: Marcel Ziswiler
---
From: Marcel Ziswiler
Reorder NAND manufacturer IDs for clarity.
Signed-off-by: Marcel Ziswiler
---
Changes in v2:
- Subject prefix s/nand:/rawnand:/ as well as upper-case: s/nand/NAND/
and s/id/ID/ in the commit log as suggested by Miquèl.
- Reordering the macro definitions too as
Hi all,
Commit
760902b24960 ("clocksource: Revert "Remove kthread"")
is missing a Signed-off-by from its committer. Reverts are commits, too.
--
Cheers,
Stephen Rothwell
pgpcgkQbAXzRp.pgp
Description: OpenPGP digital signature
Hi all,
Commit
760902b24960 ("clocksource: Revert "Remove kthread"")
is missing a Signed-off-by from its committer. Reverts are commits, too.
--
Cheers,
Stephen Rothwell
pgpcgkQbAXzRp.pgp
Description: OpenPGP digital signature
On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> Hi,
>
> On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> > Add a channel node for the die temperature to the ADC.
> >
> > Signed-off-by: Matthias Kaehlcke
> > Reviewed-by: Douglas Anderson
> > Signed-off-by: Matthias
On Thu, Sep 06, 2018 at 02:10:43PM -0700, Doug Anderson wrote:
> Hi,
>
> On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> > Add a channel node for the die temperature to the ADC.
> >
> > Signed-off-by: Matthias Kaehlcke
> > Reviewed-by: Douglas Anderson
> > Signed-off-by: Matthias
Hi Matthias,
On Wed, Sep 05, 2018 at 08:51:26AM +0200, Mathias Kresin wrote:
> From: Tobias Wolf
>
> Set the PCI controller of_node such that PCI devices can be
> instantiated via device tree.
>
> Signed-off-by: Tobias Wolf
> Signed-off-by: Mathias Kresin
> ---
> arch/mips/pci/pci-rt2880.c
Hi Matthias,
On Wed, Sep 05, 2018 at 08:51:26AM +0200, Mathias Kresin wrote:
> From: Tobias Wolf
>
> Set the PCI controller of_node such that PCI devices can be
> instantiated via device tree.
>
> Signed-off-by: Tobias Wolf
> Signed-off-by: Mathias Kresin
> ---
> arch/mips/pci/pci-rt2880.c
Hi Ding,
On Thu, Sep 06, 2018 at 12:19:19PM +0800, Ding Xiang wrote:
> if device_register return error, iounmap should be called, also iounmap
> need to call before put_device.
>
> Signed-off-by: Ding Xiang
> ---
> arch/mips/txx9/generic/setup.c | 5 ++---
> 1 file changed, 2 insertions(+), 3
Hi Ding,
On Thu, Sep 06, 2018 at 12:19:19PM +0800, Ding Xiang wrote:
> if device_register return error, iounmap should be called, also iounmap
> need to call before put_device.
>
> Signed-off-by: Ding Xiang
> ---
> arch/mips/txx9/generic/setup.c | 5 ++---
> 1 file changed, 2 insertions(+), 3
Hi!
> Add the device tree bindings for the lm3697
> LED driver for backlighting and display.
>
> Signed-off-by: Dan Murphy
> ---
>
> v6 - Fix minor issues - https://lore.kernel.org/patchwork/patch/975387/
>
> v5 - Fix the comment for the example -
>
Hi!
> Add the device tree bindings for the lm3697
> LED driver for backlighting and display.
>
> Signed-off-by: Dan Murphy
> ---
>
> v6 - Fix minor issues - https://lore.kernel.org/patchwork/patch/975387/
>
> v5 - Fix the comment for the example -
>
Hi!
> diff --git a/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> b/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> new file mode 100644
> index 000..d8056d5
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> @@ -0,0 +1,22 @@
> +What:
Hi!
> diff --git a/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> b/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> new file mode 100644
> index 000..d8056d5
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-led-driver-sc27xx
> @@ -0,0 +1,22 @@
> +What:
Hi,
On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> This adds the adc node to pm8998 based on the examples in the
> bindings. It also fixes the order of the included headers.
>
> Signed-off-by: Matthias Kaehlcke
> --
> Changes in v2:
> - removed io-channel-ranges attribute
> ---
>
Hi,
On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> This adds the adc node to pm8998 based on the examples in the
> bindings. It also fixes the order of the included headers.
>
> Signed-off-by: Matthias Kaehlcke
> --
> Changes in v2:
> - removed io-channel-ranges attribute
> ---
>
Hi,
On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> Add a channel node for the die temperature to the ADC.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Douglas Anderson
> Signed-off-by: Matthias Kaehlcke
Double-SoB?
...presumably Andy can remove that when he lands and
Hi,
On Thu, Sep 6, 2018 at 2:04 PM, Matthias Kaehlcke wrote:
> Add a channel node for the die temperature to the ADC.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Douglas Anderson
> Signed-off-by: Matthias Kaehlcke
Double-SoB?
...presumably Andy can remove that when he lands and
The documentation of Qualcomm's SPMI PMIC voltage ADC claims that the
'reg' property consists of two values, the SPMI address and the length
of the controller's registers. However the SPMI bus to which it is added
specifies "#size-cells = <0>;". Remove the controller register length
from the
This series adds the DT node for the QCOM SPMI PMIC5 ADC and a channel
for the die temperature.
The die temperature is going to be used by the temperature alarm driver
(https://lore.kernel.org/patchwork/project/lkml/list/?series=361416).
My understanding is that some of the ADC channels are/can
601 - 700 of 1950 matches
Mail list logo
