From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linuxppc-dev@ozlabs.org, "Kim Phillips" <kim.phillips@arm.com>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
"Horia Geantă" <horia.geanta@nxp.com>
Subject: Re: [PATCH] crypto: talitos - Fix sparse warnings
Date: Thu, 8 Oct 2020 11:50:21 +0200 [thread overview]
Message-ID: <1716ab93-cd9d-bbb3-a954-f3f8378da437@csgroup.eu> (raw)
In-Reply-To: <20201007065048.GA25944@gondor.apana.org.au>
Le 07/10/2020 à 08:50, Herbert Xu a écrit :
> On Sat, Oct 03, 2020 at 07:15:53PM +0200, Christophe Leroy wrote:
>>
>> The following changes fix the sparse warnings with less churn:
>
> Yes that works too. Can you please submit this patch?
>
This fixed two independant commits from the past. I sent out two fix patches.
Christophe
prev parent reply other threads:[~2020-10-08 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201002115236.GA14707@gondor.apana.org.au>
[not found] ` <be222fed-425b-d55c-3efc-9c4e873ccf8e@csgroup.eu>
[not found] ` <20201002124223.GA1547@gondor.apana.org.au>
[not found] ` <20201002124341.GA1587@gondor.apana.org.au>
2020-10-03 17:15 ` [PATCH] crypto: talitos - Fix sparse warnings Christophe Leroy
2020-10-07 6:50 ` Herbert Xu
2020-10-08 9:50 ` Christophe Leroy [this message]
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=1716ab93-cd9d-bbb3-a954-f3f8378da437@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kim.phillips@arm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).