From: Allen Pais <apais@linux.microsoft.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Allen Pais <allen.lkml@gmail.com>
Cc: davem@davemloft.net, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, ludovic.desroches@microchip.com,
jesper.nilsson@axis.com, lars.persson@axis.com,
horia.geanta@nxp.com, aymen.sghaier@nxp.com,
gcherian@marvell.com, thomas.lendacky@amd.com,
john.allen@amd.com, gilad@benyossef.com, bbrezillon@kernel.org,
arno@natisbad.org, schalla@marvell.com, matthias.bgg@gmail.com,
jamie@jamieiles.com, giovanni.cabiddu@intel.com, heiko@sntech.de,
krzk@kernel.org, vz@mleia.com, k.konieczny@samsung.com,
linux-crypto@vger.kernel.org, linux-mediatek@lists.infradead.org,
qat-linux@intel.com, linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Romain Perier <romain.perier@gmail.com>
Subject: Re: [PATCH v5 01/19] crypto: amcc: convert tasklets to use new tasklet_setup() API
Date: Tue, 9 Mar 2021 14:59:51 +0530 [thread overview]
Message-ID: <2e2604a3-b0b1-92f2-aa7b-f413fae4cb51@linux.microsoft.com> (raw)
In-Reply-To: <20210304062644.GA5107@gondor.apana.org.au>
>>
>> In preparation for unconditionally passing the
>> struct tasklet_struct pointer to all tasklet
>> callbacks, switch to using the new tasklet_setup()
>> and from_tasklet() to pass the tasklet pointer explicitly.
>>
>> Signed-off-by: Romain Perier <romain.perier@gmail.com>
>> Signed-off-by: Allen Pais <apais@linux.microsoft.com>
>> ---
>> drivers/crypto/amcc/crypto4xx_core.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> This introduces a compiler warning with C=1 W=1.
Okay. I will check and send out a fix.
Thanks.
next prev parent reply other threads:[~2021-03-09 9:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 9:42 [PATCH v5 00/19]crypto: convert tasklets to use new tasklet_setup API() Allen Pais
2021-02-08 9:42 ` [PATCH v5 01/19] crypto: amcc: convert tasklets to use new tasklet_setup() API Allen Pais
2021-03-04 6:26 ` Herbert Xu
2021-03-09 9:29 ` Allen Pais [this message]
2021-02-08 9:42 ` [PATCH v5 02/19] crypto: atmel: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 03/19] crypto: axis: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 04/19] crypto: caam: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 05/19] crypto: cavium: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 06/19] crypto: ccp: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 07/19] crypto: ccree: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 08/19] crypto: hifn_795x: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 09/19] crypto: img-hash: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 10/19] crypto: ixp4xx: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 11/19] crypto: mediatek: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 12/19] crypto: omap: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 13/19] crypto: picoxcell: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 14/19] crypto: qat: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 15/19] crypto: qce: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 16/19] crypto: rockchip: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 17/19] crypto: s5p: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 18/19] crypto: talitos: " Allen Pais
2021-02-08 9:42 ` [PATCH v5 19/19] crypto: octeontx: " Allen Pais
2021-02-08 9:46 ` [PATCH v5 00/19]crypto: convert tasklets to use new tasklet_setup API() Allen Pais
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=2e2604a3-b0b1-92f2-aa7b-f413fae4cb51@linux.microsoft.com \
--to=apais@linux.microsoft.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allen.lkml@gmail.com \
--cc=arno@natisbad.org \
--cc=aymen.sghaier@nxp.com \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=gcherian@marvell.com \
--cc=gilad@benyossef.com \
--cc=giovanni.cabiddu@intel.com \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=jamie@jamieiles.com \
--cc=jesper.nilsson@axis.com \
--cc=john.allen@amd.com \
--cc=k.konieczny@samsung.com \
--cc=krzk@kernel.org \
--cc=lars.persson@axis.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=matthias.bgg@gmail.com \
--cc=nicolas.ferre@microchip.com \
--cc=qat-linux@intel.com \
--cc=romain.perier@gmail.com \
--cc=schalla@marvell.com \
--cc=thomas.lendacky@amd.com \
--cc=vz@mleia.com \
/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