Dear kernel developers
I reported a bug at Bugzilla, but Greg Kroah-Hartman pointed me in
mailing lists. Here's my bug report:
Linux has been unbootable for me from 4.18 upwards. Even the fallback
image does not boot. This has not been fixed yet in 4.19-rc3. acpi=off
kernel parameter lets me boot
Dear kernel developers
I reported a bug at Bugzilla, but Greg Kroah-Hartman pointed me in
mailing lists. Here's my bug report:
Linux has been unbootable for me from 4.18 upwards. Even the fallback
image does not boot. This has not been fixed yet in 4.19-rc3. acpi=off
kernel parameter lets me boot
On Fri, Sep 14, 2018 at 05:39:09PM +0530, Akash Gajjar wrote:
> Rockpro64 board is a rockchip RK3399 based board from pine64.org.
> This commit adds initial device tree support for Rockpro64 board.
>
> Signed-off-by: Akash Gajjar
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4
On Fri, Sep 14, 2018 at 05:39:09PM +0530, Akash Gajjar wrote:
> Rockpro64 board is a rockchip RK3399 based board from pine64.org.
> This commit adds initial device tree support for Rockpro64 board.
>
> Signed-off-by: Akash Gajjar
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4
On Sun, 2018-09-16 at 22:19 +0300, Jarkko Sakkinen wrote:
> On Thu, Sep 13, 2018 at 05:45:54PM +0100, David Howells wrote:
> > Jarkko Sakkinen wrote:
> >
> > > David, what do you think?
> >
> > Which David?
> >
> > I think you need to ask James and Mimi since they're the current
> >
On Sun, 2018-09-16 at 22:19 +0300, Jarkko Sakkinen wrote:
> On Thu, Sep 13, 2018 at 05:45:54PM +0100, David Howells wrote:
> > Jarkko Sakkinen wrote:
> >
> > > David, what do you think?
> >
> > Which David?
> >
> > I think you need to ask James and Mimi since they're the current
> >
If hosts provides ops->adma_write_desc, we should not fall back to the
general sdhci_adma_write_desc().
Signed-off-by: Jisheng Zhang
---
Hi Ulf, Adrian,
When I introduced .adma_write_desc, I made a mistake since v4 -- if the host
provide ops->adma_write_desc, we should just call it and don't
If hosts provides ops->adma_write_desc, we should not fall back to the
general sdhci_adma_write_desc().
Signed-off-by: Jisheng Zhang
---
Hi Ulf, Adrian,
When I introduced .adma_write_desc, I made a mistake since v4 -- if the host
provide ops->adma_write_desc, we should just call it and don't
When runtime is not enabled, pm_runtime_get_sync() returns -EACCESS,
the counter will be incremented but the resume callback not called,
so enumeration and charging will not start properly.
To avoid that happen, wait and try again later.
Practically this happens when the device is woken up from
When runtime is not enabled, pm_runtime_get_sync() returns -EACCESS,
the counter will be incremented but the resume callback not called,
so enumeration and charging will not start properly.
To avoid that happen, wait and try again later.
Practically this happens when the device is woken up from
Hi Suren
On Fri, Sep 7, 2018 at 11:58 PM, Suren Baghdasaryan wrote:
> Thanks for the new patchset! Backported to 4.9 and retested on ARMv8 8
> code system running Android. Signals behave as expected reacting to
> memory pressure, no jumps in "total" counters that would indicate an
>
Hi Suren
On Fri, Sep 7, 2018 at 11:58 PM, Suren Baghdasaryan wrote:
> Thanks for the new patchset! Backported to 4.9 and retested on ARMv8 8
> code system running Android. Signals behave as expected reacting to
> memory pressure, no jumps in "total" counters that would indicate an
>
the charging current uses unsigned int variables, if we step back
if the current is still low, we would run into negative which
means setting the target to a huge value.
Better add checks here.
Signed-off-by: Andreas Kemnade
---
drivers/power/supply/twl4030_charger.c | 3 ++-
1 file changed, 2
the charging current uses unsigned int variables, if we step back
if the current is still low, we would run into negative which
means setting the target to a huge value.
Better add checks here.
Signed-off-by: Andreas Kemnade
---
drivers/power/supply/twl4030_charger.c | 3 ++-
1 file changed, 2
On Sun, Sep 16, 2018 at 09:04:04PM -0700, Stefan Agner wrote:
> Hi Greg,
>
> The follow up patch 8b2ded1c94c0 ("block: don't warn when doing fsync
> on read-only devices") should get applied too, since it correctly
> fixes what this patch tried to fix.
Already queueud up, thanks!
greg k-h
On Sun, Sep 16, 2018 at 09:04:04PM -0700, Stefan Agner wrote:
> Hi Greg,
>
> The follow up patch 8b2ded1c94c0 ("block: don't warn when doing fsync
> on read-only devices") should get applied too, since it correctly
> fixes what this patch tried to fix.
Already queueud up, thanks!
greg k-h
On Mon, Sep 17, 2018 at 04:14:55AM +, k...@linuxonhyperv.com wrote:
> From: Vitaly Kuznetsov
>
> 'error' variable is left uninitialized in case we see an unknown operation.
> As we don't immediately return and proceed to pwrite() we need to set it
> to something, HV_E_FAIL sounds good
On Mon, Sep 17, 2018 at 04:14:55AM +, k...@linuxonhyperv.com wrote:
> From: Vitaly Kuznetsov
>
> 'error' variable is left uninitialized in case we see an unknown operation.
> As we don't immediately return and proceed to pwrite() we need to set it
> to something, HV_E_FAIL sounds good
Hey Martin,
Thanks for running these and pointing this out. I've replicated the
results with tcrypt and fixed some issues, and the next patch series
should be a lot closer to what you'd expect, instead of the regression
you noticed. Most of the slowdown happened as a result of over-eager
XSAVEs,
Hey Martin,
Thanks for running these and pointing this out. I've replicated the
results with tcrypt and fixed some issues, and the next patch series
should be a lot closer to what you'd expect, instead of the regression
you noticed. Most of the slowdown happened as a result of over-eager
XSAVEs,
From: Andy Lutomirski
Date: Sun, 16 Sep 2018 21:09:11 -0700
> CRYPTO API
> M: Herbert Xu
> M: "David S. Miller"
> L: linux-cry...@vger.kernel.org
>
> Herbert hasn't replied to any of these submissions. You're the other
> maintainer :)
Herbert is the primary crypto maintainer,
From: Andy Lutomirski
Date: Sun, 16 Sep 2018 21:09:11 -0700
> CRYPTO API
> M: Herbert Xu
> M: "David S. Miller"
> L: linux-cry...@vger.kernel.org
>
> Herbert hasn't replied to any of these submissions. You're the other
> maintainer :)
Herbert is the primary crypto maintainer,
[ This pull request was originally intended for 4.19-rc4, but some
testing hiccups delayed my sending this earlier. Given Linus's
comments, I'm not sure whether PULL requests should be going to Linus
or Greg, so I'm sending it to both. -- Ted ]
The following changes since commit
[ This pull request was originally intended for 4.19-rc4, but some
testing hiccups delayed my sending this earlier. Given Linus's
comments, I'm not sure whether PULL requests should be going to Linus
or Greg, so I'm sending it to both. -- Ted ]
The following changes since commit
Move the idmap_pg_dir/tramp_pg_dir/reserved_ttbr0/swapper_pg_dir to
the rodata section. When the kernel is initialized, the
idmap_pg_dir, tramp_pg_dir and reserved_ttbr0 will not change. And
it's safe to move them to rodata section.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/vmlinux.lds.S |
Move the idmap_pg_dir/tramp_pg_dir/reserved_ttbr0/swapper_pg_dir to
the rodata section. When the kernel is initialized, the
idmap_pg_dir, tramp_pg_dir and reserved_ttbr0 will not change. And
it's safe to move them to rodata section.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/vmlinux.lds.S |
As the initial page table is created in the init_pg_dir, we can set
up the final page table directly in the swapper_pg_dir. And it only
contains the top level page table, so we can reduce it to a page
size.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/vmlinux.lds.S | 2 +-
arch/arm64/mm/mmu.c
To make the swapper_pg_dir read only, we will move it to the rodata
section. And force the kernel to set up the initial page table in
the init_pg_dir. After generating all levels page table, we copy
only the top level into the swapper_pg_dir during paging_init().
In this patch, just add the
The kernel will set up the initial page table in the init_pg_dir.
However, it will create the final page table in the swapper_pg_dir
during the initialization process. We need to let __enable_mmu()
know which page table to use.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/head.S | 19
Version 5 changes:
1. Correct spelling and indentation errors[1].
2. Update init_mm.pgd by assembly[2].
3. Simplify set_p?d() by introducing set_swapper_pgd()[3].
4. Reduce unnecessary tlbi for every write to swapper_pg_dir
during paging_init()[3].
v4:
Since we will move the swapper_pg_dir to rodata section, we need a
way to update it. The fixmap can handle it. When the swapper_pg_dir
needs to be updated, we map it dynamically. The map will be
canceled after the update is complete. In this way, we can defend
against KSMA(Kernel Space Mirror
Create the initial page table in the init_pg_dir. And update the
init_mm.pgd to make sure that pgd_offset_k() works correctly. When
the final page table is created, we redirect the init_mm.pgd to the
swapper_pg_dir.
Signed-off-by: Jun Yao
---
arch/arm64/include/asm/pgtable.h | 2 ++
As the initial page table is created in the init_pg_dir, we can set
up the final page table directly in the swapper_pg_dir. And it only
contains the top level page table, so we can reduce it to a page
size.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/vmlinux.lds.S | 2 +-
arch/arm64/mm/mmu.c
To make the swapper_pg_dir read only, we will move it to the rodata
section. And force the kernel to set up the initial page table in
the init_pg_dir. After generating all levels page table, we copy
only the top level into the swapper_pg_dir during paging_init().
In this patch, just add the
The kernel will set up the initial page table in the init_pg_dir.
However, it will create the final page table in the swapper_pg_dir
during the initialization process. We need to let __enable_mmu()
know which page table to use.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/head.S | 19
Version 5 changes:
1. Correct spelling and indentation errors[1].
2. Update init_mm.pgd by assembly[2].
3. Simplify set_p?d() by introducing set_swapper_pgd()[3].
4. Reduce unnecessary tlbi for every write to swapper_pg_dir
during paging_init()[3].
v4:
Since we will move the swapper_pg_dir to rodata section, we need a
way to update it. The fixmap can handle it. When the swapper_pg_dir
needs to be updated, we map it dynamically. The map will be
canceled after the update is complete. In this way, we can defend
against KSMA(Kernel Space Mirror
Create the initial page table in the init_pg_dir. And update the
init_mm.pgd to make sure that pgd_offset_k() works correctly. When
the final page table is created, we redirect the init_mm.pgd to the
swapper_pg_dir.
Signed-off-by: Jun Yao
---
arch/arm64/include/asm/pgtable.h | 2 ++
On Sun, Sep 16, 2018 at 10:35:17PM +0530, Pintu Kumar wrote:
> On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport wrote:
> >
> > On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
> > > Hi All,
> > >
> > > Board: Hikey620 ARM64
> > > Kernel: 4.9.20
> > >
> > > I am trying to verify KSM
On Sun, Sep 16, 2018 at 10:35:17PM +0530, Pintu Kumar wrote:
> On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport wrote:
> >
> > On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
> > > Hi All,
> > >
> > > Board: Hikey620 ARM64
> > > Kernel: 4.9.20
> > >
> > > I am trying to verify KSM
From: Vitaly Kuznetsov
'error' variable is left uninitialized in case we see an unknown operation.
As we don't immediately return and proceed to pwrite() we need to set it
to something, HV_E_FAIL sounds good enough.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
---
From: Dexuan Cui
With CONFIG_DEBUG_PREEMPT=y, I always see this warning:
BUG: using smp_processor_id() in preemptible []
Fix the false warning by using get/put_cpu().
Here vmbus_connect() sends a message to the host and waits for the
host's response. The host will deliver the response
From: Vitaly Kuznetsov
'error' variable is left uninitialized in case we see an unknown operation.
As we don't immediately return and proceed to pwrite() we need to set it
to something, HV_E_FAIL sounds good enough.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Srinivasan
---
From: Dexuan Cui
With CONFIG_DEBUG_PREEMPT=y, I always see this warning:
BUG: using smp_processor_id() in preemptible []
Fix the false warning by using get/put_cpu().
Here vmbus_connect() sends a message to the host and waits for the
host's response. The host will deliver the response
From: "K. Y. Srinivasan"
Some miscellaneous fixes.
Dexuan Cui (1):
Drivers: hv: vmbus: Use get/put_cpu() in vmbus_connect()
Vitaly Kuznetsov (1):
tools: hv: fcopy: set 'error' in case an unknown operation was
requested
drivers/hv/connection.c| 8 +---
From: "K. Y. Srinivasan"
Some miscellaneous fixes.
Dexuan Cui (1):
Drivers: hv: vmbus: Use get/put_cpu() in vmbus_connect()
Vitaly Kuznetsov (1):
tools: hv: fcopy: set 'error' in case an unknown operation was
requested
drivers/hv/connection.c| 8 +---
On Tue, Sep 11, 2018 at 4:57 PM David Miller wrote:
>
> From: Andrew Lunn
> Date: Wed, 12 Sep 2018 01:30:15 +0200
>
> > Just as an FYI:
> >
> > 1) I don't think anybody in netdev has taken a serious look at the
> > network code yet. There is little point until the controversial part
> > of the
On Tue, Sep 11, 2018 at 4:57 PM David Miller wrote:
>
> From: Andrew Lunn
> Date: Wed, 12 Sep 2018 01:30:15 +0200
>
> > Just as an FYI:
> >
> > 1) I don't think anybody in netdev has taken a serious look at the
> > network code yet. There is little point until the controversial part
> > of the
Hi Greg,
The follow up patch 8b2ded1c94c0 ("block: don't warn when doing fsync on
read-only devices") should get applied too, since it correctly fixes what this
patch tried to fix.
--
Stefan
On 13.09.2018 06:30, Greg Kroah-Hartman wrote:
> 4.18-stable review patch. If anyone has any
Hi Greg,
The follow up patch 8b2ded1c94c0 ("block: don't warn when doing fsync on
read-only devices") should get applied too, since it correctly fixes what this
patch tried to fix.
--
Stefan
On 13.09.2018 06:30, Greg Kroah-Hartman wrote:
> 4.18-stable review patch. If anyone has any
Hi Sebastian,
On 16 September 2018 at 22:35, Sebastian Reichel
wrote:
> Hi,
>
> Looks mostly good. I have a couple of comments in addition to the
> ones from the binding about using battery_info for the OCV ->
> capacity mapping.
OK.
>> +
>> +static int sc27xx_fgu_get_vbat_vol(struct
Hi Sebastian,
On 16 September 2018 at 22:35, Sebastian Reichel
wrote:
> Hi,
>
> Looks mostly good. I have a couple of comments in addition to the
> ones from the binding about using battery_info for the OCV ->
> capacity mapping.
OK.
>> +
>> +static int sc27xx_fgu_get_vbat_vol(struct
On 2018/9/15 19:35, Andreas Schwab wrote:
> On Sep 15 2018, YueHaibing wrote:
>
>> Comparing an int to a size, which is unsigned, causes the int to become
>> unsigned, giving the wrong result. kernel_sendmsg can return a negative
>> error code.
>>
>> Signed-off-by: YueHaibing
>> ---
>>
On 2018/9/15 19:35, Andreas Schwab wrote:
> On Sep 15 2018, YueHaibing wrote:
>
>> Comparing an int to a size, which is unsigned, causes the int to become
>> unsigned, giving the wrong result. kernel_sendmsg can return a negative
>> error code.
>>
>> Signed-off-by: YueHaibing
>> ---
>>
Hi Daniel,
Thank you for your review comments.
I will address all your comments in next patch set.
Regards,
Srinath.
On Fri, Sep 14, 2018 at 7:50 PM, Daniel Lezcano
wrote:
> On 09/08/2018 14:54, Srinath Mannam wrote:
>> From: Pramod Kumar
>>
>> Adds stingray thermal driver to monitor six
>>
Hi Daniel,
Thank you for your review comments.
I will address all your comments in next patch set.
Regards,
Srinath.
On Fri, Sep 14, 2018 at 7:50 PM, Daniel Lezcano
wrote:
> On 09/08/2018 14:54, Srinath Mannam wrote:
>> From: Pramod Kumar
>>
>> Adds stingray thermal driver to monitor six
>>
Hi Sebastian,
On 16 September 2018 at 21:57, Sebastian Reichel
wrote:
> Hi,
>
> On Wed, Sep 12, 2018 at 03:29:38PM +0800, Baolin Wang wrote:
>> This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
>> fuel gauge unit device, which is used to calculate the battery capacity.
Hi Sebastian,
On 16 September 2018 at 21:57, Sebastian Reichel
wrote:
> Hi,
>
> On Wed, Sep 12, 2018 at 03:29:38PM +0800, Baolin Wang wrote:
>> This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
>> fuel gauge unit device, which is used to calculate the battery capacity.
Hi,
On Sep 17 2018 09:34, Randy Dunlap wrote:
From: Randy Dunlap
Fix kernel-doc markup warnings in soundwire/stream.rst:
rc4/Documentation/driver-api/soundwire/stream.rst:177: WARNING: Explicit markup
ends without a blank line; unexpected unindent.
Hi,
On Sep 17 2018 09:34, Randy Dunlap wrote:
From: Randy Dunlap
Fix kernel-doc markup warnings in soundwire/stream.rst:
rc4/Documentation/driver-api/soundwire/stream.rst:177: WARNING: Explicit markup
ends without a blank line; unexpected unindent.
From: Matt Ranostay
[ Upstream commit ce054546cc2c26891cefa2f284d90d93b52205de ]
ADC channel 0 photodiode detects both infrared + visible light,
but ADC channel 1 just detects infrared. However, the latter is a bit
more sensitive in that range so complete darkness or low light causes
a error
From: Matt Ranostay
[ Upstream commit ce054546cc2c26891cefa2f284d90d93b52205de ]
ADC channel 0 photodiode detects both infrared + visible light,
but ADC channel 1 just detects infrared. However, the latter is a bit
more sensitive in that range so complete darkness or low light causes
a error
From: Dan Carpenter
[ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ]
The problem is that if get_user_pages_fast() fails and returns a
negative error code, it gets type promoted to a high positive value and
treated as a success.
Fixes: 06164d2b72aa ("VMCI: queue pairs
From: Dan Williams
[ Upstream commit 3b6c62f363a19ce82bf378187ab97c9dc01e3927 ]
Without this change the distance table calculation for emulated nodes
may use the wrong numa node and report an incorrect distance.
Signed-off-by: Dan Williams
Cc: David Rientjes
Cc: Linus Torvalds
Cc: Peter
From: Dan Carpenter
[ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ]
The problem is that if get_user_pages_fast() fails and returns a
negative error code, it gets type promoted to a high positive value and
treated as a success.
Fixes: 06164d2b72aa ("VMCI: queue pairs
From: Dan Williams
[ Upstream commit 3b6c62f363a19ce82bf378187ab97c9dc01e3927 ]
Without this change the distance table calculation for emulated nodes
may use the wrong numa node and report an incorrect distance.
Signed-off-by: Dan Williams
Cc: David Rientjes
Cc: Linus Torvalds
Cc: Peter
From: Johan Hovold
[ Upstream commit d5b9653dd2bb7a2b1c8cc783c5d3b607bbb6b271 ]
Make sure to enable the clock before registering regions and exporting
partitions to user space at which point we must be prepared for I/O.
Fixes: ee895ccdf776 ("misc: sram: fix enabled clock leak on error path")
From: Uwe Kleine-König
[ Upstream commit e890591413819eeb604207ad3261ba617b2ec0bb ]
When a siox master device is registered a kthread is created that is
only started when triggered by userspace. So this thread might be in
TASK_UNINTERRUPTIBLE state for long and trigger a warning
[
+ DT maintainers
On Mon, 17 Sep 2018 11:29:49 +0800
Jisheng Zhang wrote:
> On some platforms, the sda/scl pins are muxed with gpio functions, so
> they could be used for recovery. Select the gpio/default pin function
> when prepare/unprepare recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
>
From: Johan Hovold
[ Upstream commit d5b9653dd2bb7a2b1c8cc783c5d3b607bbb6b271 ]
Make sure to enable the clock before registering regions and exporting
partitions to user space at which point we must be prepared for I/O.
Fixes: ee895ccdf776 ("misc: sram: fix enabled clock leak on error path")
From: Uwe Kleine-König
[ Upstream commit e890591413819eeb604207ad3261ba617b2ec0bb ]
When a siox master device is registered a kthread is created that is
only started when triggered by userspace. So this thread might be in
TASK_UNINTERRUPTIBLE state for long and trigger a warning
[
+ DT maintainers
On Mon, 17 Sep 2018 11:29:49 +0800
Jisheng Zhang wrote:
> On some platforms, the sda/scl pins are muxed with gpio functions, so
> they could be used for recovery. Select the gpio/default pin function
> when prepare/unprepare recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
>
From: Yunsheng Lin
[ Upstream commit d7099d15478e89edb9bc6c6e3ab4cd341884a367 ]
The napi_alloc_skb is excepted to be called under the
non-preemptible code path when it is called by hns3_clean_rx_ring
during loopback selftest, otherwise the below warning will be
logged:
[ 92.420780] BUG:
From: Zhen Lei
[ Upstream commit 3c120143f584360a13614787e23ae2cdcb5e5ccd ]
Although the mapping has already been removed in the page table, it maybe
still exist in TLB. Suppose the freed IOVAs is reused by others before the
flush operation completed, the new user can not correctly access to
From: Johan Hovold
[ Upstream commit a420b5d939ee58f1d950f0ea782834056520aeaa ]
Make sure to return -EIO in case of a short modem-status read request.
While at it, split the debug message to not include the (zeroed)
transfer-buffer content in case of errors.
Fixes: 1da177e4c3f4
From: Yunsheng Lin
[ Upstream commit d7099d15478e89edb9bc6c6e3ab4cd341884a367 ]
The napi_alloc_skb is excepted to be called under the
non-preemptible code path when it is called by hns3_clean_rx_ring
during loopback selftest, otherwise the below warning will be
logged:
[ 92.420780] BUG:
From: Zhen Lei
[ Upstream commit 3c120143f584360a13614787e23ae2cdcb5e5ccd ]
Although the mapping has already been removed in the page table, it maybe
still exist in TLB. Suppose the freed IOVAs is reused by others before the
flush operation completed, the new user can not correctly access to
From: Johan Hovold
[ Upstream commit a420b5d939ee58f1d950f0ea782834056520aeaa ]
Make sure to return -EIO in case of a short modem-status read request.
While at it, split the debug message to not include the (zeroed)
transfer-buffer content in case of errors.
Fixes: 1da177e4c3f4
From: Jian-Hong Pan
[ Upstream commit 45ae68b8cfc25bdbffc11248001c47ab1b76ff6e ]
Without this patch we cannot turn on the Bluethooth adapter on HP
14-bs007la.
T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P:
From: Hans de Goede
[ Upstream commit f2a42595f0865886a2d40524b0e9d15600848670 ]
We should look at val which contains the value read from the register,
not ret which is always 0 on a successful read.
Signed-off-by: Hans de Goede
Fixes: eac53b3664f59 ("power: supply: axp288_charger: Drop
From: Anton Vasilyev
[ Upstream commit 11b71782c1d10d9bccc31825cf84291cd7588a1e ]
hwarc_probe() allocates memory for hwarc, but does not free it
if uwb_rc_add() or hwarc_get_version() fail.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Vasilyev
+ DT maintainers
On Mon, 17 Sep 2018 11:28:30 +0800
Jisheng Zhang wrote:
> Document the pinctrl property for bus recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/i2c/i2c-designware.txt | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git
From: Jian-Hong Pan
[ Upstream commit 45ae68b8cfc25bdbffc11248001c47ab1b76ff6e ]
Without this patch we cannot turn on the Bluethooth adapter on HP
14-bs007la.
T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P:
From: Hans de Goede
[ Upstream commit f2a42595f0865886a2d40524b0e9d15600848670 ]
We should look at val which contains the value read from the register,
not ret which is always 0 on a successful read.
Signed-off-by: Hans de Goede
Fixes: eac53b3664f59 ("power: supply: axp288_charger: Drop
From: Anton Vasilyev
[ Upstream commit 11b71782c1d10d9bccc31825cf84291cd7588a1e ]
hwarc_probe() allocates memory for hwarc, but does not free it
if uwb_rc_add() or hwarc_get_version() fail.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Vasilyev
+ DT maintainers
On Mon, 17 Sep 2018 11:28:30 +0800
Jisheng Zhang wrote:
> Document the pinctrl property for bus recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/i2c/i2c-designware.txt | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git
+ DT maintainers
On Mon, 17 Sep 2018 11:27:41 +0800
Jisheng Zhang wrote:
> Document the scl-gpios and sda-gpios properties for bus recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/i2c/i2c-designware.txt | 6 ++
> 1 file changed, 6 insertions(+)
>
>
From: Benjamin Tissoires
[ Upstream commit 3ffa6583e24e1ad1abab836d24bfc9d2308074e5 ]
If a device gets removed right after having registered a power_supply node,
we might enter in a deadlock between the remove call (that has a lock on
the parent device) and the deferred register work.
Allow
From: Colin Ian King
[ Upstream commit c5fae4f4fd28189b1062fb8ef7b21fec37cb8b17 ]
Currently the check on error return from the call to rtsx_write_register
is checking the error status from the previous call. Fix this by adding
in the missing assignment of retval.
Detected by CoverityScan,
+ DT maintainers
On Mon, 17 Sep 2018 11:27:41 +0800
Jisheng Zhang wrote:
> Document the scl-gpios and sda-gpios properties for bus recovery.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/i2c/i2c-designware.txt | 6 ++
> 1 file changed, 6 insertions(+)
>
>
From: Benjamin Tissoires
[ Upstream commit 3ffa6583e24e1ad1abab836d24bfc9d2308074e5 ]
If a device gets removed right after having registered a power_supply node,
we might enter in a deadlock between the remove call (that has a lock on
the parent device) and the deferred register work.
Allow
From: Colin Ian King
[ Upstream commit c5fae4f4fd28189b1062fb8ef7b21fec37cb8b17 ]
Currently the check on error return from the call to rtsx_write_register
is checking the error status from the previous call. Fix this by adding
in the missing assignment of retval.
Detected by CoverityScan,
From: Vasily Gorbik
[ Upstream commit 5bedf8aa03c28cb8dc98bdd32a41b66d8f7d3eaa ]
Since proc_dointvec does not perform value range control,
proc_dointvec_minmax should be used to limit value range, which is
clearly intended here, as the internal representation of the value:
unsigned int
From: Niklas Cassel
[ Upstream commit 379521462e4add27f3514da8e4ab1fd7a54fe1c7 ]
Fixes the following splat during boot:
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:747
in_atomic(): 1, irqs_disabled(): 128, pid: 77, name: kworker/2:1
4 locks held by
From: Vasily Gorbik
[ Upstream commit 5bedf8aa03c28cb8dc98bdd32a41b66d8f7d3eaa ]
Since proc_dointvec does not perform value range control,
proc_dointvec_minmax should be used to limit value range, which is
clearly intended here, as the internal representation of the value:
unsigned int
From: Niklas Cassel
[ Upstream commit 379521462e4add27f3514da8e4ab1fd7a54fe1c7 ]
Fixes the following splat during boot:
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:747
in_atomic(): 1, irqs_disabled(): 128, pid: 77, name: kworker/2:1
4 locks held by
From: Dan Carpenter
[ Upstream commit c1dfc0114c901b4f46c85ceff0491debf2b2a2ec ]
The srq->swq[] is allocated in bnxt_qplib_create_srq(). It has
srq->hwq.max_elements elements so these tests should be > instead of >=
or we might go beyond the end of the array.
Fixes: 1ac5a4047975
From: Sylwester Nawrocki
[ Upstream commit 7c1b9a5aeed91bef98988ac0fcf38c8c1f4f9a3a ]
This patch fixes potential NULL pointer dereference as indicated
by the following static checker warning:
drivers/media/platform/exynos4-is/fimc-isp-video.c:408
isp_video_try_fmt_mplane()
error: NULL
From: Tarick Bedeir
[ Upstream commit f1228867adaf8890826f2b59e4caddb1c5cc2df7 ]
rdma_ah_find_type() can reach into ib_device->port_immutable with a
potentially out-of-bounds port number, so check that the port number is
valid first.
Fixes: 44c58487d51a ("IB/core: Define 'ib' and 'roce'
From: Dan Carpenter
[ Upstream commit c1dfc0114c901b4f46c85ceff0491debf2b2a2ec ]
The srq->swq[] is allocated in bnxt_qplib_create_srq(). It has
srq->hwq.max_elements elements so these tests should be > instead of >=
or we might go beyond the end of the array.
Fixes: 1ac5a4047975
1 - 100 of 1082 matches
Mail list logo
