From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, ek@google.com, fgont@si6networks.com,
lorenzo@google.com, hideaki.yoshifuji@miraclelinux.com
Subject: Re: [PATCH net-next v2 0/8] ipv6: RFC7217 stable privacy addresses implementation
Date: Mon, 23 Mar 2015 22:15:29 -0400 (EDT) [thread overview]
Message-ID: <20150323.221529.1733601437583593221.davem@davemloft.net> (raw)
In-Reply-To: <cover.1427149704.git.hannes@stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Mon, 23 Mar 2015 23:35:58 +0100
> this is an implementation of basic support for RFC7217 stable privacy
> addresses. Please review and consider for net-next.
>
> v2:
> * Correct references to RFC 7212 -> RFC 7217 in documentation patch (thanks, Eric!)
Applied, thanks!
prev parent reply other threads:[~2015-03-24 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 22:35 [PATCH net-next v2 0/8] ipv6: RFC7217 stable privacy addresses implementation Hannes Frederic Sowa
2015-03-23 22:35 ` [PATCH net-next v2 1/8] lib: EXPORT_SYMBOL sha_init Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 2/8] ipv6: introduce secret_stable to ipv6_devconf Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 3/8] ipv6: generation of stable privacy addresses for link-local and autoconf Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 4/8] ipv6: introduce IFA_F_STABLE_PRIVACY flag Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 5/8] ipv6: collapse state_lock and lock Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 6/8] ipv6: do retries on stable privacy addresses Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 7/8] ipv6: introduce idgen_delay and idgen_retries knobs Hannes Frederic Sowa
2015-03-23 22:36 ` [PATCH net-next v2 8/8] ipv6: add documentation for stable_secret, " Hannes Frederic Sowa
2015-03-24 2:15 ` David Miller [this message]
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=20150323.221529.1733601437583593221.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ek@google.com \
--cc=fgont@si6networks.com \
--cc=hannes@stressinduktion.org \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=lorenzo@google.com \
--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).