From: Jeremy Kerr <jk@ozlabs.org>
To: patchwork@ozlabs.org
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
oliver@hartkopp.net, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] can: af_can.c use rcu_barrier() on module unload.
Date: Wed, 10 Jun 2009 22:41:47 +1000 [thread overview]
Message-ID: <200906102241.47823.jk@ozlabs.org> (raw)
In-Reply-To: <20090610.015245.141342130.davem@davemloft.net>
David,
> We really can't expect patchwork to look for every conceivable
> malignment of the various reviewer tags.
No, but we could probably be more tolerant about capitalisation. Any
objections about ignoring case completely? I have a patch ready to
push...
Cheers,
Jeremy
next parent reply other threads:[~2009-06-10 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A2D112A.4000308@hartkopp.net>
[not found] ` <4A2F6D32.8030400@hartkopp.net>
[not found] ` <20090610.015245.141342130.davem@davemloft.net>
2009-06-10 12:41 ` Jeremy Kerr [this message]
2009-06-10 16:45 ` [PATCH 3/5] can: af_can.c use rcu_barrier() on module unload 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=200906102241.47823.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@hartkopp.net \
--cc=patchwork@ozlabs.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).