From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: paulmck@linux.vnet.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com
Subject: Re: [PATCH net-next-2.6 v3] fasync: RCU and fine grained locking
Date: Wed, 21 Apr 2010 16:20:24 -0700 (PDT) [thread overview]
Message-ID: <20100421.162024.248644052.davem@davemloft.net> (raw)
In-Reply-To: <1271274935.16881.1746.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 14 Apr 2010 21:55:35 +0200
> [PATCH net-next-2.6 v3] fasync: RCU and fine grained locking
BTW, just to be clear I made sure to apply V3 of this
patch not the initial submission :-)
next prev parent reply other threads:[~2010-04-21 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 7:42 [PATCH net-next-2.6] fasync: RCU locking Eric Dumazet
2010-04-14 8:36 ` Lai Jiangshan
2010-04-14 14:57 ` Eric Dumazet
2010-04-14 15:34 ` Eric Dumazet
2010-04-14 19:55 ` [PATCH net-next-2.6 v3] fasync: RCU and fine grained locking Eric Dumazet
2010-04-21 23:20 ` David Miller [this message]
2010-04-14 15:41 ` [PATCH net-next-2.6] fasync: RCU locking Paul E. McKenney
2010-04-21 23:19 ` 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=20100421.162024.248644052.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).