From: Cong Wang <xiyou.wangcong@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: [Patch net-next 0/5] ipv6: clean up locking in anycast and mcast
Date: Wed, 10 Sep 2014 16:54:07 -0700 [thread overview]
Message-ID: <CAM_iQpWX0vkjGJWwhtfGr8KCJ15AVREWttSxvcFQrfzRzAWfYA@mail.gmail.com> (raw)
In-Reply-To: <20140910.130150.1203685634918422464.davem@davemloft.net>
On Wed, Sep 10, 2014 at 1:01 PM, David Miller <davem@davemloft.net> wrote:
> From: Cong Wang <xiyou.wangcong@gmail.com>
> Date: Tue, 9 Sep 2014 16:52:13 -0700
>
>> This patchset cleans up the locking in anycast.c and mcast.c.
>>
>> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
>
> Please update this based upon the feedback you've received.
>
Sure thing, done.
prev parent reply other threads:[~2014-09-10 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 23:52 [Patch net-next 0/5] ipv6: clean up locking in anycast and mcast Cong Wang
2014-09-09 23:52 ` [Patch net-next 1/5] ipv6: drop useless rcu_read_lock() in anycast Cong Wang
2014-09-09 23:52 ` [Patch net-next 2/5] ipv6: remove ipv6_sk_ac_lock Cong Wang
2014-09-09 23:52 ` [Patch net-next 3/5] ipv6: clean up ipv6_dev_ac_inc() Cong Wang
2014-09-10 12:23 ` Hannes Frederic Sowa
2014-09-10 21:32 ` Cong Wang
2014-09-09 23:52 ` [Patch net-next 4/5] ipv6: drop ipv6_sk_mc_lock in mcast Cong Wang
2014-09-10 17:16 ` Sabrina Dubroca
2014-09-10 22:36 ` Cong Wang
2014-09-09 23:52 ` [Patch net-next 5/5] ipv6: drop some rcu_read_lock " Cong Wang
2014-09-10 20:01 ` [Patch net-next 0/5] ipv6: clean up locking in anycast and mcast David Miller
2014-09-10 23:54 ` Cong Wang [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=CAM_iQpWX0vkjGJWwhtfGr8KCJ15AVREWttSxvcFQrfzRzAWfYA@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).