From: Ahmed Abdelsalam <amsalam20@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: davem@davemloft.net, linux-doc@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [net-next] ipv6: sr: Add documentation for seg_flowlabel sysctl
Date: Fri, 27 Apr 2018 17:53:20 +0200 [thread overview]
Message-ID: <20180427175320.9690fefcead52e3b73ad100f@gmail.com> (raw)
In-Reply-To: <e9dcc2ad-798f-5dce-a508-e3d1fb450d0e@infradead.org>
On Fri, 27 Apr 2018 08:47:14 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 04/27/2018 03:35 AM, Ahmed Abdelsalam wrote:
> > This patch adds a documentation for seg_flowlabel sysctl into
> > Documentation/networking/ip-sysctl.txt
> >
> > Signed-off-by: Ahmed Abdelsalam <amsalam20@gmail.com>
> > ---
> > Documentation/networking/ip-sysctl.txt | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
> > index 5dc1a04..7528f71 100644
> > --- a/Documentation/networking/ip-sysctl.txt
> > +++ b/Documentation/networking/ip-sysctl.txt
> > @@ -1428,6 +1428,19 @@ ip6frag_low_thresh - INTEGER
> > ip6frag_time - INTEGER
> > Time in seconds to keep an IPv6 fragment in memory.
> >
> > +IPv6 Segment Routing:
> > +
> > +seg6_flowlabel - INTEGER
> > + Controls the behaviour of computing the flowlabel of outer
> > + IPv6 header in case of SR T.encaps
> > +
> > + -1 set flowlabel to zero.
> > + 0 copy flowlabel from Inner paceket in case of Inner IPv6
>
> packet
>
Thanks
I fixed it in v2 of the patch.
--
Ahmed Abdelsalam <amsalam20@gmail.com>
prev parent reply other threads:[~2018-04-27 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 10:35 [net-next] ipv6: sr: Add documentation for seg_flowlabel sysctl Ahmed Abdelsalam
2018-04-27 15:47 ` Randy Dunlap
2018-04-27 15:53 ` Ahmed Abdelsalam [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=20180427175320.9690fefcead52e3b73ad100f@gmail.com \
--to=amsalam20@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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).