From: sashiko-bot@kernel.org
To: "Robin Murphy" <robin.murphy@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf: Process subdirectory Makefiles unconditionally
Date: Fri, 06 Nov 2026 18:54:01 +0000 [thread overview]
Message-ID: <sashiko-outbox-202115@kernel.org> (raw)
In-Reply-To: <4b2e518499270b2a6cab3e04a1123458d82d2759.1793990977.git.robin.murphy@arm.com>
> Our subdirectories here are purely for file-level organisation rather
> than any particular build structure, and everything in the Makefiles
> is already conditional on the appropriate config options. Plus they're
> not exactly big and complex, so for simplicity let's just drop the
> top-level conditions.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/4b2e518499270b2a6cab3e04a1123458d82d2759.1793990977.git.robin.murphy@arm.com?part=1
next prev parent reply other threads:[~2026-11-06 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:49 [PATCH] perf: Process subdirectory Makefiles unconditionally Robin Murphy
2026-11-06 18:54 ` sashiko-bot [this message]
2026-11-11 17:34 ` Robin Murphy
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=sashiko-outbox-202115@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=robin.murphy@arm.com \
--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