From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Weilin Wang" <weilin.wang@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Perry Taylor" <perry.taylor@intel.com>,
"Samantha Alt" <samantha.alt@intel.com>,
"Caleb Biggers" <caleb.biggers@intel.com>,
"Edward Baker" <edward.baker@intel.com>,
"Michael Petlan" <mpetlan@redhat.com>
Subject: Re: [PATCH v1 00/22] Intel vendor events and TMA 5.01 metrics
Date: Tue, 7 Jan 2025 16:56:29 -0300 [thread overview]
Message-ID: <Z32G7cNV3hZ2bZHT@x1> (raw)
In-Reply-To: <CAP-5=fUTXzZfRqre0Vai_5pxue_mAvb9oh-Ea9Sgr7U=Lrm_Nw@mail.gmail.com>
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
next prev parent reply other threads:[~2025-01-07 19:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 22:27 [PATCH v1 00/22] Intel vendor events and TMA 5.01 metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 01/22] perf vendor events: Update Alderlake events/metrics Ian Rogers
2025-01-08 14:51 ` Arnaldo Carvalho de Melo
2025-01-08 16:18 ` Ian Rogers
2024-12-09 22:27 ` [PATCH v1 02/22] perf vendor events: Update AlderlakeN events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 03/22] perf vendor events: Add Arrowlake events/metrics Ian Rogers
2024-12-12 0:32 ` kernel test robot
2024-12-14 22:57 ` kernel test robot
2024-12-09 22:27 ` [PATCH v1 04/22] perf vendor events: Update Broadwell events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 05/22] perf vendor events: Update BroadwellDE events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 06/22] perf vendor events: Update BroadwellX events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 07/22] perf vendor events: Update CascadelakeX events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 08/22] perf vendor events: Update EmeraldRapids events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 09/22] perf vendor events: Update GrandRidge events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 10/22] perf vendor events: Update/add Graniterapids events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 11/22] perf vendor events: Update Haswell events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 12/22] perf vendor events: Update HaswellX events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 13/22] perf vendor events: Update Icelake events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 14/22] perf vendor events: Update IcelakeX events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 15/22] perf vendor events: Update/add Lunarlake events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 16/22] perf vendor events: Update Meteorlake events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 17/22] perf vendor events: Update Rocketlake events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 18/22] perf vendor events: Update Sapphirerapids events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 19/22] perf vendor events: Update Sierraforest events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 20/22] perf vendor events: Update Skylake metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 21/22] perf vendor events: Update SkylakeX events/metrics Ian Rogers
2024-12-09 22:27 ` [PATCH v1 22/22] perf vendor events: Update Tigerlake events/metrics Ian Rogers
2024-12-10 0:44 ` [PATCH v1 00/22] Intel vendor events and TMA 5.01 metrics Ian Rogers
2024-12-10 19:03 ` Arnaldo Carvalho de Melo
2024-12-11 16:24 ` Liang, Kan
2025-01-06 17:16 ` Ian Rogers
2025-01-07 19:56 ` Arnaldo Carvalho de Melo [this message]
2025-01-07 20:38 ` Ian Rogers
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=Z32G7cNV3hZ2bZHT@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afaerber@suse.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@intel.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