From: Johannes Berg <johannes@sipsolutions.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH 0/6] crypto: Make all AEAD users include aead.h
Date: Wed, 22 Apr 2015 09:18:48 +0200 [thread overview]
Message-ID: <1429687128.2185.0.camel@sipsolutions.net> (raw)
In-Reply-To: <20150422070455.GA8351@gondor.apana.org.au>
On Wed, 2015-04-22 at 15:04 +0800, Herbert Xu wrote:
> Hi:
>
> This series adds inclusions of aead.h to all AEAD users including
> AEAD implementors (where it's internal/aead.h). This is necessary
> because I'll be adding an updated AEAD interface and that will live
> in aead.h instead of crypto.h.
>
> Dave, if it's OK with you I'd like to push the last two patches
> through my tree as the new AEAD interface would depend on them.
Looks good to me. Fine with me if you do that for the mac80211 patch,
I'm not expecting to change that file and cause conflicts.
johannes
next prev parent reply other threads:[~2015-04-22 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 7:04 [PATCH 0/6] crypto: Make all AEAD users include aead.h Herbert Xu
2015-04-22 7:06 ` [PATCH 1/6] crypto: arm64/aes-ce-ccm - Include crypto/internal/aead.h Herbert Xu
2015-04-22 7:06 ` [PATCH 2/6] crypto: algif_aead - Include crypto/aead.h Herbert Xu
2015-04-22 7:06 ` [PATCH 3/6] crypto: tcrypt " Herbert Xu
2015-04-22 7:06 ` [PATCH 4/6] crypto: testmgr " Herbert Xu
2015-04-22 7:06 ` [PATCH 5/6] mac80211: " Herbert Xu
2015-04-22 7:06 ` [PATCH 6/6] mac802154: " Herbert Xu
2015-04-22 7:18 ` Johannes Berg [this message]
2015-04-22 15:41 ` [PATCH 0/6] crypto: Make all AEAD users include aead.h David Miller
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=1429687128.2185.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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).