From: David Miller <davem@davemloft.net>
To: dborkman@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next 0/7] IPv6 MLD updates
Date: Fri, 30 Aug 2013 14:38:46 -0400 (EDT) [thread overview]
Message-ID: <20130830.143846.2250283565647562811.davem@davemloft.net> (raw)
In-Reply-To: <1377881908-8022-1-git-send-email-dborkman@redhat.com>
From: Daniel Borkmann <dborkman@redhat.com>
Date: Fri, 30 Aug 2013 18:58:21 +0200
> If there are no further objections, I'll send out the non-RFC version on
> Monday after some more testing. That's just a heads up. This set includes
> my improved fix from yesterday as well besides other things.
>
> Thanks!
>From a coding style and general correctness perspective these changes
look fine to me.
I'll let IPV6 MLD experts comment on the semantic part.
prev parent reply other threads:[~2013-08-30 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 16:58 [RFC PATCH net-next 0/7] IPv6 MLD updates Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 1/7] net: ipv6: mld: fix v1/v2 switchback timeout to rfc3810, 9.12 Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 2/7] net: ipv6: mld: clean up MLD_V1_SEEN macro Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 3/7] net: ipv6: mld: get rid of MLDV2_MRC and simplify calculation Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 4/7] net: ipv6: mld: implement RFC3810 MLDv2 mode only Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 5/7] net: ipv6: mld: restrict min/max of sysctl force_mld_version Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 6/7] net: ipv6: mld: similarly to MLDv2 have min max_delay of 1 Daniel Borkmann
2013-08-30 16:58 ` [RFC PATCH net-next 7/7] net: ipv6: mld: document force_mld_version in ip-sysctl.txt Daniel Borkmann
2013-08-30 18:38 ` David Miller [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=20130830.143846.2250283565647562811.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).