Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dapeng Mi" <dapeng1.mi@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/2] perf util: Explicitly include required headers
Date: Tue, 15 Sep 2026 09:23:54 +0000	[thread overview]
Message-ID: <20260915092354.A1A411F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915091112.333308-2-dapeng1.mi@linux.intel.com>

> Sashiko complains "the perf tool can be compiled with musl libc, which
> enforces strict POSIX namespace separation and does not implicitly
> include headers. Relying on implicit header inclusion can cause build
> failures under musl."
> 
> Include the required headers explicitly to avoid such failures.
> 
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260915091112.333308-1-dapeng1.mi@linux.intel.com?part=2


  reply	other threads:[~2026-09-15  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  9:11 [PATCH 1/2] perf alsr: Add missing SIMD handling in aslr_tool__process_sample() Dapeng Mi
2026-09-15  9:11 ` [PATCH 2/2] perf util: Explicitly include required headers Dapeng Mi
2026-09-15  9:23   ` sashiko-bot [this message]
2026-09-21 16:23   ` Ian Rogers
2026-09-15  9:24 ` [PATCH 1/2] perf alsr: Add missing SIMD handling in aslr_tool__process_sample() sashiko-bot
2026-09-21  6:42 ` Mi, Dapeng
2026-09-21 16:21   ` Ian Rogers
2026-09-21 16:22     ` Ian Rogers
2026-09-22  0:31       ` Mi, Dapeng
2026-09-22 12:50       ` Arnaldo Carvalho de Melo
2026-09-22  0:30     ` Mi, Dapeng

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=20260915092354.A1A411F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.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