From: Johannes Berg <johannes@sipsolutions.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Xiang Gao <qasdfgtyuiop@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] mac80211: aead api to reduce redundancy
Date: Mon, 25 Sep 2017 07:22:26 +0200 [thread overview]
Message-ID: <1506316946.2909.8.camel@sipsolutions.net> (raw)
In-Reply-To: <20170925045641.GB22947@gondor.apana.org.au>
On Mon, 2017-09-25 at 12:56 +0800, Herbert Xu wrote:
> On Sun, Sep 24, 2017 at 07:42:46PM +0200, Johannes Berg wrote:
> >
> > Unrelated to this, I'm not sure whose tree this should go through -
> > probably Herbert's (or DaveM's with his ACK? not sure if there's a
> > crypto tree?) or so?
>
> Since you're just rearranging code invoking the crypto API, rather
> than touching actual crypto API code, I think you should handle it
> as you do with any other wireless patch.
The code moves to crypto/ though, and I'm not even sure I can vouch for
the Makefile choice there.
johannes
next prev parent reply other threads:[~2017-09-25 5:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 5:40 [PATCH] mac80211: aead api to reduce redundancy Xiang Gao
2017-09-24 15:05 ` Johannes Berg
2017-09-24 17:21 ` Xiang Gao
2017-09-24 17:42 ` Johannes Berg
2017-09-24 18:39 ` Xiang Gao
2017-09-25 4:56 ` Herbert Xu
2017-09-25 5:22 ` Johannes Berg [this message]
2017-09-25 6:14 ` Herbert Xu
2017-09-28 8:06 ` [lkp-robot] [mac80211] 31e9170bde: hwsim.sta_dynamic_down_up.fail kernel test robot
2017-09-29 2:21 ` Xiang Gao
-- strict thread matches above, loose matches on Subject: below --
2017-09-26 13:19 [PATCH] mac80211: aead api to reduce redundancy Xiang Gao
2017-10-02 12:04 ` Johannes Berg
2017-10-08 5:43 ` Xiang Gao
2017-10-09 7:09 ` Johannes Berg
2017-10-11 2:31 ` Xiang Gao
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=1506316946.2909.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qasdfgtyuiop@gmail.com \
/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).