From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: David Miller <davem@davemloft.net>,
steffen.klassert@secunet.com,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux NetDev <netdev@vger.kernel.org>,
Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [PATCH] net-xfrm: add build time cfg option to PF_KEY SHA256 to use RFC4868-compliant truncation
Date: Tue, 16 Oct 2018 01:08:57 -0700 [thread overview]
Message-ID: <CAHo-OozFUHVJuqd3R7HF=MYG8cNAzVCsLsg2LBnA6JZ2Z0vNeA@mail.gmail.com> (raw)
In-Reply-To: <20181016080634.139776-1-zenczykowski@gmail.com>
Yes, I realize there's been similar submits in the past,
but we're trying to get rid of or upstream android kernel networking
divergences...
maybe this approach will be more palatable?
Thanks,
Maciej
next prev parent reply other threads:[~2018-10-16 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 8:06 [PATCH] net-xfrm: add build time cfg option to PF_KEY SHA256 to use RFC4868-compliant truncation Maciej Żenczykowski
2018-10-16 8:08 ` Maciej Żenczykowski [this message]
2018-10-16 8:14 ` Lorenzo Colitti
2018-10-17 5:59 ` Herbert Xu
2018-10-17 6:01 ` Maciej Żenczykowski
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='CAHo-OozFUHVJuqd3R7HF=MYG8cNAzVCsLsg2LBnA6JZ2Z0vNeA@mail.gmail.com' \
--to=zenczykowski@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).