From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, thaller@redhat.com,
stephen@networkplumber.org, hannes@stressinduktion.org,
vyasevich@gmail.com, dcbw@redhat.com
Subject: Re: [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses
Date: Mon, 11 Nov 2013 18:03:02 -0500 (EST) [thread overview]
Message-ID: <20131111.180302.121736785883262610.davem@davemloft.net> (raw)
In-Reply-To: <20131111210404.GB2397@minipsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Mon, 11 Nov 2013 22:04:04 +0100
> Anyway, should I touch the state in netdev patchwork or should I always
> leave that to you?
>
> I'm used to set "changes requested" before I send another patch version
> and "RFC" when I send RFC patch.
I'd rather others not touch the patchwork state.
You plan to send this again, so whether it's marked RFC or changes requested
is not all that important :-)
prev parent reply other threads:[~2013-11-11 23:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:49 [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses Jiri Pirko
2013-11-11 14:49 ` [patch net-next RFC 1/2] ipv6 addrconf: extend ifa_flags to u32 Jiri Pirko
2013-11-11 15:07 ` David Laight
2013-11-11 15:12 ` Jiri Pirko
2013-11-11 14:49 ` [patch net-next RFC 2/2] ipv6 addrconf: introduce IFA_F_MANAGETEMPADDR to tell kernel to manage temporary addresses Jiri Pirko
2013-11-15 17:48 ` [PATCH 1/1] fixup! " Thomas Haller
2013-11-18 10:23 ` Jiri Pirko
2013-11-15 18:04 ` [patch net-next RFC 2/2] " Thomas Haller
2013-11-11 14:50 ` [patch iproute2 RFC 1/2] add support for extended ifa_flags Jiri Pirko
2013-11-11 14:50 ` [patch iproute2 RFC 2/2] add support for IFA_F_MANAGETEMPADDR Jiri Pirko
2013-11-11 18:42 ` [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses David Miller
2013-11-11 19:49 ` Jiri Pirko
2013-11-11 20:01 ` David Miller
2013-11-11 21:04 ` Jiri Pirko
2013-11-11 23:03 ` 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=20131111.180302.121736785883262610.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=thaller@redhat.com \
--cc=vyasevich@gmail.com \
--cc=yoshfuji@linux-ipv6.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).