linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrew Pinski <apinski@quicinc.com>
Cc: Yonghong Song <yonghong.song@linux.dev>,
	"Andrew Pinski (QUIC)" <quic_apinski@quicinc.com>,
	Namhyung Kim <namhyung@kernel.org>, Sam James <sam@gentoo.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>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"Andrew.pinski@oss.qualcomm.com" <Andrew.pinski@oss.qualcomm.com>
Subject: Re: [PATCH] perf: use __builtin_preserve_field_info for GCC compatibility
Date: Thu, 2 Oct 2025 14:58:29 -0300	[thread overview]
Message-ID: <aN69RSQQ8agXOBDH@x1> (raw)
In-Reply-To: <CO1PR02MB84601693B2ECBB323297B4ECB8E7A@CO1PR02MB8460.namprd02.prod.outlook.com>

On Thu, Oct 02, 2025 at 05:35:09PM +0000, Andrew Pinski wrote:
> > From: Arnaldo Carvalho de Melo <acme@kernel.org>
> > So I'm taking the patch as-is, ok?

> > But first we need the Signed-off-by tag from Andrew Pinski as
> > he is listed in a Co-authored-by, that I replaced with Co-
> > developed-by as its the term used for this purpose in:

> > Yonghong, can I add an Acked-by: you since you participated in
> > this discussion agreeing with the original patch (If I'm not
> > mistaken)?

> Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
 
> Note my email address for doing Linux and GCC development is
> Andrew.pinski@oss.qualcomm.com . It was apinski_quic@quicinc.com but
> that changed last month.

This is what I have in the patch now:

Co-developed-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>

- Arnaldo

  reply	other threads:[~2025-10-02 17:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  0:03 [PATCH] perf: use __builtin_preserve_field_info for GCC compatibility Sam James
2025-08-06 23:33 ` Namhyung Kim
2025-08-06 23:57   ` Andrew Pinski
2025-08-07  0:27     ` Yonghong Song
2025-10-02 17:31       ` Arnaldo Carvalho de Melo
2025-10-02 17:35         ` Andrew Pinski
2025-10-02 17:58           ` Arnaldo Carvalho de Melo [this message]
2025-10-02 18:01             ` Sam James
2025-10-02 18:09               ` Andrew Pinski
2025-10-04 23:19         ` Yonghong Song
2025-10-06 18:22           ` Arnaldo Carvalho de Melo
2025-08-07  0:15   ` Yonghong Song

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=aN69RSQQ8agXOBDH@x1 \
    --to=acme@kernel.org \
    --cc=Andrew.pinski@oss.qualcomm.com \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=apinski@quicinc.com \
    --cc=bpf@vger.kernel.org \
    --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=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=quic_apinski@quicinc.com \
    --cc=sam@gentoo.org \
    --cc=yonghong.song@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).