From: roopa <roopa@cumulusnetworks•com>
To: Robert Shearman <rshearma@brocade•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org,
"Eric W. Biederman" <ebiederm@xmission•com>,
Thomas Graf <tgraf@suug•ch>
Subject: Re: [PATCH net-next] mpls: Use definition for reserved label checks
Date: Mon, 03 Aug 2015 14:45:19 -0700 [thread overview]
Message-ID: <55BFE0EF.5010000@cumulusnetworks.com> (raw)
In-Reply-To: <1438620604-18746-1-git-send-email-rshearma@brocade.com>
On 8/3/15, 9:50 AM, Robert Shearman wrote:
> In multiple locations there are checks for whether the label in hand
> is a reserved label or not using the arbritray value of 16. Factor
> this out into a #define for better maintainability and for
> documentation.
>
> Signed-off-by: Robert Shearman <rshearma@brocade•com>
> ---
Acked-by: Roopa Prabhu <roopa@cumulusnetworks•com>
next prev parent reply other threads:[~2015-08-03 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 16:50 [PATCH net-next] mpls: Use definition for reserved label checks Robert Shearman
2015-08-03 21:45 ` roopa [this message]
2015-08-04 5:35 ` 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=55BFE0EF.5010000@cumulusnetworks.com \
--to=roopa@cumulusnetworks$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ebiederm@xmission$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rshearma@brocade$(echo .)com \
--cc=tgraf@suug$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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