From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephen Rothwell <sfr@canb.auug.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: Sat, 11 Feb 2017 18:56:21 +0800 [thread overview]
Message-ID: <20170211105621.GJ855@gondor.apana.org.au> (raw)
In-Reply-To: <20170210141251.03b39b40@canb.auug.org.au>
On Fri, Feb 10, 2017 at 02:12:51PM +1100, Stephen Rothwell wrote:
>
> I am still getting these warnings ... I have seen no updates to the
> crypot tree since Feb 2.
Sorry Stephen. I have now applied Arnd's fixes for this problem
and it should be pushed out.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2017-02-11 10:56 UTC|newest]
Thread overview: 23+ 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 ` linux-next: build warnings after merge of the crypto tree Stephen Rothwell
2017-02-11 10:56 ` Herbert Xu [this message]
2017-02-12 23:42 ` Stephen Rothwell
2017-02-06 10:15 ` Cyrille Pitchen
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=20170211105621.GJ855@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=cyrille.pitchen@atmel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.