[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1503081633300.20994@utopia.booyaka.com>
Date: Sun, 8 Mar 2015 16:35:13 +0000 (UTC)
From: Paul Walmsley <paul@...an.com>
To: Pali Rohár <pali.rohar@...il.com>
cc: Aaro Koskinen <aaro.koskinen@....fi>,
Tony Lindgren <tony@...mide.com>,
Benoît Cousson <bcousson@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Russell King <linux@....linux.org.uk>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
Pavel Machek <pavel@....cz>, Nishanth Menon <nm@...com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Sebastian Reichel <sre@...nel.org>
Subject: Re: [PATCH 00/10] omap3 crypto fixes
On Sun, 8 Mar 2015, Pali Rohár wrote:
> On Friday 06 March 2015 23:23:06 Aaro Koskinen wrote:
> > On Fri, Mar 06, 2015 at 10:36:32AM -0800, Tony Lindgren wrote:
> > > Are there any fixes in this series that should go into
> > > v4.0-rc series, or can it all wait for v4.1?
> >
> > I think these all should wait for v4.1.
> >
> > A.
>
> I would suggest to include at least patches 01, 04, 06. Probably
> those could go to -stable tree... but this decision is up to you.
I'm not sure patch 1 is a fix. As far as I know we haven't
run into any issues with it on real hardware - only on QEMU - unless you
know otherwise, Pali? Are we sure that the QEMU model behavior matches
the hardware?
- Paul
Powered by blists - more mailing lists