From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Horia Geanta <horia.geanta@nxp.com>,
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 v1 2/5] crypto: talitos - move struct talitos_edesc into talitos.h
Date: Tue, 11 Jun 2019 14:38:30 +0200 [thread overview]
Message-ID: <a3474daf-3e51-4ce9-0634-8690c2e3045d@c-s.fr> (raw)
In-Reply-To: <VI1PR0402MB3485848D81EF07419EB0128F98ED0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Le 11/06/2019 à 13:57, Horia Geanta a écrit :
> On 6/6/2019 2:31 PM, Christophe Leroy wrote:
>> Next patch will require struct talitos_edesc to be defined
>> earlier in talitos.c
>>
>> This patch moves it into talitos.h so that it can be used
>> from any place in talitos.c
>>
>> Fixes: 37b5e8897eb5 ("crypto: talitos - chain in buffered data for ahash on SEC1")
> This isn't really a fix, so please drop the tag.
As the next patch requires this one and Fixes 37b5e8897eb5, by setting
Fixes: 37b5e8897eb5 here was for me a way to tell stable that this one
is required for the following one.
Otherwise, how can I ensure that this one will be taken when next one is
taken ?
Christophe
>
> Thanks,
> Horia
>
next prev parent reply other threads:[~2019-06-11 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 11:31 [PATCH v1 0/5] Additional fixes on Talitos driver Christophe Leroy
2019-06-06 11:31 ` [PATCH v1 1/5] crypto: talitos - fix ECB and CBC algs ivsize Christophe Leroy
2019-06-11 11:52 ` Horia Geanta
2019-06-11 14:04 ` Christophe Leroy
2019-06-06 11:31 ` [PATCH v1 2/5] crypto: talitos - move struct talitos_edesc into talitos.h Christophe Leroy
2019-06-11 11:57 ` Horia Geanta
2019-06-11 12:38 ` Christophe Leroy [this message]
2019-06-11 13:06 ` Horia Geanta
2019-06-06 11:31 ` [PATCH v1 3/5] crypto: talitos - fix hash on SEC1 Christophe Leroy
2019-06-06 11:31 ` [PATCH v1 4/5] crypto: talitos - eliminate unneeded 'done' functions at build time Christophe Leroy
2019-06-06 11:31 ` [PATCH v1 5/5] crypto: talitos - drop icv_ool Christophe Leroy
2019-06-11 12:09 ` [PATCH v1 0/5] Additional fixes on Talitos driver Horia Geanta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3474daf-3e51-4ce9-0634-8690c2e3045d@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®