From: Kevin Hilman <khilman@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
Cc: J Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v1 1/3] PM / AVS: SmartReflex: disable errgen before vpbound disable
Date: Wed, 29 May 2013 07:01:57 -0700 [thread overview]
Message-ID: <87fvx5anqi.fsf@linaro.org> (raw)
In-Reply-To: <51A5D148.8050203@ti.com> (Andrii Tseglytskyi's message of "Wed, 29 May 2013 12:58:32 +0300")
Andrii Tseglytskyi <andrii.tseglytskyi@ti.com> writes:
[...]
>>> Signed-off-by: Vincent Bour <v-bour@ti.com>
>>> Signed-off-by: Leonardo Affortunati <l-affortunati@ti.com>
>>> Signed-off-by: Nishanth Menon <nm@ti.com>
>>> Signed-off-by: Andrii.Tseglytskyi <andrii.tseglytskyi@ti.com>
>> From Documentation/SubbmittingPatches:
>>
>> "If a person was not directly involved in the preparation or handling
>> of a patch but wishes to signify and record their approval of it then
>> they can arrange to have an Acked-by: line added to the patch's
>> changelog."
>>
>> Are all of the tags above co-authors or on the delivery path? I suspect
>> an Acked-by or Reviewed-by is more appropriate here.
[...]
> This patch was developed by Nishanth, he is the author of the code.
> Patch is the result of 2-week debug session. Vincent, Leonardo and
> Nishanth were involved to that debug session.
> My contribution to this patch - is sending it to upstream, no more
> than this.
> Could you please suggest - who should remain in Signed-offs ?
Nishanth as the author, and you since you're on the delivery path.
If Vincent & Leonardo should be considered as co-authors, then their
signoffs are fine, otherwise they should be reviewed-by or acked-by.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
Cc: J Keerthy <j-keerthy@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] PM / AVS: SmartReflex: disable errgen before vpbound disable
Date: Wed, 29 May 2013 07:01:57 -0700 [thread overview]
Message-ID: <87fvx5anqi.fsf@linaro.org> (raw)
In-Reply-To: <51A5D148.8050203@ti.com> (Andrii Tseglytskyi's message of "Wed, 29 May 2013 12:58:32 +0300")
Andrii Tseglytskyi <andrii.tseglytskyi@ti.com> writes:
[...]
>>> Signed-off-by: Vincent Bour <v-bour@ti.com>
>>> Signed-off-by: Leonardo Affortunati <l-affortunati@ti.com>
>>> Signed-off-by: Nishanth Menon <nm@ti.com>
>>> Signed-off-by: Andrii.Tseglytskyi <andrii.tseglytskyi@ti.com>
>> From Documentation/SubbmittingPatches:
>>
>> "If a person was not directly involved in the preparation or handling
>> of a patch but wishes to signify and record their approval of it then
>> they can arrange to have an Acked-by: line added to the patch's
>> changelog."
>>
>> Are all of the tags above co-authors or on the delivery path? I suspect
>> an Acked-by or Reviewed-by is more appropriate here.
[...]
> This patch was developed by Nishanth, he is the author of the code.
> Patch is the result of 2-week debug session. Vincent, Leonardo and
> Nishanth were involved to that debug session.
> My contribution to this patch - is sending it to upstream, no more
> than this.
> Could you please suggest - who should remain in Signed-offs ?
Nishanth as the author, and you since you're on the delivery path.
If Vincent & Leonardo should be considered as co-authors, then their
signoffs are fine, otherwise they should be reviewed-by or acked-by.
Kevin
next prev parent reply other threads:[~2013-05-29 14:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 11:07 [PATCH v1 0/3] PM / AVS: SmartReflex: driver misc fixes Andrii Tseglytskyi
2013-05-27 11:07 ` Andrii Tseglytskyi
2013-05-27 11:07 ` [PATCH v1 1/3] PM / AVS: SmartReflex: disable errgen before vpbound disable Andrii Tseglytskyi
2013-05-27 11:07 ` Andrii Tseglytskyi
2013-05-28 18:45 ` Kevin Hilman
2013-05-28 18:45 ` Kevin Hilman
2013-05-29 9:58 ` Andrii Tseglytskyi
2013-05-29 9:58 ` Andrii Tseglytskyi
2013-05-29 14:01 ` Kevin Hilman [this message]
2013-05-29 14:01 ` Kevin Hilman
2013-05-29 14:24 ` Andrii Tseglytskyi
2013-05-29 14:24 ` Andrii Tseglytskyi
2013-05-29 16:32 ` Kevin Hilman
2013-05-29 16:32 ` Kevin Hilman
2013-05-27 11:07 ` [PATCH v1 2/3] PM / AVS: SmartReflex: disable runtime PM on driver remove Andrii Tseglytskyi
2013-05-27 11:07 ` Andrii Tseglytskyi
2013-05-27 11:07 ` [PATCH v1 3/3] PM / AVS: SmartReflex: fix driver name Andrii Tseglytskyi
2013-05-27 11:07 ` Andrii Tseglytskyi
2013-05-28 21:03 ` [PATCH v1 0/3] PM / AVS: SmartReflex: driver misc fixes Kevin Hilman
2013-05-28 21:03 ` Kevin Hilman
2013-05-29 10:00 ` Andrii Tseglytskyi
2013-05-29 10:00 ` Andrii Tseglytskyi
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=87fvx5anqi.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=andrii.tseglytskyi@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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 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.