From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752893AbbCHQfR (ORCPT ); Sun, 8 Mar 2015 12:35:17 -0400 Received: from utopia.booyaka.com ([74.50.51.50]:39331 "EHLO utopia.booyaka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752582AbbCHQfO (ORCPT ); Sun, 8 Mar 2015 12:35:14 -0400 Date: Sun, 8 Mar 2015 16:35:13 +0000 (UTC) From: Paul Walmsley To: =?ISO-8859-15?Q?Pali_Roh=E1r?= cc: Aaro Koskinen , Tony Lindgren , =?ISO-8859-15?Q?Beno=EEt_Cousson?= , Rob Herring , Russell King , Herbert Xu , "David S. Miller" , linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Pavel Machek , Nishanth Menon , Ivaylo Dimitrov , Sebastian Reichel Subject: Re: [PATCH 00/10] omap3 crypto fixes In-Reply-To: <201503081101.37452@pali> Message-ID: References: <1424958600-18881-1-git-send-email-pali.rohar@gmail.com> <20150306183631.GA13520@atomide.com> <20150306222306.GB587@fuloong-minipc.musicnaut.iki.fi> <201503081101.37452@pali> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="843723315-361176072-1425832513=:20994" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --843723315-361176072-1425832513=:20994 Content-Type: TEXT/PLAIN; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 8 Mar 2015, Pali Roh=C3=A1r 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? > >=20 > > I think these all should wait for v4.1. > >=20 > > A. >=20 > I would suggest to include at least patches 01, 04, 06. Probably=20 > 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=20 run into any issues with it on real hardware - only on QEMU - unless you=20 know otherwise, Pali? Are we sure that the QEMU model behavior matches=20 the hardware? - Paul --843723315-361176072-1425832513=:20994--