From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: shmobile: Enable CPU FREQ support
Date: Thu, 29 May 2014 23:04:40 +0000 [thread overview]
Message-ID: <20140529230438.GA2353@verge.net.au> (raw)
In-Reply-To: <5386E64B.7060202@bp.renesas.com>
On Thu, May 29, 2014 at 01:09:17AM -0700, Kuninori Morimoto wrote:
>
> Hi Inami-san
>
> > Benoit Cousson (2):
> > ARM: dts: r8a7790-lager: Add DVFS parameters into cpu0 node for
> > r8a7790
> > ARM: shmobile: Make r8a77900 CPUFreq capable
>
> According to this, [1/7] [2/7] patches were
> created by Benoit ?
>
> Maybe you want to add extra "From" to these patches,
> and I guess you want to add your Signed-off-by also ?
> Otherwise, patch author will be you instead of Benoit
>
> like this ?
>
> -----------------------
> From: Gaku Inami <gaku.inami.xw@bp.renesas.com>
> Subject: [PATCH 2/7] ARM: shmobile: Make r8a77900 CPUFreq capable
>
> => From: Benoit Cousson <bcousson@baylibre.com>
>
> Mark r8a77900 platform as CPUFreq capable
> on multiplatform build only.
>
> => Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
> Signed-off-by: Benoit Cousson <bcousson@baylibre.com>
If Benoit Cousson wrote the patch and Inami-san is passing it on
(with or without modifications) then I think the Signed-off-by lines
should be the other way around.
Signed-off-by: Benoit Cousson <bcousson@baylibre.com>
=> Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
Also, I think it would be sane tough not essential to CC Benoit Cousson
when reposting the patches.
> ---
> ...
>
prev parent reply other threads:[~2014-05-29 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 7:48 [PATCH 0/7] ARM: shmobile: Enable CPU FREQ support Gaku Inami
2014-05-29 8:09 ` Kuninori Morimoto
2014-05-29 9:06 ` Gaku Inami
2014-05-29 23:04 ` Simon Horman [this message]
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=20140529230438.GA2353@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).