On 29/01/2019 11:35, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.154 release.
> There are 44 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 sh
On Tue, 29 Jan 2019, Andrew Lunn wrote:
> On Tue, Jan 29, 2019 at 11:35:32AM +, Lee Jones wrote:
> > On Sat, 12 Jan 2019, Andrew Lunn wrote:
> >
> > > The QMX86 is a PLD present on some TQ-Systems ComExpress modules. It
> > > provides 1 or 2 I2C bus masters, 8 GPIOs and a watchdog timer. Add
There are functions in relocate_kernel which are not annotated. This
makes automatic annotations rather hard. So annotate all the functions
now.
Note that these are not C-like functions, so we do not use FUNC, but
CODE markers. Also they are not aligned, so we use the NOALIGN versions:
- SYM_CODE_
_key_expansion_128 is an alias to _key_expansion_256a, __memcpy to
memcpy, xen_syscall32_target to xen_sysenter_target, and so on. Annotate
them all using the new SYM_FUNC_START_ALIAS, SYM_FUNC_START_LOCAL_ALIAS,
and SYM_FUNC_END_ALIAS. This will make the tools generating the
debuginfo happy.
Sign
You need to rebase on linus/master. A bunch of your patches are obsoleted by
Al's security changes there.
David
On 29/01/2019 11:35, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.97 release.
> There are 68 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 sh
Hi Krzysztof,
On 1/30/19 10:46 AM, Krzysztof Kozlowski wrote:
> On Tue, 29 Jan 2019 at 18:55, Lukasz Luba wrote:
>>
>> Add description of Dynamic Memory Controller and PPMU counters.
>> They are used by exynos5422-dmc driver.
>>
>> CC: Rob Herring
>> CC: Mark Rutland
>> CC: Kukjin Kim
>> CC: K
On Wed, Jan 30, 2019 at 01:28:20PM +0100, Sebastian Andrzej Siewior wrote:
> > > + /*
> > > + * If we do not need to load the FPU registers at return to userspace
> > > + * then the CPU has the current state and we need to save it. Otherwise
> > > + * it is already done and we can skip it.
> > >
On Tue, Jan 29, 2019 at 8:49 PM Sam Ravnborg wrote:
>
> Hi Jagan.
>
> > >
> > > I see DRM_MODE_ARG as mode argument, that print all mode timings but
> > > here we need only 3 timings out of it. do we really need? if yes
> > > please suggest an example.
> >
> > fyi: sent v6 for this except this cha
On Tue, 29 Jan 2019 at 17:19, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.97 release.
> There are 68 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.
>
> Res
Hi Jon,
Have you had a chance to review this patchset?
Thanks,
Joel Nider/Haifa/IBM@IBMIL wrote on 01/22/2019 12:00:32 PM:
> From: Joel Nider/Haifa/IBM@IBMIL
> To: "Jonathan Corbet"
> Cc: "Jason Gunthorpe" , "Leon Romanovsky"
,
> "Doug Ledford" , "Mike Rapoport"
,
> Joel Nider/Haifa/IBM@IB
Hi Roger,
On 30/01/19 6:11 PM, Roger Quadros wrote:
> Kishon,
>
> On 30/01/19 12:59, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On 30/01/19 4:18 PM, Roger Quadros wrote:
>>> Hi Kishon,
>>>
>>> On 24/01/19 12:48, Kishon Vijay Abraham I wrote:
DRA72 platform has the second instance of PH
From: Frieder Schrempf
The information about where the manufacturer puts the bad block
markers inside the bad block and in the OOB data is stored in
different places. Let's move this information to nand_chip.options
and nand_chip.badblockpos.
As this chip-specific information is not directly rel
From: Frieder Schrempf
Currently supported bad block marker positions within the block are:
* in first page only
* in last page only
* in first or second page
Some ESMT NANDs are known to have been shipped by the manufacturer
with bad block markers in the first or last page, instead of the
first
From: Frieder Schrempf
It is known that some ESMT SLC NANDs have been shipped
with the factory bad block markers in the first or last page
of the block, instead of the first or second page. To be on
the safe side, let's check all three locations.
Signed-off-by: Frieder Schrempf
Reviewed-by: Bor
From: Frieder Schrempf
According to the datasheet of some Cypress SLC NANDs, the bad
block markers can be in the first, second or last page of a block.
So let's check all three locations.
Signed-off-by: Frieder Schrempf
Reviewed-by: Boris Brezillon
---
drivers/mtd/nand/raw/nand_amd.c | 8
Karel Zak wrote:
> It seems more elegant is to ask for Nth option as expected by fsinfo().
More elegant yes, but there's an issue with atomiticity[*]. I'm in the
process of switching to something that returns you a single buffer with all
the options in, but each key and each value is preceded b
From: Frieder Schrempf
To be able to check and set bad block markers in the first and
second page of a block independently of each other, we create
separate flags for both cases.
Previously NAND_BBM_SECONDPAGE meant, that both, the first and the
second page were used. With this patch NAND_BBM_FI
On 2019-01-30 21:41, Petr Mladek wrote:
On Tue 2019-01-29 10:50:54, Josh Poimboeuf wrote:
On Mon, Jan 28, 2019 at 02:49:43PM -0500, Joe Lawrence wrote:
> On Sun, Jan 27, 2019 at 04:26:30AM +0900, Alice Ferrazzi wrote:
> > This patch fixes a checkpatch warning:
> > WARNING: ENOSYS means 'inva
From: Frieder Schrempf
Currently supported bad block marker positions within the block are:
* in first page only
* in last page only
* in first or second page
After some cleanup and preparation in patch 1 and 2, we make it
possible to set NAND_BBM_FIRSTPAGE, NAND_BBM_SECONDPAGE and
NAND_BBM_LAST
On Tue, 29 Jan 2019 at 17:21, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.154 release.
> There are 44 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.
>
> Res
On Wed, Jan 30, 2019 at 06:22:47AM +0100, Vincent Guittot wrote:
> The algorithm used to order cfs_rq in rq->leaf_cfs_rq_list assumes that
> it will walk down to root the 1st time a cfs_rq is used and we will finish
> to add either a cfs_rq without parent or a cfs_rq with a parent that is
> alread
They are not used at all, remove them.
Signed-off-by: Axel Lin
---
drivers/regulator/lp8788-ldo.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/regulator/lp8788-ldo.c b/drivers/regulator/lp8788-ldo.c
index a2ef146e6b3a..172b5f9355dd 100644
--- a/drivers/regulator/lp8788-ldo.c
++
It is not used at all, remove it.
Signed-off-by: Axel Lin
---
drivers/regulator/lp8788-buck.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/regulator/lp8788-buck.c b/drivers/regulator/lp8788-buck.c
index 30de784d8e30..f84167688e5e 100644
--- a/drivers/regulator/lp8788-buck.c
+++ b
Not all 64 interrupts may be used in one group. e.g. most irqsteer in
imx8qxp and imx8qm subsystems supports only 32 interrupts.
And one irqsteer channel can support up to 8 output interrupts.
This patch series aims to support 32 interrupts chan and multi output
interrupts.
Tested on:
iMX8QXP MEK
Not all 64 interrupts may be used in one group. e.g. most irqsteer in
imx8qxp and imx8qm subsystems supports only 32 interrupts.
As the IP integration parameters are Channel number and interrupts number,
let's use fsl,num-irqs to represents how many interrupts supported
by this irqsteer channel.
One group can manage 64 interrupts by using two registers (e.g. STATUS/SET).
However, the integrated irqsteer may support only 32 interrupts which
needs only one register in a group. But the current driver assume there's
a mininum of two registers in a group which result in a wrong register map
for
One irqsteer channel can support up to 8 output interrupts.
Cc: Marc Zyngier
Cc: Lucas Stach
Cc: Shawn Guo
Signed-off-by: Dong Aisheng
---
ChangeLog:
v1->v2:
* calculate irq_count by fsl,num-irqs instead of parsing interrupts
property from devicetree to match the input interrupts and outpu
One irqsteer channel can support up to 8 output interrupts.
Cc: Marc Zyngier
Cc: Rob Herring
Cc: Lucas Stach
Cc: Shawn Guo
Cc: devicet...@vger.kernel.org
Signed-off-by: Dong Aisheng
---
ChangeLog:
v1->v2:
* remove one unnecessary note.
---
.../devicetree/bindings/interrupt-controller/fsl,ir
On Wed, Jan 30, 2019 at 12:16 PM Vincent Guittot
wrote:
>
> A deadlock has been seen when swicthing clocksources which use PM runtime.
> The call path is:
> change_clocksource
> ...
> write_seqcount_begin
> ...
> timekeeping_update
> ...
> sh_cmt_clocksource_enable
On Wed, Jan 30, 2019 at 02:04:10PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 30, 2019 at 06:22:47AM +0100, Vincent Guittot wrote:
>
> > The algorithm used to order cfs_rq in rq->leaf_cfs_rq_list assumes that
> > it will walk down to root the 1st time a cfs_rq is used and we will finish
> > to add
On Mon, 21 Jan 2019, Pi-Hsun Shih wrote:
> Since a SCP and EC would both exist on a system, and use the cros_ec_dev
> driver, we need to differentiate between them for the userspace, or they
> would both be registered at /dev/cros_ec, causing a conflict.
>
> Cc: Enric Balletbo Serra
> Cc: Guente
On 30/01/2019 08:24, Jason Yan wrote:
If the device is unplugged or disconnected, the negotiated_linkrate
still can be seen from the userspace by sysfs. This makes people
confused and leaks information of the device last used. So let's reset
the negotiated_linkrate after the phy is down.
Signed-
On Mon, 21 Jan 2019, Jarkko Nikula wrote:
> INTEL_SOC_PMIC, INTEL_SOC_PMIC_CHTWC and MFD_TPS68470 select the
> I2C_DESIGNWARE_PLATFORM without its dependencies making it possible to see
> warning and build error like below:
>
> WARNING: unmet direct dependencies detected for I2C_DESIGNWARE_PLATFO
On Wed, Jan 30, 2019 at 01:41:56PM +0100, Petr Mladek wrote:
> Hmm, the error code is passed to the syscall, for example:
>
> + SYSCALL_DEFINE3(init_module
> + load_module()
> + do_init_module()
> + do_one_initcall(mod->init);
>
> I am not sure if we are allowed to return -ENOTSUPP (-
Thanks Aisheng for the comments!
+int imx_sc_pm_cpu_start(struct imx_sc_ipc *ipc, u32 resource,
> > + bool enable, u64 address)
> > +{
> > + struct imx_sc_msg_req_cpu_start msg;
> > + struct imx_sc_rpc_msg *hdr = &msg.hdr;
> > +
> > + hdr->ver = IMX_SC_RPC
With the following commit:
73d5e2b47264 ("cpu/hotplug: detect SMT disabled by BIOS")
... the hotplug code attempted to detect when SMT was disabled by BIOS,
in which case it reported SMT as permanently disabled. However, that
code broke a virt hotplug scenario, where the guest is booted with o
Fix booting time warnings.
On Wed, Jan 30, 2019 at 9:12 PM Daniel Baluta wrote:
>
> Thanks Aisheng for the comments!
>
>
>
> +int imx_sc_pm_cpu_start(struct imx_sc_ipc *ipc, u32 resource,
> > > + bool enable, u64 address)
> > > +{
> > > + struct imx_sc_msg_req_cpu_start msg;
> > > + struct
Dt-bindings doc about CPU node of Ingenic XBurst based SOCs.
Signed-off-by: Zhou Yanjie
---
.../devicetree/bindings/mips/ingenic/ingenic,cpu.txt| 17 +
1 file changed, 17 insertions(+)
create mode 100644
Documentation/devicetree/bindings/mips/ingenic/ingenic,cpu.txt
diff -
On Tue, 29 Jan 2019 at 17:13, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.19 release.
> There are 103 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.
>
> Re
On Fri, 2019-01-25 at 01:03 +0900, Masahiro Yamada wrote:
> On Tue, Jan 22, 2019 at 1:17 AM Leonard Crestez
> wrote:
> >
> > On 1/7/2019 9:31 PM, Leonard Crestez wrote:
> > > The dts makefiles go through a lot of pointless churn when boards are
> > > added. Many SOCs (such as imx) have very simp
On Tue, 29 Jan 2019 at 18:36, Qian Cai wrote:
>
> Read efi_page_tables debugfs triggering an out-of-bounds access here,
>
> arch/arm64/mm/dump.c: 282
> if (addr >= st->marker[1].start_address) {
>
> from,
>
> arch/arm64/mm/dump.c: 331
> note_page(st, addr, 2, pud_val(pud));
>
> because st->marker+
On Wed, 30 Jan 2019 at 14:06, Rafael J. Wysocki wrote:
>
> On Wed, Jan 30, 2019 at 12:16 PM Vincent Guittot
> wrote:
> >
> > A deadlock has been seen when swicthing clocksources which use PM runtime.
> > The call path is:
> > change_clocksource
> > ...
> > write_seqcount_begin
> > ...
Am Mittwoch, den 30.01.2019, 13:05 + schrieb Aisheng Dong:
> One irqsteer channel can support up to 8 output interrupts.
>
> > Cc: Marc Zyngier
> > Cc: Rob Herring
> > Cc: Lucas Stach
> > Cc: Shawn Guo
> Cc: devicet...@vger.kernel.org
> > Signed-off-by: Dong Aisheng
> ---
> ChangeLog:
> v
Am Mittwoch, den 30.01.2019, 13:05 + schrieb Aisheng Dong:
> Not all 64 interrupts may be used in one group. e.g. most irqsteer in
> imx8qxp and imx8qm subsystems supports only 32 interrupts.
>
> As the IP integration parameters are Channel number and interrupts number,
> let's use fsl,num-irq
On Wed, Jan 30, 2019 at 12:48:42PM +, Li,Rongqing wrote:
>
>
> > -邮件原件-
> > 发件人: linux-kernel-ow...@vger.kernel.org
> > [mailto:linux-kernel-ow...@vger.kernel.org] 代表 Greg KH
> > 发送时间: 2019年1月30日 18:19
> > 收件人: Li,Rongqing
> > 抄送: jsl...@suse.com; linux-kernel@vger.kernel.org; gko...
Current kernels complain when booting on CI20:
[0.329630] cacheinfo: Failed to find cpu0 device node
[0.335023] cacheinfo: Unable to detect cache hierarchy for CPU 0
Add the CPU node and the L2 cache node, then let each CPU point to it.
Signed-off-by: Zhou Yanjie
---
arch/mips/boot/dts/i
Am Mittwoch, den 30.01.2019, 13:06 + schrieb Aisheng Dong:
> One group can manage 64 interrupts by using two registers (e.g. STATUS/SET).
> However, the integrated irqsteer may support only 32 interrupts which
> needs only one register in a group. But the current driver assume there's
> a minin
On 2019-01-30 13:59:55 [+0100], Heiko Carstens wrote:
> Last lines of trace below (full log attached):
<...>-56956 [005] 658.931364: handle_futex_death: uaddr:
3ff9e880c58 pi: 1
…
<...>-56956 [005] 658.931369: handle_futex_death: uaddr:
3ff9e8808c0 success
David Howells writes:
> You need to rebase on linus/master. A bunch of your patches are obsoleted by
> Al's security changes there.
Before anything is merged definitely.
Al dealt with mount options from the LSMs in a slightly different way
than I did. At a practical level Als version of the c
On Wed, 30 Jan 2019, Heiko Carstens wrote:
> On Wed, Jan 30, 2019 at 01:15:18PM +0100, Thomas Gleixner wrote:
> > On Wed, 30 Jan 2019, Heiko Carstens wrote:
> > > On Tue, Jan 29, 2019 at 06:16:53PM +0100, Sebastian Sewior wrote:
> > > > if (unlikely(p->flags & PF_KTHREAD)) {
> > > >
On Fri, 25 Jan 2019, Brian Masney wrote:
> Convert the PM8XXX IRQ code to use the version 2 IRQ interface in order
> to support hierarchical IRQ chips. This is necessary so that ssbi-gpio
> can be setup as a hierarchical IRQ chip with PM8xxx as the parent. IRQ
> chips in device tree should be usab
On Wed, Jan 30, 2019 at 02:06:20PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 30, 2019 at 02:04:10PM +0100, Peter Zijlstra wrote:
> > So I don't much like this; at all. But maybe I misunderstand, this is
> > somewhat tricky stuff and I've not looked at it in a while.
> >
> > So per normal we do:
On Wed, 30 Jan 2019, Michael Ellerman wrote:
> I'm happy to take it, unless there's some reason you'd rather it go via
> the LP tree?
As this is more about reliable stack unwinding than live patching per se
(which is only a user of that facility), I'd actually slightly prefer if
it goes via yo
On Wed, 30 Jan 2019 13:01:44 +
Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The information about where the manufacturer puts the bad block
> markers inside the bad block and in the OOB data is stored in
> different places. Let's move this information to nand_chip.options
> and nand
On Wed, 30 Jan 2019, Sebastian Sewior wrote:
> On 2019-01-30 13:59:55 [+0100], Heiko Carstens wrote:
> > Last lines of trace below (full log attached):
>
> <...>-56956 [005] 658.931364: handle_futex_death: uaddr:
> 3ff9e880c58 pi: 1
> …
> <...>-56956 [005] 6
On Wed, 30 Jan 2019 at 14:27, Peter Zijlstra wrote:
>
> On Wed, Jan 30, 2019 at 02:06:20PM +0100, Peter Zijlstra wrote:
> > On Wed, Jan 30, 2019 at 02:04:10PM +0100, Peter Zijlstra wrote:
>
> > > So I don't much like this; at all. But maybe I misunderstand, this is
> > > somewhat tricky stuff and
This is done via RPC call to SCU.
Signed-off-by: Daniel Baluta
---
Changes since v2: (as per Aisheng's review)
- rename address with phys_address
- remove unnecessary uint8_t cast
- use 'true' as last parameter of imx_scu_call_rpc to actually
wait for a response fr
Thomas,
On Fri, 25 Jan 2019, Brian Masney wrote:
> Check to see if the hwirq is already associated with another virq on
> this IRQ domain. If so, then disassociate it before associating the
> hwirq with the new virq.
>
> This is a temporary hack that is needed in order to not break git
> bisect
Am Mittwoch, den 30.01.2019, 13:06 + schrieb Aisheng Dong:
> One irqsteer channel can support up to 8 output interrupts.
>
> > Cc: Marc Zyngier
> > Cc: Lucas Stach
> > Cc: Shawn Guo
> > Signed-off-by: Dong Aisheng
> ---
> ChangeLog:
> v1->v2:
> * calculate irq_count by fsl,num-irqs instea
On Wed, Jan 30, 2019 at 9:21 PM Lucas Stach wrote:
>
> Am Mittwoch, den 30.01.2019, 13:05 + schrieb Aisheng Dong:
> > One irqsteer channel can support up to 8 output interrupts.
> >
> > > Cc: Marc Zyngier
> > > Cc: Rob Herring
> > > Cc: Lucas Stach
> > > Cc: Shawn Guo
> > Cc: devicet...@vg
On 1/30/19 9:18 AM, h...@owltronix.com wrote:
From: Hans Holmberg
pblk stripes writes of minimal write size across all non-offline chunks
in a line, which means that the maximum write pointer delta should not
exceed the minimal write size.
Extend the line write pointer balance check to cover t
On Tue, 29 Jan 2019 at 17:08, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.20.6 release.
> There are 117 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.
>
> Res
On Sun, 27 Jan 2019, Chen-Yu Tsai wrote:
> gpiod_get_value() gives out a warning if access to the underlying gpiochip
> requires sleeping, which is common for I2C based chips:
>
> WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
> gpiod_get_value+0xd0/0x100
> Modules linked in:
>
David Howells writes:
> Karel Zak wrote:
>
>> It seems more elegant is to ask for Nth option as expected by fsinfo().
>
> More elegant yes, but there's an issue with atomiticity[*]. I'm in the
> process of switching to something that returns you a single buffer with all
> the options in, but ea
On Tue, 22 Jan 2019, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
> int stuff
On Tue, 22 Jan 2019, Gustavo A. R. Silva wrote:
> There is a potential NULL pointer dereference in case devm_kzalloc()
> fails and returns NULL.
>
> Fix this by adding a NULL check on *lookup*
>
> This bug was detected with the help of Coccinelle.
>
> Fixes: b2e6392f ("i2c: gpio: Convert to
Hi Boris,
Thanks for reviewing.
On 30.01.19 14:28, Boris Brezillon wrote:
> On Wed, 30 Jan 2019 13:01:44 +
> Schrempf Frieder wrote:
>
>> From: Frieder Schrempf
>>
>> The information about where the manufacturer puts the bad block
>> markers inside the bad block and in the OOB data is stor
On 三, 2019-01-30 at 10:59 +0100, Petr Mladek wrote:
> On Sat 2019-01-19 17:15:23, Luc Van Oostenryck wrote:
> >
> > This variable is declared as:
> > static struct powerclamp_worker_data * __percpu worker_data;
> > In other words, a percpu pointer to struct ...
> >
> > But this variable not u
On Wed, 30 Jan 2019 13:01:47 +
Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> To be able to check and set bad block markers in the first and
> second page of a block independently of each other, we create
> separate flags for both cases.
>
> Previously NAND_BBM_SECONDPAGE meant, that
On 三, 2019-01-30 at 11:04 +0100, Daniel Lezcano wrote:
> On 30/01/2019 10:25, Pi-Hsun Shih wrote:
> >
> > On Wed, Jan 30, 2019 at 3:44 PM Daniel Lezcano
> > wrote:
> > >
> > >
> > > On 30/01/2019 07:04, Peter Shih wrote:
> > > >
> > > > Adding Michael Kao to cc list.
> > > >
> > > > On Wed, J
On Mon 2019-01-21 10:04:08, Mike Rapoport wrote:
> As all the memblock allocation functions return NULL in case of error
> rather than panic(), the duplicates with _nopanic suffix can be removed.
>
> Signed-off-by: Mike Rapoport
> Acked-by: Greg Kroah-Hartman
> ---
> arch/arc/kernel/unwind.c
On 1/30/19 11:26 AM, Javier González wrote:
In order to respect mw_cuinits, pblk's write buffer maintains a
backpointer to protect data not yet persisted; when writing to the write
buffer, this backpointer defines a threshold that pblk's rate-limiter
enforces.
On small PU configurations, the fol
On Wed, Jan 30, 2019 at 02:29:42PM +0100, Vincent Guittot wrote:
> On Wed, 30 Jan 2019 at 14:27, Peter Zijlstra wrote:
> >
> > On Wed, Jan 30, 2019 at 02:06:20PM +0100, Peter Zijlstra wrote:
> > > On Wed, Jan 30, 2019 at 02:04:10PM +0100, Peter Zijlstra wrote:
> >
> > > > So I don't much like this
On 三, 2019-01-30 at 21:37 +0800, Zhang Rui wrote:
> On 三, 2019-01-30 at 10:59 +0100, Petr Mladek wrote:
> >
> > On Sat 2019-01-19 17:15:23, Luc Van Oostenryck wrote:
> > >
> > >
> > > This variable is declared as:
> > > static struct powerclamp_worker_data * __percpu worker_data;
> > > In othe
Karel Zak writes:
> On Tue, Jan 29, 2019 at 03:44:22PM -0600, Eric W. Biederman wrote:
>> so I am proposing we change this in the new mount api.
>
> Well, this forces me to ask what the new API is? :-)
>
> It seems that David uses fsconfig() and fsinfo() to set and get
> mount options, and your p
On 28/01/2019 12:47, Marc Zyngier wrote:
> On Mon, 21 Jan 2019 15:33:45 +,
> Julien Thierry wrote:
>>
>> Add a build option and a command line parameter to build and enable the
>> support of pseudo-NMIs.
>>
>> Signed-off-by: Julien Thierry
>> Suggested-by: Daniel Thompson
>> Cc: Catalin M
kvm->debugfs_dentry).
On 2019/01/30 20:32, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 02495e76ded5 Add linux-next specific files for 20190130
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10
Add missing .owner field in regulator_desc, which is used for refcounting.
Signed-off-by: Axel Lin
---
drivers/regulator/max77620-regulator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/max77620-regulator.c
b/drivers/regulator/max77620-regulator.c
index cd93cf53e23c.
Add missing .owner field in regulator_desc, which is used for refcounting.
Signed-off-by: Axel Lin
---
drivers/regulator/max77650-regulator.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/regulator/max77650-regulator.c
b/drivers/regulator/max77650-regulator.c
index 5afb91400
On Mon, Jan 7, 2019 at 4:12 PM Laurentiu Tudor wrote:
>
>
>
> On 09.11.2018 11:51, Brajeswar Ghosh wrote:
> > Remove linux/fsl/mc.h which is included more than once
> >
> > Signed-off-by: Brajeswar Ghosh
>
> Acked-by: Laurentiu Tudor
>
> ---
> Best Regards, Laurentiu
If no further comment, can
Hi Brian,
On 25/01/2019 16:22, Brian Masney wrote:
> Add a new function irq_domain_translate_twocell() that is to be used as
> the translate function in struct irq_domain_ops for v2 IRQ interfaces.
> This is based on irq_domain_xlate_twocell().
>
> Signed-off-by: Brian Masney
> ---
> include/li
>From fd653e8dd0d5368cd0cd9ccd89cf3001e4584f8a Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Wed, 30 Jan 2019 22:21:45 +0900
Subject: [PATCH] block: pass no-op callback to INIT_WORK().
syzbot is hitting flush_work() warning caused by commit 4d43d395fed12463
("workqueue: Try to catch flush_wor
From: Georg Ottinger
Having a brief look at at91_adc_read_raw() it is obvious that in the case
of a timeout the setting of AT91_ADC_CHDR and AT91_ADC_IDR registers is
omitted. If 2 different channels are queried we can end up with a
situation where two interrupts are enabled, but only one interru
+Rob,
On 30/01/19 15:00, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On 30/01/19 6:11 PM, Roger Quadros wrote:
>> Kishon,
>>
>> On 30/01/19 12:59, Kishon Vijay Abraham I wrote:
>>> Hi Roger,
>>>
>>> On 30/01/19 4:18 PM, Roger Quadros wrote:
Hi Kishon,
On 24/01/19 12:48, Kishon Vi
On Fri, Dec 21, 2018 at 6:06 PM Souptick Joarder wrote:
>
> On Fri, Dec 21, 2018 at 2:49 PM Brajeswar Ghosh
> wrote:
> >
> > Remove hwmgr_ppt.h which is included more than once
> >
> > Signed-off-by: Brajeswar Ghosh
> > ---
> Acked-by: Souptick Joarder
If no further comment, can we get this pa
Hi,
On 30/01/19 7:27 PM, Roger Quadros wrote:
> +Rob,
>
> On 30/01/19 15:00, Kishon Vijay Abraham I wrote:
>> Hi Roger,
>>
>> On 30/01/19 6:11 PM, Roger Quadros wrote:
>>> Kishon,
>>>
>>> On 30/01/19 12:59, Kishon Vijay Abraham I wrote:
Hi Roger,
On 30/01/19 4:18 PM, Roger Quadros
On Wed, Jan 30, 2019 at 06:22:47AM +0100, Vincent Guittot wrote:
> Sargun reported a crash:
> "I picked up c40f7d74c741a907cfaeb73a7697081881c497d0 sched/fair: Fix
>infinite loop in update_blocked_averages() by reverting a9e7f6544b9c
>and put it on top of 4.19.13. In addition to this, I u
On Wed, Jan 30, 2019 at 03:01:04PM +0100, Peter Zijlstra wrote:
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -282,13 +282,15 @@ static inline struct cfs_rq *group_cfs_r
> return grp->my_q;
> }
>
> -static inline void list_add_leaf_cfs_rq(struct cfs_rq *cfs_rq)
> +static inl
On Wed, Jan 30, 2019 at 9:33 PM Lucas Stach wrote:
>
> Am Mittwoch, den 30.01.2019, 13:06 + schrieb Aisheng Dong:
> > One irqsteer channel can support up to 8 output interrupts.
> >
> > > Cc: Marc Zyngier
> > > Cc: Lucas Stach
> > > Cc: Shawn Guo
> > > Signed-off-by: Dong Aisheng
> > ---
>
Hello,
syzbot found the following crash on:
HEAD commit:30e5c2c6bf28 net: Revert devlink health changes.
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1249a2b8c0
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
dashboard link:
On Tue, Jan 29, 2019 at 10:41 AM Florian Westphal wrote:
>
> syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:085c4c7dd2b6 net: lmc: remove -I. header search path
> > git tree: net-next
> > console output: https://syzkaller.appspot.com/x/log.txt?
Hi Andreas,
> Am 30.01.2019 um 10:02 schrieb Johan Hovold :
>
> On Mon, Jan 28, 2019 at 05:44:29PM +0100, Andreas Kemnade wrote:
>> On Mon, 28 Jan 2019 08:53:56 +0100
>> Johan Hovold wrote:
>>
>>> On Fri, Jan 25, 2019 at 08:43:10PM +0100, Andreas Kemnade wrote:
The GTA04 has a w2sg0004 or
> Waiman Long (4):
> locking/qspinlock: Handle > 4 slowpath nesting levels
> locking/qspinlock_stat: Track the no MCS node available case
I've taken these two,
> locking/qspinlock_stat: Introduce a generic lockevent counting APIs
> locking/lock_events: Make lock_events available for all a
On Mon, Jan 15, 2018 at 06:44:56PM +0600, Aleksey Makarov wrote:
> From: Radoslaw Biernacki
>
> This patch adds support for the Precision Time Protocol
> Clocks and Timestamping hardware found on Cavium ThunderX
> processors.
>
> Signed-off-by: Radoslaw Biernacki
> Signed-off-by: Aleksey Makaro
Am Mittwoch, den 30.01.2019, 22:03 +0800 schrieb Dong Aisheng:
> > On Wed, Jan 30, 2019 at 9:33 PM Lucas Stach wrote:
> >
> > Am Mittwoch, den 30.01.2019, 13:06 + schrieb Aisheng Dong:
> > > One irqsteer channel can support up to 8 output interrupts.
> > >
> > > > > > > > Cc: Marc Zyngier
>
Dmitry Vyukov wrote:
> > syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:085c4c7dd2b6 net: lmc: remove -I. header search path
> > > git tree: net-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=12347128c0
> > >
On Wed, Jan 30, 2019 at 01:31:31PM +0100, Andrea Parri wrote:
> On Wed, Jan 30, 2019 at 01:18:51PM +0200, Elena Reshetova wrote:
> > This adds an smp_acquire__after_ctrl_dep() barrier on successful
> > decrease of refcounter value from 1 to 0 for refcount_dec(sub)_and_test
> > variants and therefor
On Wed, Jan 23, 2019 at 12:41:16PM +0100, Christian Brauner wrote:
> binderfs should not have a separate device_initcall(). When a kernel is
> compiled with CONFIG_ANDROID_BINDERFS register the filesystem alongside
> CONFIG_ANDROID_IPC. This use-case is especially sensible when users specify
> CONF
301 - 400 of 1221 matches
Mail list logo
