From: sashiko-bot@kernel.org
To: "Dapeng Mi" <dapeng1.mi@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [Patch v2 2/2] perf util: Explicitly include required headers
Date: Tue, 22 Sep 2026 01:16:31 +0000 [thread overview]
Message-ID: <20260922011631.9832A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922010531.1933320-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/20260922010531.1933320-1-dapeng1.mi@linux.intel.com?part=2
next prev parent reply other threads:[~2026-09-22 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 1:05 [Patch v2 1/2] perf aslr: Add missing SIMD handling in aslr_tool__process_sample() Dapeng Mi
2026-09-22 1:05 ` [Patch v2 2/2] perf util: Explicitly include required headers Dapeng Mi
2026-09-22 1:16 ` sashiko-bot [this message]
2026-09-22 1:20 ` [Patch v2 1/2] perf aslr: Add missing SIMD handling in aslr_tool__process_sample() sashiko-bot
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=20260922011631.9832A1F000FF@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 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.