Re: [PATCH v1 00/22] Intel vendor events and TMA 5.01 metrics

Arnaldo Carvalho de Melo
2025-01-07T19:56:33Z

On Mon, Jan 06, 2025 at 09:16:56AM -0800, Ian Rogers wrote:
> On Wed, Dec 11, 2024 at 8:24 AM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > On 2024-12-10 2:03 p.m., Arnaldo Carvalho de Melo wrote:
> > >> I should have also said, this series requires:
> > >> https://lore.kernel.org/all/20241113165558.628856-1-irogers@google.com/

Checking that this is in...

> > > Applying that one now to perf-tools-next,

> > > Kan, can I have your Acked-by or Reviewed-by?

> > Sure.

> > Acked-by: Kan Liang <kan.liang@linux.intel.com>

> Happy new year and thanks Kan! Arnaldo, Namhyung please let me know if
> there is anything more necessary for this series. I don't believe it
> needs a rebase.

So, the Co-authored-by: tag was used and it is not documented in
Documentation/process/submitting-patches.rst, I think the right tag her
is "Co-developed-by:", and there are some rules about its usage, from
that doc:

---------------------------------- 8< ------------------------------

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.

---------------------------------- 8< ------------------------------

I'm taking the liberty to make these changes locally, please Ack these
changes by replying to this message, ok?

- Arnaldo