From: Harsh Jain <harsh@chelsio•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Herbert Xu <herbert@gondor•apana.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the crypto tree
Date: Mon, 19 Mar 2018 11:14:14 +0530 [thread overview]
Message-ID: <dbcf6dc6-919c-1b7e-5a6c-c4181fd29c40@chelsio.com> (raw)
In-Reply-To: <20180319120433.24cc4be1@canb.auug.org.au>
On 19-03-2018 06:34, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/crypto/chelsio/chcr_ipsec.c:66:0:
> drivers/crypto/chelsio/chcr_crypto.h:343:12: warning: 'chcr_ahash_continue' declared 'static' but never defined [-Wunused-function]
> static int chcr_ahash_continue(struct ahash_request *req);
> ^~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 5110e65536f3 ("crypto: chelsio -Split Hash requests for large scatter gather list")
>
Hi Stephen/Herbert,
I will submit the fix to cryptodev tree.
Thanks & Regards
Harsh Jain
next prev parent reply other threads:[~2018-03-19 5:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 1:04 linux-next: build warning after merge of the crypto tree Stephen Rothwell
2018-03-19 5:44 ` Harsh Jain [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 3:07 Stephen Rothwell
2025-10-20 2:53 Stephen Rothwell
2025-10-20 3:34 ` Bagas Sanjaya
2025-06-16 5:31 Stephen Rothwell
2024-10-08 6:29 Stephen Rothwell
2024-02-12 3:48 Stephen Rothwell
2024-02-12 12:59 ` Cabiddu, Giovanni
2022-11-21 1:52 Stephen Rothwell
2022-07-11 10:49 Stephen Rothwell
2019-08-23 3:14 Stephen Rothwell
2019-08-25 18:01 ` Hans de Goede
2019-02-04 0:01 Stephen Rothwell
2018-10-05 5:31 Stephen Rothwell
2018-01-19 1:49 Stephen Rothwell
2018-01-19 4:21 ` Harsh Jain
2018-01-19 5:12 ` Herbert Xu
2017-07-31 2:17 Stephen Rothwell
2017-07-31 13:50 ` Gary R Hook
2016-08-25 1:38 Stephen Rothwell
2016-08-25 6:20 ` Martin Schwidefsky
2016-08-25 7:47 ` Herbert Xu
2016-08-25 11:14 ` Stephen Rothwell
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=dbcf6dc6-919c-1b7e-5a6c-c4181fd29c40@chelsio.com \
--to=harsh@chelsio$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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