From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Florent Fourcot <florent.fourcot@enst-bretagne.fr>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] ipv6: add ip6_flowlabel_consistency sysctl
Date: Wed, 15 Jan 2014 01:59:49 +0100 [thread overview]
Message-ID: <20140115005948.GA19945@order.stressinduktion.org> (raw)
In-Reply-To: <1389721816-21165-3-git-send-email-florent.fourcot@enst-bretagne.fr>
On Tue, Jan 14, 2014 at 06:50:16PM +0100, Florent Fourcot wrote:
> diff --git a/kernel/sysctl_binary.c b/kernel/sysctl_binary.c
> index 653cbbd..7c32501 100644
> --- a/kernel/sysctl_binary.c
> +++ b/kernel/sysctl_binary.c
> @@ -557,6 +557,7 @@ static const struct bin_table bin_net_ipv6_table[] = {
> { CTL_DIR, NET_IPV6_ROUTE, "route", bin_net_ipv6_route_table },
> { CTL_DIR, NET_IPV6_ICMP, "icmp", bin_net_ipv6_icmp_table },
> { CTL_INT, NET_IPV6_BINDV6ONLY, "bindv6only" },
> + { CTL_INT, NET_IPV6_FLOWLABEL_CONSISTENCY, "ip6_flowlabel_consistency" },
> { CTL_INT, NET_IPV6_IP6FRAG_HIGH_THRESH, "ip6frag_high_thresh" },
> { CTL_INT, NET_IPV6_IP6FRAG_LOW_THRESH, "ip6frag_low_thresh" },
> { CTL_INT, NET_IPV6_IP6FRAG_TIME, "ip6frag_time" },
This hunk is not necessary and should get removed. bin_tables are legacy. Also
I didn't see NET_IPV6_FLOWLABEL_CONSISTENCY getting defined. ;)
Greetings,
Hannes
prev parent reply other threads:[~2014-01-15 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:50 [PATCH net-next 1/3] ipv6: add the IPV6_FL_F_REFLECT flag to IPV6_FL_A_GET Florent Fourcot
2014-01-14 17:50 ` [PATCH net-next 2/3] ipv6: add a flag to get the flow label used remotly Florent Fourcot
2014-01-14 17:50 ` [PATCH net-next 3/3] ipv6: add ip6_flowlabel_consistency sysctl Florent Fourcot
2014-01-15 0:59 ` Hannes Frederic Sowa [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=20140115005948.GA19945@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=florent.fourcot@enst-bretagne.fr \
--cc=netdev@vger.kernel.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