All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michel Lind <michel@michel-slm.name>, Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-perf-users@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1 perf-tools] perf MANIFEST: Add arch/*/include/uapi/asm/bpf_perf_event.h to the perf tarball
Date: Fri, 10 Jan 2025 10:40:55 -0300	[thread overview]
Message-ID: <Z4EjZ8G_DcM3IWVU@x1> (raw)
In-Reply-To: <317c11923cf676437456e44a7f408d4ce589a9c0.camel@michel-slm.name>

On Thu, Jan 09, 2025 at 04:48:57PM -0600, Michel Lind wrote:
> Hi Arnaldo,
> 
> On Tue, 2024-11-26 at 17:43 -0300, Arnaldo Carvalho de Melo wrote:
> > Needed to build tools/lib/bpf/ on various arches other than x86_64,
> > notably arm64 when using the perf tarballs generated by:
> > 
> >   $ make help | grep perf-
> 
> I can confirm this works - I've applied this on top of the stable

Ok, so I'm taking this as a:

Tested-by: Michel Lind <michel@michel-slm.name>

Applied.

- Arnaldo

> tree's 6.12.9 tag, and generated a tarball that works for building perf
> in Hyperscale, e.g.

> https://cbs.centos.org/koji/buildinfo?buildID=57925
> 
> Can this be merged too? Thanks
> 
> (Also - presumably merged changes eventually shows up in the perf-
> tools-next branch)
> 
> 
> Best regards,
> 
> -- 
>  _o) Michel Lind
> _( ) identities:
> https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2



      reply	other threads:[~2025-01-10 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 20:43 [PATCH 1/1 perf-tools] perf MANIFEST: Add arch/*/include/uapi/asm/bpf_perf_event.h to the perf tarball Arnaldo Carvalho de Melo
2024-11-26 23:30 ` Michel Lind
2025-01-09 22:48 ` Michel Lind
2025-01-10 13:40   ` Arnaldo Carvalho de Melo [this message]

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=Z4EjZ8G_DcM3IWVU@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=michel@michel-slm.name \
    --cc=namhyung@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.