On Tue, Jul 31, 2018 at 11:59:14AM -0700, Matthias Kaehlcke wrote:
> The current example for a thermal zone isn't very useful as reference
> since it would result in a hardware shutdown at 145°C, instead of
> allowing the system to try to shutdown gracefully. Without an ADC
> channel a maximum of t
On Mon, Jul 09, 2018 at 04:49:37PM -0700, Evan Green wrote:
> pm_runtime_suspended can return 0 even if the last runtime power
> management function called in the device was a suspend call. This
> trips up the i2c-qcom-geni's suspend_noirq accounting, which was
> trying to use the function to deter
On Mon, Jul 30, 2018 at 11:23:51AM -0600, Karthikeyan Ramasubramanian wrote:
> This bus driver supports the GENI based i2c hardware controller in the
> Qualcomm SOCs. The Qualcomm Generic Interface (GENI) is a programmable
> module supporting a wide range of serial interfaces including I2C. The
> d
On Mon, Jul 30, 2018 at 11:23:52AM -0600, Karthikeyan Ramasubramanian wrote:
> Add Alok Chauhan and myself as maintainers for Qualcomm GENI I2C master
> controller driver.
>
> Signed-off-by: Karthikeyan Ramasubramanian
Applied to for-next, thanks!
signature.asc
Description: PGP signature
On Tue, Jul 31, 2018 at 11:59:13AM -0700, Matthias Kaehlcke wrote:
> The documentation 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 con
On Tue, 2018-07-31 at 17:04 +0200, Peter Zijlstra wrote:
> On Mon, Jul 30, 2018 at 07:06:21AM -0700, Srinivas Pandruvada wrote:
> > On Mon, 2018-07-30 at 14:16 +0300, Eero Tamminen wrote:
> > > Questions:
> > >
> > > * Does currently kernel CPU freq management have any idea which
> > > IO
> > >
Am Dienstag, 31. Juli 2018, 15:38:27 CEST schrieb Mike Rapoport:
> Any comments on this?
>
> On Tue, Jul 24, 2018 at 04:23:12PM +0300, Mike Rapoport wrote:
> > Hi,
> >
> > These patches convert UML to use NO_BOOTMEM.
> > Tested on x86-64.
> >
> > Mike Rapoport (2):
> > um: setup_physmem: stop
On Tue, Jul 31, 2018 at 10:43 AM Luck, Tony wrote:
>
> If I just revert bfd40eaff5ab ("mm: fix vma_is_anonymous() false-positives")
> then ia64 boots again.
Ok, so it's not just the ashmem thing.
I think I'll do an rc8 with the revert, just so that we'll have some
time to figure this out. It's o
On 31.07.2018 18:29, Robin Murphy wrote:
> On 31/07/18 16:53, Stefan Agner wrote:
>> On 31.07.2018 14:32, Robin Murphy wrote:
>>> On 31/07/18 09:19, Stefan Agner wrote:
On 30.07.2018 16:38, Robin Murphy wrote:
> On 28/07/18 17:58, Guenter Roeck wrote:
>> On Fri, Jul 27, 2018 at 04:04:4
The documentation 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 documentation of the field and the
example
There are three thermal stages defined in the PMIC:
stage 1: warning
stage 2: system should shut down
stage 3: emergency shut down
By default the PMIC assumes that the OS isn't doing anything and thus
at stage 2 it does a partial PMIC shutdown and at stage 3 it kills
all power. When switching bet
This adds the spmi-temp-alarm node to pm8998 based on the examples in the
bindings.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Douglas Anderson
---
Changes in v6:
- none
Changes in v5:
- added tag 'Reviewed-by: Douglas Anderson '
Changes in v4:
- none
Changes in v3:
- changed node name fro
The thermal zone uses spmi-temp-alarm as sensor, the trip points
correspond to the PMIC thermal stages 1 and 2. The critical trip
point at 125°C disables the partial PMIC shutdown at stage 2.
Without an IIO input the sensor only reports a limited number of
temperatures:
- 37°C for temperatures be
The current example for a thermal zone isn't very useful as reference
since it would result in a hardware shutdown at 145°C, instead of
allowing the system to try to shutdown gracefully. Without an ADC
channel a maximum of two trip points is useful in practice for this
sensor, with temperatures cor
On Tue, Jul 31, 2018 at 10:02 AM Kees Cook wrote:
>
> On Tue, Jul 31, 2018 at 9:48 AM, Nick Desaulniers
> > On Tue, Jul 31, 2018 at 3:27 AM kbuild test robot wrote:
> >>drivers/net//wireless/intel/iwlwifi/iwl-trans.c: In function
> >> 'iwl_trans_send_cmd':
> >> >> drivers/net//wireless/intel
Hi Greg,
could you please confirm you received my patch?
Regards,
Roman.
On Mon, Jul 23, 2018 at 3:47 PM wrote:
>
> From: Roman Kiryanov
>
> goldfish.h refers to external symbols such as
> dma_addr_t and writel. This causes compilation errors
> if this file is included before other header files
> On Jul 31, 2018, at 8:36 AM, Peter Zijlstra wrote:
>
> On Tue, Jul 31, 2018 at 09:12:22PM +0900, jiada_w...@mentor.com wrote:
>> diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c
>> index 60caf1fb94e0..7b2997d4a349 100644
>> --- a/kernel/sched/debug.c
>> +++ b/kernel/sched/debug.c
>>
There are three thermal stages defined in the PMIC:
stage 1: warning
stage 2: system should shut down
stage 3: emergency shut down
By default the PMIC assumes that the OS isn't doing anything and thus
at stage 2 it does a partial PMIC shutdown and at stage 3 it kills
all power. When switching bet
The thermal zone uses spmi-temp-alarm as sensor, the trip points
correspond to the PMIC thermal stages 1 and 2. The critical trip
point at 125°C disables the partial PMIC shutdown at stage 2.
Without an IIO input the sensor only reports a limited number of
temperatures:
- 37°C for temperatures be
The documentation 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 documentation of the field and the
example
This adds the spmi-temp-alarm node to pm8998 based on the examples in the
bindings.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Douglas Anderson
---
Changes in v6:
- none
Changes in v5:
- added tag 'Reviewed-by: Douglas Anderson '
Changes in v4:
- none
Changes in v3:
- changed node name fro
The current example for a thermal zone isn't very useful as reference
since it would result in a hardware shutdown at 145°C, instead of
allowing the system to try to shutdown gracefully. Without an ADC
channel a maximum of two trip points is useful in practice for this
sensor, with temperatures cor
On Tue, Jul 31, 2018 at 01:37:29AM +, Jeremy Cline wrote:
> Hi folks,
>
> This series unifies XQM_MAXQUOTAS with MAXQUOTAS, which were both being
> used to perform bounds checks on arrays, and then sanitizes 'type' so it
> can't be used in speculative out-of-bounds array access.
>
> Jeremy Cl
On 31/07/2018 17:53:17+0300, Andy Shevchenko wrote:
> On Tue, 2018-07-31 at 16:30 +0200, Alexandre Belloni wrote:
> > On 31/07/2018 17:23:04+0300, Andy Shevchenko wrote:
> > > On Tue, 2018-07-31 at 17:02 +0300, Andy Shevchenko wrote:
> > > > On Tue, 2018-07-31 at 15:47 +0200, Alexandre Belloni wrot
Hi Peter,
In 4.9 branch, we hit an issue in RCU, where the NOCB follower list not getting
reclaimed and causing OOM.
In discussion with Paul, we were able to figure out the problem was because of
missed wake up resulted from lack of proper memory barrier between setting
wake up condition and swak
On Mon, 2018-07-30 at 18:24 +0200, Mike Galbraith wrote:
> On Sun, 2018-07-29 at 13:47 +0200, Mike Galbraith wrote:
> > FYI, per kvm unit tests, 4.16-rt definitely has more kvm issues.
But it's not RT, or rather most of it isn't...
> > huawei5:/abuild/mike/kvm-unit-tests # uname -r
> > 4.16.18-rt
Add support for control peripheral of EUD (Embedded USB Debugger) to
listen to events such as USB attach/detach, charger enable/disable, pet
EUD to indicate software is functional.
Signed-off-by: Satya Durga Srinivasu Prabhala
Signed-off-by: Prakruthi Deepak Heragu
---
drivers/soc/qcom/Kconfig
Documentation for Embedded USB Debugger (EUD) device tree bindings.
Signed-off-by: Satya Durga Srinivasu Prabhala
Signed-off-by: Prakruthi Deepak Heragu
---
.../devicetree/bindings/soc/qcom/qcom,msm-eud.txt | 28 ++
1 file changed, 28 insertions(+)
create mode 100644 Docum
This is a series of patches that implements a driver for the control
peripheral, EUD (Embedded USB Debugger). The EUD is a mini-USB hub
implemented on chip to support the USB-based debug and trace capabilities.
Apart from debug capabilities, EUD has a control peripheral. Control
Peripheral is on
On Tue, Jul 31, 2018 at 01:59:27PM -0400, Alex Bounine wrote:
> On 2018-07-31 11:52 AM, Russell King - ARM Linux wrote:
> >On Tue, Jul 31, 2018 at 08:54:14AM -0400, Alex Bounine wrote:
> >>On 2018-07-31 04:41 AM, Will Deacon wrote:
> >>>On Mon, Jul 30, 2018 at 06:50:34PM -0400, Alexei Colin wrote:
This is a series of patches that implements a driver for the control
peripheral, EUD (Embedded USB Debugger). The EUD is a mini-USB hub
implemented on chip to support the USB-based debug and trace capabilities.
Apart from debug capabilities, EUD has a control peripheral. Control
Peripheral is on
On 31/07/2018 10:38:09-0700, Paul Burton wrote:
> Hi Alexandre,
>
> On Tue, Jul 31, 2018 at 04:38:52PM +0200, Alexandre Belloni wrote:
> > Hello,
> >
> > This series only contains the DT documentation and the corresponding DT
> > addition
> > since it has been rebased on spi-next.
> >
> > Alexa
On 2018-07-31 10:57, Krzysztof Kozlowski wrote:
On 31 July 2018 at 18:43, Angus Ainslie (Purism)
wrote:
To ease adding a new part variant some debugging is handy.
Signed-off-by: Angus Ainslie (Purism)
You missed my tag - I already reviewed it. Unless you change
something, the tag should be
On 7/31/2018 10:34 AM, Micah Morton wrote:
> The set*uid system calls all call an LSM fixup hook called
> security_task_fix_setuid, which allows for altering the behavior of those
> calls by a security module. Comments explaining the LSM_SETID_* constants
> in /include/linux/security.h imply that t
On 2018-07-31 11:52 AM, Russell King - ARM Linux wrote:
On Tue, Jul 31, 2018 at 08:54:14AM -0400, Alex Bounine wrote:
On 2018-07-31 04:41 AM, Will Deacon wrote:
On Mon, Jul 30, 2018 at 06:50:34PM -0400, Alexei Colin wrote:
Platforms with a PCI bus will be offered the RapidIO menu since they ma
On Tue, Jul 31, 2018 at 04:23:00PM +, Sironi, Filippo wrote:
>
> > On 31. Jul 2018, at 17:41, Greg KH wrote:
> >
> > On Tue, Jul 31, 2018 at 05:29:30PM +0200, Filippo Sironi wrote:
> >> ... on late microcode loading when handling a CPU that's already been
> >> updated and a CPU that's yet to
On Tue, Jul 31, 2018 at 10:36 AM Christopher Lameter wrote:
>
> If there is refcounting going on then why use SLAB_TYPESAFE_BY_RCU?
.. because the object can be accessed (by RCU) after the refcount has
gone down to zero, and the thing has been released.
That's the whole and only point of SLAB_TY
There are a few table entries that aren't used. Drop them.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/power/supply/bq25890_charger.c
b/drivers/power/supply/bq2
Changes since v3:
Corrected reviewed-by tags.
Fix typos.
Clarify desscriptions of patches.
Changes since v2:
Remove additional un-used table entries.
Use the exsisting compitble string for the new part.
Voltage now doesn't depend on state "online".
Angus Ainslie (Purism) (4):
power: bq25890_c
The BQ25896 is almost identical to the BQ25890.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Angus Ainslie (Purism)
---
.../bindings/power/supply/bq25890.txt | 3 +++
drivers/power/supply/bq25890_charger.c| 24 +++
2 files changed, 22 insertions(+), 5 deletio
To ease adding a new part variant some debugging is handy.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/drivers/power/supply/bq25890_
The BQ2589x family has the capability of reading the current battery voltage.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/power/supply/bq25890_charger.c
On Tue, Jul 31, 2018 at 07:09:28PM +0800, Zhaoyang Huang wrote:
> This patch try to let the direct reclaim finish earlier than it used
> to be. The problem comes from We observing that the direct reclaim
> took a long time to finish when memcg is enabled. By debugging, we
> find that the reason is
Add devicetree binding for Xilinx AXI Multichannel Direct Memory Access
(AXI MCDMA) IP. The AXI MCDMA provides high-bandwidth direct memory
access between memory and AXI4-Stream target peripherals. The AXI MCDMA
core provides scatter-gather interface with multiple channel support.
Signed-off-by: R
On Thu, Jul 26, 2018 at 01:54:43PM +0100, Suzuki K Poulose wrote:
> At the moment, if there is no CPU specified for a given
> event, we use cpu_online_mask and try to build path for
> each of the CPUs in the mask. This could prevent any CPU
> that is turned online later to be used for the tracing.
Add support for AXI Multichannel Direct Memory Access (AXI MCDMA)
core, which is a soft Xilinx IP core that provides high-bandwidth
direct memory access between memory and AXI4-Stream target peripherals.
The AXI MCDMA core provides scatter-gather interface with multiple
independent transmit and rec
This patchset adds Xilinx AXI MCDMA IP support. The AXI MCDMA provides
high-bandwidth direct memory access between memory and AXI4-Stream target
peripherals. It supports up to 16 independent read/write channels.
MCDMA IP supports per channel interrupt output but driver support one
interrupt per ch
On Tue, Jul 31, 2018 at 08:03:28PM +0300, Kirill A. Shutemov wrote:
> But it's not the only issue unfortunately. Tony reported issue with
> booting ia64 with the patch. I have no clue why. I rechecked everything
> ia64-specific and looks fine to me. :-/
If I just revert bfd40eaff5ab ("mm: fix vma_
> The feature strings are automatically generated from the define. The comment
> can be used to supress them by an empty "" string or to modify them by a
> "override" string at the beginning of the comment.
I overlooked "override" part. Sorry! about that.
It's clear now. Thanks for the explanation
On Tue, Jul 31, 2018 at 04:58:41PM +0100, Robin Murphy wrote:
> On 31/07/18 16:43, Guenter Roeck wrote:
> >On Tue, Jul 31, 2018 at 03:09:34PM +0100, Robin Murphy wrote:
> >>>Please note that sparc images still generate the warning (next-20180731).
> >>
> >&g
Hi Alexandre,
On Tue, Jul 31, 2018 at 04:38:52PM +0200, Alexandre Belloni wrote:
> Hello,
>
> This series only contains the DT documentation and the corresponding DT
> addition
> since it has been rebased on spi-next.
>
> Alexandre Belloni (3):
> spi: dw: document Microsemi integration
> mi
The set*uid system calls all call an LSM fixup hook called
security_task_fix_setuid, which allows for altering the behavior of those
calls by a security module. Comments explaining the LSM_SETID_* constants
in /include/linux/security.h imply that the constants are to be used for
both the set*uid an
Приветствуем прозаических творений Материализуем всякие Ваши творения
литературы Работаем по всему миру и по всяким категориям. Конкурсы и
презентации авторов в белокаменной столице
Имеем нужду в спонсоре .
On Tue, Jul 31, 2018 at 12:39:41AM -0600, Andreas Dilger wrote:
> > Also it looks like XQM_MAXQUOTAS, MAXQUOTAS, and EXT4_MAXQUOTAS all
> > have the same value (3). Maybe they can be consolidated to just use
> > MAXQUOTAS everywhere?
>
> No, the filesystem-specific MAXQUOTAS values were separated
Em Tue, Jul 31, 2018 at 08:40:51PM +0530, Ganapatrao Kulkarni escreveu:
> Hi Arnaldo,
>
> On Tue, Jul 31, 2018 at 7:58 PM, Arnaldo Carvalho de Melo
> wrote:
> > Em Tue, Jul 31, 2018 at 03:32:51PM +0530, Ganapatrao Kulkarni escreveu:
> >> Signed-off-by: Ganapatrao Kulkarni
> >
> > Can you please
On Tue, 2018-07-31 at 12:32 +0200, Marcel Holtmann wrote:
> Hi Sean,
>
> >>> All suggestions seem reasonable for me in order to make code style
> >>> aligned with the other drivers and code better to read,
> >>> and it looks like no any big problem, so I'll start to work on the next
> >>> versio
Amit Pundir and Youling in parallel reported crashes with recent
mainline kernels running Android:
F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
F DEBUG : Build fingerprint:
'Android/db410c32_only/db410c32_only:Q/OC-MR1/102:userdebug/test-key
F DEBUG : Revision: '
On Fri, Jul 27, 2018 at 01:18:02PM +0100, Srinivas Kandagatla wrote:
> +static const char * const wcd9335_ear_pa_gain_text[] = {
> + "G_6_DB", "G_4P5_DB", "G_3_DB", "G_1P5_DB",
> + "G_0_DB", "G_M2P5_DB", "UNDEFINED", "G_M12_DB"
> +};
This is fairly clearly a volume control so shouldn't be
From: Sean Wang
Add an entry for the MediaTek Bluetooth driver.
Signed-off-by: Sean Wang
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0f2cce4..e983d9e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9144,6 +9144,14 @@ F: inclu
From: Sean Wang
Add binding document for a SoC built-in device using MediaTek protocol.
Which could be found on MT7622 SoC or other similar MediaTek SoCs.
Signed-off-by: Sean Wang
Reviewed-by: Rob Herring
---
.../devicetree/bindings/net/mediatek-bluetooth.txt | 35 ++
1 fi
From: Sean Wang
This adds a driver based on serdev driver for the MediaTek serial protocol
based on running H:4, which can enable the built-in Bluetooth device inside
MT7622 SoC.
Signed-off-by: Sean Wang
---
drivers/bluetooth/Kconfig | 11 +
drivers/bluetooth/Makefile| 2 +
drivers/
From: Sean Wang
v7 and changes since v6:
- drop already applied patches
- move clk_* and pm_* operation to ->open and ->close
- label this driver as BT_MTKUART
- make code style aligned with the other drivers and code better to read
as these suggestions and fixes are mentioned in [1]
[1]
On Tue, Jul 31, 2018 at 06:13:58PM +0200, Anna-Maria Gleixner wrote:
> local_timer_softirq_pending() checks whether the timer softirq is
> pending with: local_softirq_pending() & TIMER_SOFTIRQ.
>
> This is wrong because TIMER_SOFTIRQ is the softirq number and not a
> bitmask. So the test checks fo
Xunlei Pang writes:
> On 7/31/18 1:55 AM, Cong Wang wrote:
>> On Sun, Jul 29, 2018 at 10:29 PM Xunlei Pang
>> wrote:
>>>
>>> Hi Cong,
>>>
>>> On 7/28/18 8:24 AM, Cong Wang wrote:
Each time we sync cfs_rq->runtime_expires with cfs_b->runtime_expires,
we should sync its ->expires_seq to
On Tue, Jul 31, 2018 at 10:02 AM Kees Cook wrote:
>
> On Tue, Jul 31, 2018 at 9:48 AM, Nick Desaulniers
> wrote:
> > Does anyone understand this error? The code looks just fine to me,
> > and the source file doesn't conflict with any of the macros I've added
> > (certainly not in any way that co
we prefer to the kmemdup rather than kmalloc+memcpy. so just
replace them.
Signed-off-by: zhong jiang
---
kernel/module.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 20344e4..6746c85 100644
--- a/kernel/module.c
+++ b/kernel/m
On 07/31/2018 06:13 PM, Anna-Maria Gleixner wrote:
> local_timer_softirq_pending() checks whether the timer softirq is
> pending with: local_softirq_pending() & TIMER_SOFTIRQ.
>
> This is wrong because TIMER_SOFTIRQ is the softirq number and not a
> bitmask. So the test checks for the wrong bit.
>
Hello,
On Thu, Jul 26, 2018 at 01:54:40PM +0100, Suzuki K Poulose wrote:
> If the ETB is already enabled in sysfs mode, the ETB reports
> success even if a perf mode is requested. Fix this by checking
> the requested mode.
>
> Cc: Mathieu Poirier
> Signed-off-by: Suzuki K Poulose
> ---
> drive
On Fri, Jul 27, 2018 at 01:18:01PM +0100, Srinivas Kandagatla wrote:
> + res_val = WCD9XXX_CLASSH_CTRL_VCL_VREF_FILT_R_0KOHM;
> + switch (mode) {
> + case CLS_H_NORMAL:
> + res_val = WCD9XXX_CLASSH_CTRL_VCL_VREF_FILT_R_50KOHM;
> + val = WCD9XXX_A_ANA_HPH_PWR_LEV
Convert the DPAA2 Ethernet driver documentation to .rst format
and rename the file accordingly.
Also add a SPDX tag to the new rst file.
Signed-off-by: Ioana Ciornei
---
.../ethernet/{README => ethernet-driver.rst} | 39 +++---
1 file changed, 19 insertions(+), 20 deletions
On Tue, Jul 31, 2018 at 09:29:22AM -0700, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
> >
> > This ashmem change ^^ worked too.
>
> Ok, let's go for that one and hope it's the only one.
>
> John, can I get a proper commit message and sign-off for that ashmem chang
The DPAA2 Ethernet driver files use a GPL-2.0+ OR BSD-3-Clause
license. Add SPDX tags and delete the full license text,
keeping the existing licenses for each file.
Add a GPL-2.0 tag for the Makefile.
Signed-off-by: Ioana Ciornei
---
drivers/staging/fsl-dpaa2/ethernet/Makefile| 1 +
...
test WARNING on v4.18-rc7 next-20180727]
> > [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/Nick-Desaulniers/compiler-clang-h-Add-CLANG_VERSION-and-__
On 31 July 2018 at 18:43, Angus Ainslie (Purism) wrote:
> The part has the capability of reading the current battery voltage.
Instead of "part": BQ25890-family of chargers? Chip?
Anyway,
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
>
> Signed-off-by: Angus Ainslie (Purism)
> ---
On Tue, Jul 31, 2018 at 9:48 AM, Nick Desaulniers
wrote:
> Does anyone understand this error? The code looks just fine to me,
> and the source file doesn't conflict with any of the macros I've added
> (certainly not in any way that could cause an indentation error as
> reported here).
It does _u
On 31 July 2018 at 18:43, Angus Ainslie (Purism) wrote:
> The BQ25896 is almost identical the the BQ25890.
s/the the/to the/
>
> Signed-off-by: Angus Ainslie (Purism)
> ---
> .../bindings/power/supply/bq25890.txt | 3 +++
> drivers/power/supply/bq25890_charger.c| 24 ++
On 31 July 2018 at 18:43, Angus Ainslie (Purism) wrote:
> There are a few table entries that aren't used. Drop them.
>
> Signed-off-by: Angus Ainslie (Purism)
> ---
> drivers/power/supply/bq25890_charger.c | 5 -
> 1 file changed, 5 deletions(-)
Reviewed-by: Krzysztof Kozlowski
Best regar
On 31 July 2018 at 18:43, Angus Ainslie (Purism) wrote:
> To ease adding a new part variant some debugging is handy.
>
> Signed-off-by: Angus Ainslie (Purism)
You missed my tag - I already reviewed it. Unless you change
something, the tag should be added to commit msg:
Reviewed-by: Krzysztof Koz
On Tue, Jul 31, 2018 at 9:29 AM, Linus Torvalds
wrote:
> On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
>>
>> This ashmem change ^^ worked too.
>
> Ok, let's go for that one and hope it's the only one.
>
> John, can I get a proper commit message and sign-off for that ashmem change?
Will do.
-Add-CLANG_VERSION-and-__diag-macros/20180731-161932
> config: x86_64-randconfig-s1-07312048 (attached as .config)
> compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All error
On Mon, Jul 30, 2018 at 08:21:33PM -0700, Atish Patra wrote:
> I found the issue. As per PLIC documentation, a hart context is a given
> privilege mode on a given hart. Thus, cpu context ID & cpu numbers are not
> same. Here is the PLIC register Maps in U54 core:
>
> Ref: https://static.dev.sifiv
On 31/07/2018 17:58, Vitaly Kuznetsov wrote:
> Thank you for the rebase,
>
> it seems that with multi-root caching this series should just ignore CR3
> changes for both root_mmu and guest_mmu: we now have two separate
> 'prev_roots' caches and these work well. However, we still can optimize
> MMU
On Tue, Jul 31, 2018 at 06:13:58PM +0200, Anna-Maria Gleixner wrote:
> local_timer_softirq_pending() checks whether the timer softirq is
> pending with: local_softirq_pending() & TIMER_SOFTIRQ.
>
> This is wrong because TIMER_SOFTIRQ is the softirq number and not a
> bitmask. So the test checks fo
> url:
> https://github.com/0day-ci/linux/commits/Nick-Desaulniers/compiler-clang-h-Add-CLANG_VERSION-and-__diag-macros/20180731-161932
> config: x86_64-fedora-25 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> # save the attached .con
Nick-Desaulniers/kernel-h-Disable-Wreturn-stack-address-for-_THIS_IP_/20180731-135818
> config: i386-tinyconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> A
The BQ25896 is almost identical the the BQ25890.
Signed-off-by: Angus Ainslie (Purism)
---
.../bindings/power/supply/bq25890.txt | 3 +++
drivers/power/supply/bq25890_charger.c| 24 +++
2 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/Documentation
Changes since v2:
Remove additional un-used table entries.
Use the exsisting compitble string for the new part.
Voltage now doesn't depend on state "online".
Angus Ainslie (Purism) (4):
power: bq25890_charger.c: Add debugging output of failed
initialization
power: bq25890_charger.c: Remov
The part has the capability of reading the current battery voltage.
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/power/supply/bq25890_charger.c
b/drivers/power/supply/bq25890_charger.c
in
There are a few table entries that aren't used. Drop them.
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/power/supply/bq25890_charger.c
b/drivers/power/supply/bq25890_charger.c
index 7f0b3a46c50c.
To ease adding a new part variant some debugging is handy.
Signed-off-by: Angus Ainslie (Purism)
---
drivers/power/supply/bq25890_charger.c | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/drivers/power/supply/bq25890_charger.c
b/drivers/power/supply/
kmem_cache_destroy has taken the null check into account. so just
remove the unnecessary check.
Signed-off-by: zhong jiang
---
lib/debugobjects.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/debugobjects.c b/lib/debugobjects.c
index 994be48..7a6d80b 100644
--- a/lib/
kmem_cache_destroy/mempool_destroy has taken null check into account.
so remove the redundant check.
Signed-off-by: zhong jiang
---
lib/sg_pool.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/lib/sg_pool.c b/lib/sg_pool.c
index 6dd3061..d1c1e63 100644
--- a/lib/sg_po
On Fri, Jul 27, 2018 at 05:04:52PM -0700, Atish Patra wrote:
>> +#define MAX_DEVICES 1024
>> +#define MAX_CONTEXTS15872
>> +
>
> Is there any way we can preserve some of the comments in the original patch
> about memory-mapped control registers or at least a
/commits/Jinbum-Park/perf-core-Fix-possible-Spectre-v1-for-perf_swevent_enabled/20180731-235311
config: i386-randconfig-x077-201830 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error
On 31/07/18 16:53, Stefan Agner wrote:
On 31.07.2018 14:32, Robin Murphy wrote:
On 31/07/18 09:19, Stefan Agner wrote:
On 30.07.2018 16:38, Robin Murphy wrote:
On 28/07/18 17:58, Guenter Roeck wrote:
On Fri, Jul 27, 2018 at 04:04:48PM +0200, Christoph Hellwig wrote:
On Fri, Jul 27, 2018 at 0
On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
>
> This ashmem change ^^ worked too.
Ok, let's go for that one and hope it's the only one.
John, can I get a proper commit message and sign-off for that ashmem change?
Kirill - you mentioned that somebody reproduced a problem on x86-64
too. I
On 2018/8/1 0:21, Thomas Gleixner wrote:
> On Tue, 31 Jul 2018, zhong jiang wrote:
>
>> kmem_cache_destroy/mempool_destroy has taken null check into account.
>> so remove the redundant check.
> Please split the patch so they can be applied independently by the relevant
> maintainers.
>
> Thanks,
>
On Mon, Jul 30, 2018 at 10:01 AM 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 is required for job control in a shell that us
> On 31. Jul 2018, at 17:41, Greg KH wrote:
>
> On Tue, Jul 31, 2018 at 05:29:30PM +0200, Filippo Sironi wrote:
>> ... on late microcode loading when handling a CPU that's already been
>> updated and a CPU that's yet to be updated.
>>
>> Signed-off-by: Filippo Sironi
>> ---
>> arch/x86/kernel
201 - 300 of 659 matches
Mail list logo
