From: roopa <roopa@cumulusnetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [ANNOUNCE] iproute2 4.1.0
Date: Fri, 26 Jun 2015 15:35:04 -0700 [thread overview]
Message-ID: <558DD398.7020003@cumulusnetworks.com> (raw)
In-Reply-To: <20150626153349.2b0152c9@urahara>
On 6/26/15, 3:33 PM, Stephen Hemminger wrote:
> On Fri, 26 Jun 2015 14:49:11 -0700
> roopa <roopa@cumulusnetworks.com> wrote:
>
>> Hi Stephen,
>>
>> I don't see the below fix in the 4.1 tarball you point below:
>> https://patchwork.ozlabs.org/patch/479743/
>>
>> I am not sure yet if there was a problem with my submission. I intended
>> for it to go into 4.1.
>>
>> Thanks,
>> Roopa
> That is held off I thought mpls needed net-next (4.2) not 4.1.
> It is merged into master (post 4.1).
>
Mpls is in 4.1 and the route dels are broken without this fix.
Thanks,
Roopa
prev parent reply other threads:[~2015-06-26 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 20:06 [ANNOUNCE] iproute2 4.1.0 Stephen Hemminger
2015-06-26 21:49 ` roopa
2015-06-26 22:33 ` Stephen Hemminger
2015-06-26 22:35 ` roopa [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=558DD398.7020003@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).