Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Horia Geanta <horia.geanta@nxp.com>
To:     Christophe Leroy <christophe.leroy@c-s.fr>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        "David S. Miller" <davem@davemloft.net>
CC:     "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 1/4] crypto: talitos - move struct talitos_edesc into
 talitos.h
Thread-Topic: [PATCH v2 1/4] crypto: talitos - move struct talitos_edesc into
 talitos.h
Thread-Index: AQHVIGOHWjiLuJ/iA0u2rV751i1YWQ==
Date:   Thu, 13 Jun 2019 12:39:34 +0000
Message-ID: <VI1PR0402MB348514C4AA9E41C26FF4430998EF0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
References: <cover.1560263641.git.christophe.leroy@c-s.fr>
 <d9b5fade242f0806a587392d31c272709949479f.1560263641.git.christophe.leroy@c-s.fr>
 <VI1PR0402MB3485C0F4CB13F8674B8B5A5598EF0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
 <7fb54918-4524-1e6b-dd29-46be8843577b@c-s.fr>
 <VI1PR0402MB34858ABA5DE0324FA6E2CFCD98EF0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
 <ce6beda2-75c8-f360-9e01-5a883128d153@c-s.fr>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8939f288-383a-4459-90af-08d6effc30aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2019 12:39:34.5426
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: horia.geanta@nxp.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0402MB2943
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-crypto.vger.kernel.org>
X-Mailing-List: linux-crypto@vger.kernel.org

On 6/13/2019 3:32 PM, Christophe Leroy wrote:=0A=
> =0A=
> =0A=
> Le 13/06/2019 =E0 14:24, Horia Geanta a =E9crit=A0:=0A=
>> On 6/13/2019 3:16 PM, Christophe Leroy wrote:=0A=
>>>=0A=
>>>=0A=
>>> Le 13/06/2019 =E0 14:13, Horia Geanta a =E9crit=A0:=0A=
>>>> On 6/11/2019 5:39 PM, Christophe Leroy wrote:=0A=
>>>>> Next patch will require struct talitos_edesc to be defined=0A=
>>>>> earlier in talitos.c=0A=
>>>>>=0A=
>>>>> This patch moves it into talitos.h so that it can be used=0A=
>>>>> from any place in talitos.c=0A=
>>>>>=0A=
>>>>> Fixes: 37b5e8897eb5 ("crypto: talitos - chain in buffered data for ah=
ash on SEC1")=0A=
>>>>> Cc: stable@vger.kernel.org=0A=
>>>>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>=0A=
>>>> Again, this patch does not qualify as a fix.=0A=
>>>>=0A=
>>>=0A=
>>> But as I said, the following one is a fix and require that one, you tol=
d=0A=
>>> me to add stable in Cc: to make it explicit it was to go into stable.=
=0A=
>> Yes, but you should remove the Fixes tag.=0A=
>> And probably replace "Next patch" with the commit headline.=0A=
>>=0A=
>>> If someone tries to merge following one into stable with taking that on=
e=0A=
>>> first, build will fail.=0A=
>> This shouldn't happen, order from main tree should be preserved.=0A=
>>=0A=
> =0A=
> When they pick up fixes, AFAIK they don't take all the preceeding commits=
.=0A=
> =0A=
This is not about Fixes tag, but Cc tag:=0A=
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#opt=
ion-1=0A=
=0A=
Horia=0A=