From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] support PMIC mc13892
Date: Tue, 7 Dec 2010 11:54:29 +0000 [thread overview]
Message-ID: <20101207115429.GB4698@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTikr5egA+mktGwCUfT8eHvnTBt6VmYxx3eb-eL4W@mail.gmail.com>
On Tue, Dec 07, 2010 at 05:55:00PM +0800, Yong Shen wrote:
> On Tue, Dec 7, 2010 at 5:39 PM, Arnaud Patard <arnaud.patard@rtp-net.org> wrote:
> > I'm not sure if it should be a signed-off-by: or acked-by: or reviewed-by:
> > tag since I wrote the code you've used a basis. I'm putting my s-o-b but
> > if I'm wrong, I do hope someone will correct it.
> > Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> It is nice that you mention this issue. I was also wondering for a
> while about what should I do about this, I was not sure, so I put
> Arnaud in the head comments. Is there any conventions for this? I am
> OK with:
> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> Signed-off-by: Yong Shen <yong.shen@linaro.org>
A signoff has a very specific meaning which would in this situation mean
that Arnaud wrote part of the patch - see SubmittingPatches. Otherwise
a Tested-by and/or Reviewed-by seem appropriate (with the obvious
meanings).
> It seems that I should send out a new patch for this, or can I just
> ask maintainer who is responsible for merging this patch to change the
> s-o-b?
Maintainers will usually take care of this, but if you need to resend
please do include tags that still apply.
next prev parent reply other threads:[~2010-12-07 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 8:01 [PATCHv2] support PMIC mc13892 b00984 at freescale.com
2010-12-07 9:39 ` Arnaud Patard (Rtp)
2010-12-07 9:43 ` Uwe Kleine-König
2010-12-07 9:55 ` Yong Shen
2010-12-07 11:54 ` Mark Brown [this message]
2010-12-07 14:48 ` Mark Brown
2010-12-08 3:19 ` Yong Shen
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=20101207115429.GB4698@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox