From: roopa <roopa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: ebiederm@xmission.com, rshearma@brocade.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6] mpls: support for dead routes
Date: Tue, 01 Dec 2015 20:39:16 -0800 [thread overview]
Message-ID: <565E75F4.80905@cumulusnetworks.com> (raw)
In-Reply-To: <20151201.154324.1248915135840079518.davem@davemloft.net>
On 12/1/15, 12:43 PM, David Miller wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
> Date: Sat, 28 Nov 2015 19:38:33 -0800
>
>> Adds support for RTNH_F_DEAD and RTNH_F_LINKDOWN flags on mpls
>> routes due to link events. Also adds code to ignore dead
>> routes during route selection.
> I agree with Robert's feedback that we probably should use
> ACCESS_ONCE(), optionally with a local variable.
>
> Please make this change and I'll apply this patch, thanks Roopa!
ack, will send v7. thanks for review all!.
prev parent reply other threads:[~2015-12-02 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 3:38 [PATCH net-next v6] mpls: support for dead routes Roopa Prabhu
2015-11-30 23:02 ` Robert Shearman
2015-12-01 20:43 ` David Miller
2015-12-02 4:39 ` 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=565E75F4.80905@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.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;
as well as URLs for NNTP newsgroup(s).