Hi all,
Changes since 20180925:
Dropped trees: xarray, ida (temporarily)
The pci tree gained a build failure for which I applied a patch.
The vfio tree gained a conflict against the vfs tree.
Non-merge commits (relative to Linus' tree): 5701
6126 files changed, 279602 insertions(+), 123599
Hi all,
Changes since 20180925:
Dropped trees: xarray, ida (temporarily)
The pci tree gained a build failure for which I applied a patch.
The vfio tree gained a conflict against the vfs tree.
Non-merge commits (relative to Linus' tree): 5701
6126 files changed, 279602 insertions(+), 123599
On Mon, Sep 17, 2018 at 7:58 PM Anup Patel wrote:
>
> On Mon, Sep 17, 2018 at 7:44 PM Christoph Hellwig wrote:
> >
> > On Mon, Sep 10, 2018 at 10:08:58PM +0530, Anup Patel wrote:
> > > > They could in theory IFF someone actually get the use case through
> > > > the riscv privileged spec working
On Mon, Sep 17, 2018 at 7:58 PM Anup Patel wrote:
>
> On Mon, Sep 17, 2018 at 7:44 PM Christoph Hellwig wrote:
> >
> > On Mon, Sep 10, 2018 at 10:08:58PM +0530, Anup Patel wrote:
> > > > They could in theory IFF someone actually get the use case through
> > > > the riscv privileged spec working
Clang warns that the acpi_id declaration is not going to be emitted
in the final assembly:
drivers/staging/rtl8723bs/os_dep/sdio_intf.c:25:36: warning: variable
'acpi_ids' is not needed and will not be emitted
[-Wunneeded-internal-declaration]
static const struct acpi_device_id acpi_ids[] = {
Clang warns that the acpi_id declaration is not going to be emitted
in the final assembly:
drivers/staging/rtl8723bs/os_dep/sdio_intf.c:25:36: warning: variable
'acpi_ids' is not needed and will not be emitted
[-Wunneeded-internal-declaration]
static const struct acpi_device_id acpi_ids[] = {
On Wed, Sep 26, 2018 at 12:01:53AM -0300, Rafael Tinoco wrote:
> Greg,
>
> > > > This is the start of the stable review cycle for the 4.14.72 release.
> > > > There are 173 patches in this series, all will be posted as a response
> > > > to this one. If anyone has any issues with these being
On Wed, Sep 26, 2018 at 12:01:53AM -0300, Rafael Tinoco wrote:
> Greg,
>
> > > > This is the start of the stable review cycle for the 4.14.72 release.
> > > > There are 173 patches in this series, all will be posted as a response
> > > > to this one. If anyone has any issues with these being
Hi, Ryder:
On Wed, 2018-09-26 at 10:38 +0800, Ryder Lee wrote:
> On Wed, 2018-09-26 at 09:37 +0800, CK Hu wrote:
> > Hi, Ryder:
> >
> > On Wed, 2018-09-05 at 22:09 +0800, Ryder Lee wrote:
> > > Add display subsystem related device nodes for MT7623.
> > >
> > > Cc: CK Hu
> > > Signed-off-by:
Clang warns that mlxplat_mlxcpld_msn201x_items is not going to be
emitted in the final assembly because it's only used in ARRAY_SIZE right
now, which is a compile time evaluation since the array's size is known.
drivers/platform/x86/mlx-platform.c:555:32: warning: variable
Hi, Ryder:
On Wed, 2018-09-26 at 10:38 +0800, Ryder Lee wrote:
> On Wed, 2018-09-26 at 09:37 +0800, CK Hu wrote:
> > Hi, Ryder:
> >
> > On Wed, 2018-09-05 at 22:09 +0800, Ryder Lee wrote:
> > > Add display subsystem related device nodes for MT7623.
> > >
> > > Cc: CK Hu
> > > Signed-off-by:
Clang warns that mlxplat_mlxcpld_msn201x_items is not going to be
emitted in the final assembly because it's only used in ARRAY_SIZE right
now, which is a compile time evaluation since the array's size is known.
drivers/platform/x86/mlx-platform.c:555:32: warning: variable
Hi Bjorn,
After merging the pci tree, today's linux-next build (powerpc allnoconfig)
failed like this:
ld: drivers/pci/pci.o: in function `pci_bus_error_reset':
pci.c:(.text+0x5fba): undefined reference to `pci_slot_mutex'
ld: pci.c:(.text+0x5fc2): undefined reference to `pci_slot_mutex'
Caused
Hi Bjorn,
After merging the pci tree, today's linux-next build (powerpc allnoconfig)
failed like this:
ld: drivers/pci/pci.o: in function `pci_bus_error_reset':
pci.c:(.text+0x5fba): undefined reference to `pci_slot_mutex'
ld: pci.c:(.text+0x5fc2): undefined reference to `pci_slot_mutex'
Caused
On 9/18/18 2:58 AM, Jan Kara wrote:
> On Tue 18-09-18 02:35:43, Jann Horn wrote:
>> On Tue, Sep 18, 2018 at 2:05 AM Hugh Dickins wrote:
>
> Thanks for CC Hugh.
>
>>> On Mon, 17 Sep 2018, Jann Horn wrote:
>>>
>>
>> Makes sense, I guess.
>>
>> I wonder whether there's a concise way to express
On 9/18/18 2:58 AM, Jan Kara wrote:
> On Tue 18-09-18 02:35:43, Jann Horn wrote:
>> On Tue, Sep 18, 2018 at 2:05 AM Hugh Dickins wrote:
>
> Thanks for CC Hugh.
>
>>> On Mon, 17 Sep 2018, Jann Horn wrote:
>>>
>>
>> Makes sense, I guess.
>>
>> I wonder whether there's a concise way to express
e.
Signed-off-by: Chen-Yu Tsai
---
This was working on linux-next 20180910, but now fails on linux-next
20180925, with the following error messages:
m25p80 spi0.0: error -22 reading 9f
m25p80: probe of spi0.0 failed with error -2
Reverting the spi/for-next branch makes it work again:
e.
Signed-off-by: Chen-Yu Tsai
---
This was working on linux-next 20180910, but now fails on linux-next
20180925, with the following error messages:
m25p80 spi0.0: error -22 reading 9f
m25p80: probe of spi0.0 failed with error -2
Reverting the spi/for-next branch makes it work again:
[Cc linux-unionfs]
On Wed, Sep 26, 2018 at 1:44 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:2dd68cc7fd8c Merge gitolite.kernel.org:/pub/scm/linux/kern..
> git tree: upstream
> console output:
[Cc linux-unionfs]
On Wed, Sep 26, 2018 at 1:44 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:2dd68cc7fd8c Merge gitolite.kernel.org:/pub/scm/linux/kern..
> git tree: upstream
> console output:
On Tue, Sep 25, 2018 at 11:29 PM Atish Patra wrote:
>
> On 9/23/18 6:37 AM, Anup Patel wrote:
> > Currently, /proc/cpuinfo show logical CPU ID as Hart ID which
> > is in-correct. This patch shows CPU ID and Hart ID separately
> > in /proc/cpuinfo using cpuid_to_hardid_map().
> >
> I noticed it
On Tue, Sep 25, 2018 at 11:29 PM Atish Patra wrote:
>
> On 9/23/18 6:37 AM, Anup Patel wrote:
> > Currently, /proc/cpuinfo show logical CPU ID as Hart ID which
> > is in-correct. This patch shows CPU ID and Hart ID separately
> > in /proc/cpuinfo using cpuid_to_hardid_map().
> >
> I noticed it
On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
devicetree interrupt parsing code is different, causing unit tests of
devicetree interrupt nodes to fail. Due to a bug in unittest code, which
tries to dereference an uninitialized pointer, this results in a crash.
OF:
On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
devicetree interrupt parsing code is different, causing unit tests of
devicetree interrupt nodes to fail. Due to a bug in unittest code, which
tries to dereference an uninitialized pointer, this results in a crash.
OF:
Lazy TLB mode can result in an idle CPU being woken up by a TLB flush,
when all it really needs to do is reload %CR3 at the next context switch,
assuming no page table pages got freed.
Memory ordering is used to prevent race conditions between switch_mm_irqs_off,
which checks whether .tlb_gen
Introduce a variant of on_each_cpu_cond that iterates only over the
CPUs in a cpumask, in order to avoid making callbacks for every single
CPU in the system when we only need to test a subset.
Signed-off-by: Rik van Riel
---
include/linux/smp.h | 4
kernel/smp.c| 17
Add an argument to flush_tlb_mm_range to indicate whether page tables
are about to be freed after this TLB flush. This allows for an
optimization of flush_tlb_mm_range to skip CPUs in lazy TLB mode.
No functional changes.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/tlb.h | 2 +-
Add an argument to flush_tlb_mm_range to indicate whether page tables
are about to be freed after this TLB flush. This allows for an
optimization of flush_tlb_mm_range to skip CPUs in lazy TLB mode.
No functional changes.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/tlb.h | 2 +-
Lazy TLB mode can result in an idle CPU being woken up by a TLB flush,
when all it really needs to do is reload %CR3 at the next context switch,
assuming no page table pages got freed.
Memory ordering is used to prevent race conditions between switch_mm_irqs_off,
which checks whether .tlb_gen
Introduce a variant of on_each_cpu_cond that iterates only over the
CPUs in a cpumask, in order to avoid making callbacks for every single
CPU in the system when we only need to test a subset.
Signed-off-by: Rik van Riel
---
include/linux/smp.h | 4
kernel/smp.c| 17
The code in on_each_cpu_cond sets CPUs in a locally allocated bitmask,
which should never be used by other CPUs simultaneously. There is no
need to use locked memory accesses to set the bits in this bitmap.
Switch to __cpumask_set_cpu.
Suggested-by: Peter Zijlstra
Signed-off-by: Rik van Riel
Move some code that will be needed for the lazy -> !lazy state
transition when a lazy TLB CPU has gotten out of date.
No functional changes, since the if (real_prev == next) branch
always returns.
Suggested-by: Andy Lutomirski
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
Cc: Linus
Now that CPUs in lazy TLB mode no longer receive TLB shootdown IPIs, except
at page table freeing time, and idle CPUs will no longer get shootdown IPIs
for things like mprotect and madvise, we can always use lazy TLB mode.
Tested-by: Song Liu
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
The code in on_each_cpu_cond sets CPUs in a locally allocated bitmask,
which should never be used by other CPUs simultaneously. There is no
need to use locked memory accesses to set the bits in this bitmap.
Switch to __cpumask_set_cpu.
Suggested-by: Peter Zijlstra
Signed-off-by: Rik van Riel
Move some code that will be needed for the lazy -> !lazy state
transition when a lazy TLB CPU has gotten out of date.
No functional changes, since the if (real_prev == next) branch
always returns.
Suggested-by: Andy Lutomirski
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
Cc: Linus
Now that CPUs in lazy TLB mode no longer receive TLB shootdown IPIs, except
at page table freeing time, and idle CPUs will no longer get shootdown IPIs
for things like mprotect and madvise, we can always use lazy TLB mode.
Tested-by: Song Liu
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
Pass the information on to native_flush_tlb_others.
No functional changes.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/tlbflush.h | 1 +
arch/x86/mm/tlb.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/include/asm/tlbflush.h
Pass the information on to native_flush_tlb_others.
No functional changes.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/tlbflush.h | 1 +
arch/x86/mm/tlb.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/include/asm/tlbflush.h
Linus asked me to come up with a smaller patch set to get the benefits
of lazy TLB mode, so I spent some time trying out various permutations
of the code, with a few workloads that do lots of context switches, and
also happen to have a fair number of TLB flushes a second.
Both of the workloads
Linus asked me to come up with a smaller patch set to get the benefits
of lazy TLB mode, so I spent some time trying out various permutations
of the code, with a few workloads that do lots of context switches, and
also happen to have a fair number of TLB flushes a second.
Both of the workloads
On Mon, Sep 24, 2018 at 07:16:45PM +0200, Krzysztof Kozlowski wrote:
> On Sun, Sep 23, 2018 at 02:46:20PM +0100, Olof Johansson wrote:
> > On Thu, Aug 30, 2018 at 7:02 PM, Krzysztof Kozlowski
> > wrote:
> > > Samsung Exynos SoCs and boards related bindings evolved since the initial
> > >
On Mon, Sep 24, 2018 at 07:16:45PM +0200, Krzysztof Kozlowski wrote:
> On Sun, Sep 23, 2018 at 02:46:20PM +0100, Olof Johansson wrote:
> > On Thu, Aug 30, 2018 at 7:02 PM, Krzysztof Kozlowski
> > wrote:
> > > Samsung Exynos SoCs and boards related bindings evolved since the initial
> > >
On Mon, Sep 24, 2018 at 07:21:33PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Pull request without ABI-stability patch.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Mon, Sep 24, 2018 at 07:18:41PM +0200, Krzysztof Kozlowski wrote:
> On Sun, Sep 23, 2018 at 06:47:42AM -0700, Olof Johansson wrote:
> > Hi,
> >
> > On Fri, Sep 21, 2018 at 07:45:19PM +0200, Krzysztof Kozlowski wrote:
> > > Hi,
> > >
> > > Nothing special, description in tag.
> >
> > Hmm.
On Mon, Sep 24, 2018 at 07:21:33PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Pull request without ABI-stability patch.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Mon, Sep 24, 2018 at 07:18:41PM +0200, Krzysztof Kozlowski wrote:
> On Sun, Sep 23, 2018 at 06:47:42AM -0700, Olof Johansson wrote:
> > Hi,
> >
> > On Fri, Sep 21, 2018 at 07:45:19PM +0200, Krzysztof Kozlowski wrote:
> > > Hi,
> > >
> > > Nothing special, description in tag.
> >
> > Hmm.
On Tue, Sep 25, 2018 at 12:53:44PM +0200, Alexandre Belloni wrote:
> Arnd, Olof
>
> The addition of the generic ADC touchscreen driver can probably benefit
> other architectures. Also add the sama5 I2S driver.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
>
On Tue, Sep 25, 2018 at 12:53:44PM +0200, Alexandre Belloni wrote:
> Arnd, Olof
>
> The addition of the generic ADC touchscreen driver can probably benefit
> other architectures. Also add the sama5 I2S driver.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
>
On Tue, Sep 25, 2018 at 12:37:35PM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Most changes are shuffling around the maintainers entries. There are
> also two PM non urgent fixes.
>
> This one as a trivial conflict with the staging tree solved in linux-next.
>
> The following changes
On Tue, Sep 25, 2018 at 12:42:26PM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Here are the DT changes for 4.20. Mostly cleanups and small additions.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Tue, Sep 25, 2018 at 04:21:26PM +, Patrice CHOTARD wrote:
> Hi Arnd, Kevin, Olof
>
> PLease consider this first round of STi dts update for v4.20
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Tue, Sep 25, 2018 at 12:23:58PM +0200, Alexandre Belloni wrote:
> Hi,
>
> A single trivial patch for at91 drivers.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
On Tue, Sep 25, 2018 at 12:37:35PM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Most changes are shuffling around the maintainers entries. There are
> also two PM non urgent fixes.
>
> This one as a trivial conflict with the staging tree solved in linux-next.
>
> The following changes
On Tue, Sep 25, 2018 at 12:42:26PM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Here are the DT changes for 4.20. Mostly cleanups and small additions.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Tue, Sep 25, 2018 at 04:21:26PM +, Patrice CHOTARD wrote:
> Hi Arnd, Kevin, Olof
>
> PLease consider this first round of STi dts update for v4.20
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are
On Tue, Sep 25, 2018 at 12:23:58PM +0200, Alexandre Belloni wrote:
> Hi,
>
> A single trivial patch for at91 drivers.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
Some systems, for example embedded systems, do not generate
enough entropy on boot through interrupts, and boot may be blocked for
several minutes waiting for a call to getrandom to complete.
Currently, random data is read from a hwrng when it is registered,
and is loaded into primary_crng. This
Some systems, for example embedded systems, do not generate
enough entropy on boot through interrupts, and boot may be blocked for
several minutes waiting for a call to getrandom to complete.
Currently, random data is read from a hwrng when it is registered,
and is loaded into primary_crng. This
Hi,
On Sun, Sep 23, 2018 at 10:55:18AM -0400, John David Anglin wrote:
> This change removes the PTE load and present check from the L2_ptep
> macro. The load and check for kernel pages is now done in the tlb_lock
> macro. This avoids a double load and check for user pages. The load
> and
Hi,
On Sun, Sep 23, 2018 at 10:55:18AM -0400, John David Anglin wrote:
> This change removes the PTE load and present check from the L2_ptep
> macro. The load and check for kernel pages is now done in the tlb_lock
> macro. This avoids a double load and check for user pages. The load
> and
We clear the pte temporarily during read/modify/write update of the pte. If we
take a page fault while the pte is cleared, the application can get SIGBUS. One
such case is with remap_pfn_range without a backing vm_ops->fault callback.
do_fault will return SIGBUS in that case.
cpu 0
We clear the pte temporarily during read/modify/write update of the pte. If we
take a page fault while the pte is cleared, the application can get SIGBUS. One
such case is with remap_pfn_range without a backing vm_ops->fault callback.
do_fault will return SIGBUS in that case.
cpu 0
dma-mapping.h and delay.h have included twice. It is unnecessary. Meanwhile,
Arrange header files in alphabetical sequence to improve readability.
Signed-off-by: zhong jiang
---
drivers/misc/genwqe/card_utils.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff
dma-mapping.h and delay.h have included twice. It is unnecessary. Meanwhile,
Arrange header files in alphabetical sequence to improve readability.
Signed-off-by: zhong jiang
---
drivers/misc/genwqe/card_utils.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff
On Tue, Sep 25, 2018 at 08:44:39PM -0400, TongZhang wrote:
> Yes, this is exactly what I am saying.
> A process can change its own name using prctl or /proc/self/comm.
> prctl is protected by security_task_prctl, whereas /proc/self/comm is not
> protected by this LSM hook.
>
> A system admin may
On Tue, Sep 25, 2018 at 08:44:39PM -0400, TongZhang wrote:
> Yes, this is exactly what I am saying.
> A process can change its own name using prctl or /proc/self/comm.
> prctl is protected by security_task_prctl, whereas /proc/self/comm is not
> protected by this LSM hook.
>
> A system admin may
On 26 September 2018 at 04:00, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/25/2018 01:15 PM, Baolin Wang wrote:
>> On 23 September 2018 at 20:25, Jacek Anaszewski
>> wrote:
>>> On 09/22/2018 09:44 PM, Pavel Machek wrote:
On Sat 2018-09-22 00:18:13, Pavel Machek wrote:
> On Sat
On 26 September 2018 at 04:00, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/25/2018 01:15 PM, Baolin Wang wrote:
>> On 23 September 2018 at 20:25, Jacek Anaszewski
>> wrote:
>>> On 09/22/2018 09:44 PM, Pavel Machek wrote:
On Sat 2018-09-22 00:18:13, Pavel Machek wrote:
> On Sat
Greg,
> > > This is the start of the stable review cycle for the 4.14.72 release.
> > > There are 173 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by
Greg,
> > > This is the start of the stable review cycle for the 4.14.72 release.
> > > There are 173 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by
Some battery driver will use the open circuit voltage (OCV) value to look
up the corresponding battery capacity percent in one certain degree Celsius.
Thus this patch provides some battery properties to present the OCV table
temperatures and OCV capacity table values.
Suggested-by: Sebastian
This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
fuel gauge unit device, which is used to calculate the battery capacity.
Signed-off-by: Baolin Wang
---
Changes from v1:
- Renamed GPIO property.
- Use standand battery properties instead of 'sprd,inner-resist' and
This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
which is used to calculate the battery capacity.
Original-by: Yuanjiang Yu
Signed-off-by: Baolin Wang
---
Changes from v1:
- Use battery standard properties to get internal resistance and ocv table.
- Change
Introduce one property to present the battery internal resistance for battery
information.
Signed-off-by: Baolin Wang
---
Changes from v1:
- New patch in v2.
---
.../devicetree/bindings/power/supply/battery.txt |2 ++
drivers/power/supply/power_supply_core.c |3 +++
Some battery driver will use the open circuit voltage (OCV) value to look
up the corresponding battery capacity percent in one certain degree Celsius.
Thus this patch provides some battery properties to present the OCV table
temperatures and OCV capacity table values.
Suggested-by: Sebastian
This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
fuel gauge unit device, which is used to calculate the battery capacity.
Signed-off-by: Baolin Wang
---
Changes from v1:
- Renamed GPIO property.
- Use standand battery properties instead of 'sprd,inner-resist' and
This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
which is used to calculate the battery capacity.
Original-by: Yuanjiang Yu
Signed-off-by: Baolin Wang
---
Changes from v1:
- Use battery standard properties to get internal resistance and ocv table.
- Change
Introduce one property to present the battery internal resistance for battery
information.
Signed-off-by: Baolin Wang
---
Changes from v1:
- New patch in v2.
---
.../devicetree/bindings/power/supply/battery.txt |2 ++
drivers/power/supply/power_supply_core.c |3 +++
On 09/25/2018 07:49 PM, Frank Rowand wrote:
Hi Guenter,
Moving in the right direction, but some comments below.
On 09/25/18 10:32, Guenter Roeck wrote:
On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
devicetree interrupt parsing code is different, causing unit tests of
On 09/25/2018 07:49 PM, Frank Rowand wrote:
Hi Guenter,
Moving in the right direction, but some comments below.
On 09/25/18 10:32, Guenter Roeck wrote:
On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
devicetree interrupt parsing code is different, causing unit tests of
On 9/24/2018 8:01 AM, Jim Quinlan wrote:
On Mon, Sep 24, 2018 at 4:25 AM Ard Biesheuvel
wrote:
On Fri, 21 Sep 2018 at 19:41, Jim Quinlan wrote:
On Thu, Sep 20, 2018 at 5:39 PM Florian Fainelli wrote:
On 09/20/2018 02:33 PM, Ard Biesheuvel wrote:
On 20 September 2018 at 14:31,
On 9/24/2018 8:01 AM, Jim Quinlan wrote:
On Mon, Sep 24, 2018 at 4:25 AM Ard Biesheuvel
wrote:
On Fri, 21 Sep 2018 at 19:41, Jim Quinlan wrote:
On Thu, Sep 20, 2018 at 5:39 PM Florian Fainelli wrote:
On 09/20/2018 02:33 PM, Ard Biesheuvel wrote:
On 20 September 2018 at 14:31,
On Tue, Sep 25, 2018 at 01:52:57PM -0400, Stephen Smalley wrote:
> On 09/25/2018 01:27 PM, Tong Zhang wrote:
> > Kernel Version: 4.18.5
> >
> > Problem Description:
> >
> > When setting nice value, it is checked by LSM function
> > security_task_setnice().
> > see kernel/sched/core.c:3972
On Tue, Sep 25, 2018 at 01:52:57PM -0400, Stephen Smalley wrote:
> On 09/25/2018 01:27 PM, Tong Zhang wrote:
> > Kernel Version: 4.18.5
> >
> > Problem Description:
> >
> > When setting nice value, it is checked by LSM function
> > security_task_setnice().
> > see kernel/sched/core.c:3972
On 9/25/2018 11:08 AM, Yasha Cherikovsky wrote:
The ELF appended dtb can be accessed now via 'fw_passed_dtb'.
Signed-off-by: Yasha Cherikovsky
Reviewed-by: Florian Fainelli
Cc: Kevin Cernekee
Cc: Florian Fainelli
Cc: Ralf Baechle
Cc: Paul Burton
Cc: James Hogan
Cc:
On 9/25/2018 11:08 AM, Yasha Cherikovsky wrote:
The ELF appended dtb can be accessed now via 'fw_passed_dtb'.
Signed-off-by: Yasha Cherikovsky
Reviewed-by: Florian Fainelli
Cc: Kevin Cernekee
Cc: Florian Fainelli
Cc: Ralf Baechle
Cc: Paul Burton
Cc: James Hogan
Cc:
On Tue, 2018-09-25 at 17:48 +0200, Matthias Brugger wrote:
>
> On 05/09/2018 16:09, Ryder Lee wrote:
> > Add display subsystem related device nodes for MT7623.
> >
> > Cc: CK Hu
> > Signed-off-by: chunhui dai
> > Signed-off-by: Bibby Hsieh
> > Signed-off-by: Ryder Lee
> > ---
> > I forgot to
On Tue, 2018-09-25 at 17:48 +0200, Matthias Brugger wrote:
>
> On 05/09/2018 16:09, Ryder Lee wrote:
> > Add display subsystem related device nodes for MT7623.
> >
> > Cc: CK Hu
> > Signed-off-by: chunhui dai
> > Signed-off-by: Bibby Hsieh
> > Signed-off-by: Ryder Lee
> > ---
> > I forgot to
Hi Guenter,
Moving in the right direction, but some comments below.
On 09/25/18 10:32, Guenter Roeck wrote:
> On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
> devicetree interrupt parsing code is different, causing unit tests of
> devicetree interrupt nodes to fail. Due to
Hi Guenter,
Moving in the right direction, but some comments below.
On 09/25/18 10:32, Guenter Roeck wrote:
> On systems with OF_IMAP_OLDWORLD_MAC set in of_irq_workarounds, the
> devicetree interrupt parsing code is different, causing unit tests of
> devicetree interrupt nodes to fail. Due to
Christoph Hellwig 於 2018年9月25日 週二 下午11:25寫道：
>
> On Tue, Sep 25, 2018 at 10:19:55AM +0800, Zong Li wrote:
> > The RV32 need the umoddi3 to do modulo when the operands are long long
> > type, like other libraries implementation such as ucmpdi2, lshrdi3 and
> > so on. I encounter the undefined
Christoph Hellwig 於 2018年9月25日 週二 下午11:25寫道：
>
> On Tue, Sep 25, 2018 at 10:19:55AM +0800, Zong Li wrote:
> > The RV32 need the umoddi3 to do modulo when the operands are long long
> > type, like other libraries implementation such as ucmpdi2, lshrdi3 and
> > so on. I encounter the undefined
On Wed, 2018-09-26 at 09:37 +0800, CK Hu wrote:
> Hi, Ryder:
>
> On Wed, 2018-09-05 at 22:09 +0800, Ryder Lee wrote:
> > Add display subsystem related device nodes for MT7623.
> >
> > Cc: CK Hu
> > Signed-off-by: chunhui dai
> > Signed-off-by: Bibby Hsieh
> > Signed-off-by: Ryder Lee
> > ---
On Wed, 2018-09-26 at 09:37 +0800, CK Hu wrote:
> Hi, Ryder:
>
> On Wed, 2018-09-05 at 22:09 +0800, Ryder Lee wrote:
> > Add display subsystem related device nodes for MT7623.
> >
> > Cc: CK Hu
> > Signed-off-by: chunhui dai
> > Signed-off-by: Bibby Hsieh
> > Signed-off-by: Ryder Lee
> > ---
On 26/09/2018 9:49 AM, Song Qiang wrote:
On Tue, Sep 25, 2018 at 10:36:54PM +0800, Phil Reid wrote:
On 25/09/2018 9:30 PM, Jonathan Cameron wrote:
+static irqreturn_t rm3100_trigger_handler(int irq, void *p)
+{
+ struct iio_poll_func *pf = p;
+ struct iio_dev *indio_dev =
On 26/09/2018 9:49 AM, Song Qiang wrote:
On Tue, Sep 25, 2018 at 10:36:54PM +0800, Phil Reid wrote:
On 25/09/2018 9:30 PM, Jonathan Cameron wrote:
+static irqreturn_t rm3100_trigger_handler(int irq, void *p)
+{
+ struct iio_poll_func *pf = p;
+ struct iio_dev *indio_dev =
On Tue, Sep 25 2018, Joe Perches wrote:
> On Tue, 2018-09-25 at 20:49 +0200, Greg Kroah-Hartman wrote:
>> On Sun, Sep 23, 2018 at 06:31:32AM -0700, Joe Perches wrote:
>> > On Sun, 2018-09-23 at 15:08 +0530, Nishad Kamdar wrote:
>> > > This patch fixes a few single statement macros in sd.c.
>> > >
On Tue, Sep 25 2018, Joe Perches wrote:
> On Tue, 2018-09-25 at 20:49 +0200, Greg Kroah-Hartman wrote:
>> On Sun, Sep 23, 2018 at 06:31:32AM -0700, Joe Perches wrote:
>> > On Sun, 2018-09-23 at 15:08 +0530, Nishad Kamdar wrote:
>> > > This patch fixes a few single statement macros in sd.c.
>> > >
Hi Alex,
Today's linux-next merge of the vfio tree got a conflict in:
drivers/vfio/Kconfig
between commit:
f57d445eb317 ("Make anon_inodes unconditional")
from the vfs tree and commit:
cf3f98c7f466 ("drivers/vfio: Allow type-1 IOMMU instantiation with all
ARM/ARM64 IOMMUs")
from the
Hi Alex,
Today's linux-next merge of the vfio tree got a conflict in:
drivers/vfio/Kconfig
between commit:
f57d445eb317 ("Make anon_inodes unconditional")
from the vfs tree and commit:
cf3f98c7f466 ("drivers/vfio: Allow type-1 IOMMU instantiation with all
ARM/ARM64 IOMMUs")
from the
1 - 100 of 1496 matches
Mail list logo
