From: Arnd Bergmann <arnd@arndb.de>
To: Barry Song <bs14@csr.com>
Cc: linux@arm.linux.org.uk, nico@fluxnic.net,
devicetree-discuss@lists.ozlabs.org, workgroup.linux@csr.com,
grant.likely@secretlab.ca, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform
Date: Thu, 7 Jul 2011 13:11:29 +0200 [thread overview]
Message-ID: <201107071311.29643.arnd@arndb.de> (raw)
In-Reply-To: <1310020616-27856-1-git-send-email-bs14@csr.com>
On Thursday 07 July 2011, Barry Song wrote:
> Changelogs:
> -v4:
> v3 got "Reviewed-by: Arnd Bergmann <arnd@arndb.de>"
> stopping the 0xffffffff madness for IO_SPACE_LIMIT
> fix .map_io compiling issue in the 1st patch
> fix set_next_event in timer.c
> rename GPU, USB, multimedia and SATA nodes in DTS
> delete redundant 0x in DTS
Note that when you get a 'Reviewed-by', 'Acked-by' or 'Tested-by'
reply to one of your mails, you should add that in the patch
changelog below your own 'Signed-off-by' in order to document
it for the future. This ususally still holds true when you make
further changes, just not when rewriting major parts of the patch.
For the Signed-off-by list, that should normally include only the
people that have handled the specific patch, it doesn't imply
authorship. Having seven people listed as Signed-off-by seems a bit
strange in this context, but there is no clear rule against it.
I would probably use 'Acked-by' or plain 'Cc' in the changelog for
some of the people, depending in what way they were involved.
At the least, you should have 'Signed-off-by' the person that wrote
most of the code, followed by the person that sends the patch at
the bottom of the list (as you did correctly).
Arnd
next prev parent reply other threads:[~2011-07-07 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 6:36 [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform Barry Song
2011-07-07 6:36 ` [PATCH v4 1/3] ARM: CSR: Adding CSR SiRFprimaII board support Barry Song
2011-07-07 6:36 ` [PATCH v4 2/3] ARM: CSR: mapping early DEBUG_LL uart Barry Song
2011-07-07 6:36 ` [PATCH v4 3/3] ARM: CSR: initializing L2 cache Barry Song
2011-07-07 11:11 ` Arnd Bergmann [this message]
2011-07-07 13:22 ` [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform Barry Song
[not found] ` <CAGsJ_4yd8i2V1FeKcELFrdRd+UxY9WLVV-dG9XnJmkxrYs8j5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-07 13:31 ` Arnd Bergmann
[not found] ` <201107071531.18623.arnd-r2nGTMty4D4@public.gmane.org>
2011-07-07 13:37 ` Barry Song
[not found] ` <CAGsJ_4zqny8_AYBTEnjOoERSrYxD_KOeWx1fPgpbP-yaQDbTZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-07 13:46 ` Arnd Bergmann
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=201107071311.29643.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=bs14@csr.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=tglx@linutronix.de \
--cc=workgroup.linux@csr.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).