From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the crypto tree
Date: Fri, 10 Feb 2017 14:12:51 +1100 [thread overview]
Message-ID: <20170210141251.03b39b40@canb.auug.org.au> (raw)
In-Reply-To: <20170206090340.GA9531@gondor.apana.org.au>
Hi Herbert,
On Mon, 6 Feb 2017 17:03:40 +0800 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> > warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has unmet direct dependencies (CRYPTO && CRYPTO_HW && ARCH_AT91)
> > warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has unmet direct dependencies (CRYPTO && CRYPTO_HW && ARCH_AT91)
> >
> > Introduced by commit
> >
> > 89a82ef87e01 ("crypto: atmel-authenc - add support to authenc(hmac(shaX), Y(aes)) modes")
> >
> > In file included from include/linux/printk.h:329:0,
> > from include/linux/kernel.h:13,
> > from drivers/crypto/atmel-sha.c:17:
>
> This patch should fix both issues. Thanks,
I am still getting these warnings ... I have seen no updates to the
crypot tree since Feb 2.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-02-10 3:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 1:28 linux-next: build warnings after merge of the crypto tree Stephen Rothwell
2017-02-06 9:03 ` Herbert Xu
2017-02-06 12:54 ` crypto: atmel - Fix authenc compile test warnings kbuild test robot
2017-02-06 16:58 ` kbuild test robot
2017-02-06 19:02 ` kbuild test robot
2017-02-10 3:12 ` Stephen Rothwell [this message]
2017-02-11 10:56 ` linux-next: build warnings after merge of the crypto tree Herbert Xu
2017-02-12 23:42 ` Stephen Rothwell
2017-02-06 10:15 ` Cyrille Pitchen
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 3:19 Stephen Rothwell
2019-08-01 1:53 Stephen Rothwell
2015-03-10 5:44 Stephen Rothwell
2015-03-10 6:03 ` Herbert Xu
2015-03-10 6:44 ` Stephen Rothwell
2015-03-10 7:02 ` Stephan Mueller
2015-03-11 0:56 ` Stephen Rothwell
2015-03-11 0:57 ` Herbert Xu
2015-03-11 2:00 ` Tadeusz Struk
2015-03-11 2:05 ` Herbert Xu
2014-08-26 6:14 Stephen Rothwell
2014-08-26 6:38 ` Herbert Xu
2014-08-26 7:00 ` Stephan Mueller
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=20170210141251.03b39b40@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cyrille.pitchen@atmel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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).