From: Jiri Pirko <jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>
To: Lubomir Rintel <lkundrak-NGH9Lh4a5iE@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
Alexey Kuznetsov <kuznet-v/Mj1YrvjDBInbfyfbPRSQ@public.gmane.org>
Subject: Re: [PATCH v2] ipv6: expose RFC4191 route preference via rtnetlink
Date: Wed, 11 Mar 2015 16:01:29 +0100 [thread overview]
Message-ID: <20150311150129.GE2057@nanopsycho.orion> (raw)
In-Reply-To: <1426084761-3303-1-git-send-email-lkundrak-NGH9Lh4a5iE@public.gmane.org>
Wed, Mar 11, 2015 at 03:39:21PM CET, lkundrak-NGH9Lh4a5iE@public.gmane.org wrote:
>This makes it possible to retain the route preference when RAs are handled in
>userspace.
>
>Signed-off-by: Lubomir Rintel <lkundrak-NGH9Lh4a5iE@public.gmane.org>
Reviewed-by: Jiri Pirko <jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>
next prev parent reply other threads:[~2015-03-11 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 10:01 [PATCH] ipv6: expose RFC4191 route preference via rtnetlink Lubomir Rintel
2015-03-03 15:17 ` Jiri Pirko
[not found] ` <20150303151715.GA2020-6KJVSR23iU5sFDB2n11ItA@public.gmane.org>
2015-03-10 15:56 ` Lubomir Rintel
2015-03-10 16:04 ` Jiri Pirko
[not found] ` <20150310160423.GC2016-6KJVSR23iU488b5SBfVpbw@public.gmane.org>
2015-03-11 14:39 ` [PATCH v2] " Lubomir Rintel
[not found] ` <1426084761-3303-1-git-send-email-lkundrak-NGH9Lh4a5iE@public.gmane.org>
2015-03-11 15:01 ` Jiri Pirko [this message]
2015-03-12 3:28 ` 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=20150311150129.GE2057@nanopsycho.orion \
--to=jiri-rhqaubhg3fbzbrfiqnyvsa@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=kuznet-v/Mj1YrvjDBInbfyfbPRSQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lkundrak-NGH9Lh4a5iE@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).