From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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>,
Harsh Jain <harsh@chelsio.com>
Subject: linux-next: build warning after merge of the crypto tree
Date: Mon, 19 Mar 2018 12:04:33 +1100 [thread overview]
Message-ID: <20180319120433.24cc4be1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-03-19 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 1:04 Stephen Rothwell [this message]
2018-03-19 5:44 ` linux-next: build warning after merge of the crypto tree Harsh Jain
-- strict thread matches above, loose matches on Subject: below --
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=20180319120433.24cc4be1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=harsh@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).