[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1706272006140.1890@nanos>
Date: Tue, 27 Jun 2017 20:07:25 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Brian Norris <briannorris@...omium.org>
cc: Linus Walleij <linus.walleij@...aro.org>,
Heiko Stuebner <heiko@...ech.de>,
linux-rockchip@...ts.infradead.org,
Julia Cartwright <julia@...com>,
LKML <linux-kernel@...r.kernel.org>, linux-gpio@...r.kernel.org,
John Keeping <john@...anate.com>, linux-pm@...r.kernel.org,
Doug Anderson <dianders@...omium.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Tony Lindgren <tony@...mide.com>,
"David.Wu" <david.wu@...k-chips.com>,
'黄涛' <huangtao@...k-chips.com>
Subject: Re: [PATCH for 4.12] Revert "pinctrl: rockchip: avoid hardirq-unsafe
functions in irq_chip"
On Tue, 27 Jun 2017, Brian Norris wrote:
> On Tue, Jun 27, 2017 at 03:06:26PM +0200, Thomas Gleixner wrote:
> > That said, the commit should be reverted and the issue needs to analyzed
> > proper. We still need the RCU -> SCRU conversion, but that's a different
> > problem.
>
> Can we consider this an "ack" for the $subject then? Heiko also gave his
> approval. How can this get merged? It's running a bit late for 4.12,
> though it really shouldn't be risky (at least for non-RT stuff that was
> working warning-free already in 4.11), but a 4.13-rc1 with -stable tag
> could work as well.
Yes. That revert can go into 4.12 from my POV, but I leave that to Linus.
Thanks,
tglx
Powered by blists - more mailing lists