public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Chun-Tse Shao <ctshao@google.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, namhyung@kernel.org,
	agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, irogers@google.com
Subject: Re: [PATCH V4] perf test: Allow tolerance for leader sampling test
Date: Fri, 16 May 2025 07:09:35 +0200	[thread overview]
Message-ID: <c7b9977e-1088-40a5-8f34-26b1705338b8@linux.ibm.com> (raw)
In-Reply-To: <aCYOEwgBLWyK7g3q@x1>

On 5/15/25 17:53, Arnaldo Carvalho de Melo wrote:
> On Fri, May 02, 2025 at 04:11:55PM -0300, Arnaldo Carvalho de Melo wrote:
>> On Fri, May 02, 2025 at 11:21:07AM -0700, Chun-Tse Shao wrote:
>>> Hi Arnaldo,
>>>
>>> I submitted the patch v1 and Thomas helped me to modify and submit v2
>>> and v3 while I was OOO. In this case I am not sure which one should be
>>> the author, maybe just keep it as Thomas.
>>
>> >From the tags provided, I think it would be best to list you as the
>> author and Thomas a a Co-developer, like mentioned in:
>>
>> Documentation/process/submitting-patches.rst
>>
>> Co-developed-by: states that the patch was co-created by multiple developers;
>> it is used to give attribution to co-authors (in addition to the author
>> attributed by the From: tag) when several people work on a single patch.  Since
>> Co-developed-by: denotes authorship, every Co-developed-by: must be immediately
>> followed by a Signed-off-by: of the associated co-author.  Standard sign-off
>> procedure applies, i.e. the ordering of Signed-off-by: tags should reflect the
>> chronological history of the patch insofar as possible, regardless of whether
>> the author is attributed via From: or Co-developed-by:.  Notably, the last
>> Signed-off-by: must always be that of the developer submitting the patch.
>>
>> Note, the From: tag is optional when the From: author is also the person (and
>> email) listed in the From: line of the email header.
>>
>> Example of a patch submitted by the From: author::
>>
>>         <changelog>
>>
>>         Co-developed-by: First Co-Author <first@coauthor.example.org>
>>         Signed-off-by: First Co-Author <first@coauthor.example.org>
>>         Co-developed-by: Second Co-Author <second@coauthor.example.org>
>>         Signed-off-by: Second Co-Author <second@coauthor.example.org>
>>         Signed-off-by: From Author <from@author.example.org>
>>
>> Example of a patch submitted by a Co-developed-by: author::
>>
>>         From: From Author <from@author.example.org>
>>
>>         <changelog>
>>
>>         Co-developed-by: Random Co-Author <random@coauthor.example.org>
>>         Signed-off-by: Random Co-Author <random@coauthor.example.org>
>>         Signed-off-by: From Author <from@author.example.org>
>>         Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
>>         Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>
> 
> I was expecting some reaction from you or Thomas, but since I got a ping
> from Thomas for this not being processed, I'll process it according to
> my assessment of this thread.
> 
> Thanks,
> 
> - Arnaldo
> 
> 

Thanks Arnaldo,

sorry, but I was not aware that you were waiting for feedback from us.
I am fine with your assessment, I actually care more about the patch
being picked...

-- 
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH

Vorsitzender des Aufsichtsrats: Wolfgang Wendt

Geschäftsführung: David Faller

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

      reply	other threads:[~2025-05-16  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 14:06 [PATCH V4] perf test: Allow tolerance for leader sampling test Thomas Richter
2025-04-30 15:02 ` Ian Rogers
2025-04-30 17:16 ` Namhyung Kim
2025-05-02 16:35 ` Arnaldo Carvalho de Melo
2025-05-02 18:21   ` Chun-Tse Shao
2025-05-02 19:11     ` Arnaldo Carvalho de Melo
2025-05-15 15:53       ` Arnaldo Carvalho de Melo
2025-05-16  5:09         ` Thomas Richter [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=c7b9977e-1088-40a5-8f34-26b1705338b8@linux.ibm.com \
    --to=tmricht@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=ctshao@google.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.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