From: Oliver Hartkopp <oliver@hartkopp.net>
To: David Miller <davem@davemloft.net>
Cc: patchwork@ozlabs.org, netdev@vger.kernel.org,
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 10:22:10 +0200 [thread overview]
Message-ID: <4A2F6D32.8030400@hartkopp.net> (raw)
In-Reply-To: <20090610.011027.43904351.davem@davemloft.net>
David Miller wrote:
> From: Oliver Hartkopp <oliver@hartkopp.net>
> Date: Mon, 08 Jun 2009 15:24:58 +0200
>
>> Acked-By: Oliver Hartkopp <oliver@hartkopp.net>
>
> Please don't capitalize the "By" in "Acked-By".
Sorry.
> Otherwise
> patchwork doesn't pick them up automatically.
IMHO patchwork should be robust against these type of typos and convert them
for the users (== your) convenience into 'Acked-by:' ...
Regards,
Oliver
next prev parent reply other threads:[~2009-06-10 8:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 13:11 [PATCH 0/5] We must use rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 13:11 ` [PATCH 1/5] 8021q: Vlan driver should use rcu_barrier() on unload instead of syncronize_net() Jesper Dangaard Brouer
2009-06-08 15:54 ` Paul E. McKenney
2009-06-08 13:11 ` [PATCH 2/5] nfnetlink_queue: Use rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 16:05 ` Paul E. McKenney
2009-06-10 5:38 ` Andrew Morton
2009-06-08 13:11 ` [PATCH 3/5] can: af_can.c use " Jesper Dangaard Brouer
2009-06-08 13:24 ` Oliver Hartkopp
2009-06-10 8:10 ` David Miller
2009-06-10 8:22 ` Oliver Hartkopp [this message]
2009-06-10 8:52 ` David Miller
2009-06-10 12:41 ` Jeremy Kerr
2009-06-10 16:45 ` David Miller
2009-06-10 10:02 ` Alan Cox
2009-06-10 11:33 ` Jan Engelhardt
2009-06-08 16:13 ` Paul E. McKenney
2009-06-08 17:00 ` Oliver Hartkopp
2009-06-08 13:11 ` [PATCH 4/5] sctp: protocol.c call rcu_barrier() on unload Jesper Dangaard Brouer
2009-06-08 16:22 ` Paul E. McKenney
2009-06-09 15:44 ` Vlad Yasevich
2009-06-09 15:50 ` Paul E. McKenney
[not found] ` <20090609155011.GD6789-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-06-09 16:26 ` Vlad Yasevich
2009-06-08 13:11 ` [PATCH 5/5] sunrpc/auth_gss: Call rcu_barrier() on module unload Jesper Dangaard Brouer
2009-06-08 16:26 ` Paul E. McKenney
[not found] ` <20090608162656.GF6961-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-06-08 17:00 ` Trond Myklebust
[not found] ` <1244480449.5040.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-08 19:48 ` Jesper Dangaard Brouer
2009-06-08 21:13 ` Paul E. McKenney
2009-06-08 14:00 ` [PATCH 0/5] We must use " Patrick McHardy
2009-06-10 8:11 ` 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=4A2F6D32.8030400@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).