From: David Miller <davem@davemloft.net>
To: kurt.van.dijck@eia.be
Cc: socketcan@hartkopp.net, netdev@vger.kernel.org,
eric.dumazet@gmail.com, urs@isnogud.escape.de
Subject: Re: [PATCH net-next-2.6 v2] can: convert protocol handling to RCU
Date: Wed, 06 Apr 2011 12:36:14 -0700 (PDT) [thread overview]
Message-ID: <20110406.123614.115926059.davem@davemloft.net> (raw)
In-Reply-To: <20110406153440.GA2277@kurt.e-circ.dyndns.org>
From: Kurt Van Dijck <kurt.van.dijck@eia.be>
Date: Wed, 6 Apr 2011 17:34:40 +0200
> Acked-by: Kurt Van Dijck <kurt.van.dijck@eia.be>
Applied, thanks everyone.
prev parent reply other threads:[~2011-04-06 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 18:01 [PATCH net-next-2.6 v2] can: convert protocol handling to RCU Oliver Hartkopp
2011-04-06 9:27 ` Kurt Van Dijck
2011-04-06 14:39 ` Oliver Hartkopp
2011-04-06 15:34 ` Kurt Van Dijck
2011-04-06 19:36 ` 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=20110406.123614.115926059.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kurt.van.dijck@eia.be \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=urs@isnogud.escape.de \
/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).