From: Andy Gospodarek <gospo@cumulusnetworks.com>
To: "Bjørnar Ness" <bjornar.ness@gmail.com>
Cc: Sowmini Varadhan <sowmini05@gmail.com>,
netdev <netdev@vger.kernel.org>,
Robert Shearman <rshearma@brocade.com>,
"John W. Linville" <linville@tuxdriver.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route
Date: Tue, 7 Apr 2015 22:52:16 -0400 [thread overview]
Message-ID: <20150408025215.GU1051@gospo> (raw)
In-Reply-To: <CAJO99TkSaJjmvTjWOpnMLwNaf7A-q9_DvkppT+M77rSV0Syh0w@mail.gmail.com>
On Tue, Apr 07, 2015 at 11:14:22PM +0200, Bjørnar Ness wrote:
> Hello, Andy.
>
> Are you working on the next version of this patchset with the suggested
> modifications?
Yes, I am.
I was planning to finish them tomorrow and test them before submitting
the next version. Are you asking as you wanted to provide some testing
feedback?
next prev parent reply other threads:[~2015-04-08 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 21:05 [RFC net-next/iproute2 0/2] net: infrastructure to support RFC-5549 Andy Gospodarek
2015-03-26 21:05 ` [RFC net-next 1/2] net: allow user to set IPv6 nexthop for IPv4 route Andy Gospodarek
2015-03-26 21:42 ` Sowmini Varadhan
2015-03-26 23:12 ` Julian Anastasov
2015-03-27 0:27 ` Andy Gospodarek
2015-03-27 11:53 ` Robert Shearman
2015-03-27 14:10 ` Andy Gospodarek
[not found] ` <CAJO99TkSaJjmvTjWOpnMLwNaf7A-q9_DvkppT+M77rSV0Syh0w@mail.gmail.com>
2015-04-08 2:52 ` Andy Gospodarek [this message]
2015-03-27 13:23 ` Sowmini Varadhan
2015-03-27 14:35 ` Andy Gospodarek
2015-03-27 14:37 ` Sowmini Varadhan
2015-03-26 21:05 ` [RFC iproute2 2/2] iproute2: " Andy Gospodarek
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=20150408025215.GU1051@gospo \
--to=gospo@cumulusnetworks.com \
--cc=bjornar.ness@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
--cc=sowmini05@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