All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform
Date: Thu, 7 Jul 2011 15:31:18 +0200	[thread overview]
Message-ID: <201107071531.18623.arnd@arndb.de> (raw)
In-Reply-To: <CAGsJ_4yd8i2V1FeKcELFrdRd+UxY9WLVV-dG9XnJmkxrYs8j5A@mail.gmail.com>

On Thursday 07 July 2011, Barry Song wrote:
> > 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.
> 
> i am sure i know reviewed-by/acked-by/tested-by should be added to the
> end. what make me confused here is you are also the maintainer who
> will merge these changes into arm-soc and finally make them pulled by
> linus. generically,you will get the last signed-off-by too. if i list
> "reviewed-by you", you might need to replace it by signed-off-by
> finally.
> anyway, i'm really not sure whether i am understanding right about that :-)

The point is mostly that I tend to pull in patches from git, so I don't
add an explicit Signed-off-by to each patch. Also, the meaning of
Reviewed-by is stronger than just pulling a git tree, it means that
I looked at the code in much detail and am happy with the end result.

Simply pulling the patches can mean either that, or that I trust you
enough that I didn't bother looking (and/or don't care about the quality).

> > 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.
> 
> yes. i understand signed-off-by should only be given to people who
> make the essential code changes in the special patch and people who
> send or merge the special patch, but not the original author of the
> original source files. for the 1st patch which is the basic board
> support, in the long history of coding sirfprimaii, all the listed
> people have contributed codes. so i get the names of all of them
> shown. anyway, it is really too long....
> 

Not a problem. I basically wanted to make sure you know the rules,
and it seemed odd. It's probably ok to leave the list as it is.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Barry Song <21cnbao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	workgroup.linux-kQvG35nSl+M@public.gmane.org,
	tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform
Date: Thu, 7 Jul 2011 15:31:18 +0200	[thread overview]
Message-ID: <201107071531.18623.arnd@arndb.de> (raw)
In-Reply-To: <CAGsJ_4yd8i2V1FeKcELFrdRd+UxY9WLVV-dG9XnJmkxrYs8j5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thursday 07 July 2011, Barry Song wrote:
> > 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.
> 
> i am sure i know reviewed-by/acked-by/tested-by should be added to the
> end. what make me confused here is you are also the maintainer who
> will merge these changes into arm-soc and finally make them pulled by
> linus. generically,you will get the last signed-off-by too. if i list
> "reviewed-by you", you might need to replace it by signed-off-by
> finally.
> anyway, i'm really not sure whether i am understanding right about that :-)

The point is mostly that I tend to pull in patches from git, so I don't
add an explicit Signed-off-by to each patch. Also, the meaning of
Reviewed-by is stronger than just pulling a git tree, it means that
I looked at the code in much detail and am happy with the end result.

Simply pulling the patches can mean either that, or that I trust you
enough that I didn't bother looking (and/or don't care about the quality).

> > 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.
> 
> yes. i understand signed-off-by should only be given to people who
> make the essential code changes in the special patch and people who
> send or merge the special patch, but not the original author of the
> original source files. for the 1st patch which is the basic board
> support, in the long history of coding sirfprimaii, all the listed
> people have contributed codes. so i get the names of all of them
> shown. anyway, it is really too long....
> 

Not a problem. I basically wanted to make sure you know the rules,
and it seemed odd. It's probably ok to leave the list as it is.

	Arnd

  reply	other threads:[~2011-07-07 13:31 UTC|newest]

Thread overview: 18+ 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 ` 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   ` 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   ` Barry Song
2011-07-07  6:36 ` [PATCH v4 3/3] ARM: CSR: initializing L2 cache Barry Song
2011-07-07  6:36   ` Barry Song
2011-07-07 11:11 ` [PATCH v4 0/3] ARM: CSR: Adding CSR SiRFprimaII platform Arnd Bergmann
2011-07-07 11:11   ` Arnd Bergmann
2011-07-07 13:22   ` Barry Song
2011-07-07 13:22     ` Barry Song
2011-07-07 13:31     ` Arnd Bergmann [this message]
2011-07-07 13:31       ` Arnd Bergmann
2011-07-07 13:37       ` Barry Song
2011-07-07 13:37         ` Barry Song
2011-07-07 13:46         ` Arnd Bergmann
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=201107071531.18623.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.