linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hupu <hupu.gm@gmail.com>
To: namhyung@kernel.org, leo.yan@arm.com
Cc: acme@kernel.org, adrian.hunter@intel.com,
	 alexander.shishkin@linux.intel.com, irogers@google.com,
	jolsa@kernel.org,  justinstitt@google.com,
	linux-kernel@vger.kernel.org,  linux-perf-users@vger.kernel.org,
	mark.rutland@arm.com, mingo@redhat.com,  morbo@google.com,
	nathan@kernel.org, nick.desaulniers+lkml@gmail.com,
	 peterz@infradead.org
Subject: Re: [RFC] perf build: Use self-contained headers from kernel source when compiling
Date: Mon, 24 Nov 2025 15:51:25 +0800	[thread overview]
Message-ID: <CADHxFxRX2=Mt+BGhpCU9WfAMi9rfUO2x7qLy8tEu1aiSVo39bQ@mail.gmail.com> (raw)
In-Reply-To: <20251124072310.3592-1-hupu.gm@gmail.com>

Hi All Maintainers:

The background of this PATCH is explained in the email linked below.
To avoid potential disagreement from submitting multiple PATCHes in a
single email, this email focuses solely on discussing whether to use
self-contained headers from the kernel source when building perf.

https://lore.kernel.org/all/20251013080609.2070555-1-hupu.gm@gmail.com/

Thanks,
hupu

  reply	other threads:[~2025-11-24  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  7:23 [RFC] perf build: Use self-contained headers from kernel source when compiling hupu
2025-11-24  7:51 ` hupu [this message]
2025-11-25 13:12   ` hupu
2025-11-25 16:39 ` Leo Yan
2025-12-05  6:29   ` hupu
2025-12-08  9:04     ` hupu
2025-12-10 10:24       ` hupu

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='CADHxFxRX2=Mt+BGhpCU9WfAMi9rfUO2x7qLy8tEu1aiSVo39bQ@mail.gmail.com' \
    --to=hupu.gm@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=peterz@infradead.org \
    /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).