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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAP-5=fUOyqyQuE3vQY6wd_XYm9nXgRmsXLJ3-ocMxD08+739VQ@mail.gmail.com>
Date: Tue, 7 Jan 2025 12:38:05 -0800
From: Ian Rogers <irogers@...gle.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>, Caleb Biggers <caleb.biggers@...el.com>
Cc: "Liang, Kan" <kan.liang@...ux.intel.com>, Namhyung Kim <namhyung@...nel.org>, 
	Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, 
	Mark Rutland <mark.rutland@....com>, 
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>, 
	Adrian Hunter <adrian.hunter@...el.com>, Andreas Färber <afaerber@...e.de>, 
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>, Weilin Wang <weilin.wang@...el.com>, 
	linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org, 
	Perry Taylor <perry.taylor@...el.com>, Samantha Alt <samantha.alt@...el.com>, 
	Edward Baker <edward.baker@...el.com>, Michael Petlan <mpetlan@...hat.com>
Subject: Re: [PATCH v1 00/22] Intel vendor events and TMA 5.01 metrics

On Tue, Jan 7, 2025 at 11:56 AM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> 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@...ux.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@...ux.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?

Thanks Arnaldo, this makes sense to me. Caleb is adding Signed-off-by
tags from you okay?

Ian