Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: "Yann E . MORIN" <yann.morin.1998@free.fr>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"Yann E . MORIN" <yann.morin@orange.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Niklas Cassel <cassel@kernel.org>
Subject: Re: [Buildroot] [PATCH 1/2] package/linux-tools: perf: Fix _BIN_ARCH_EXCLUDE
Date: Mon, 24 Feb 2025 08:14:15 +0000	[thread overview]
Message-ID: <Z7wqVXa7q_fACzly@ryzen> (raw)
In-Reply-To: <20250218104807.2329338-1-Niklas.Cassel@wdc.com>

Hello Yann,

Any chance to get a review from you on this series?

Kind regards,
Niklas


On Tue, Feb 18, 2025 at 11:48:06AM +0100, Niklas Cassel wrote:
> From: Niklas Cassel <cassel@kernel.org>
> 
> support/scripts/check-bin-arch has an option -i to exclude a path
> (or many paths by using -i multiple times).
> 
> This was implemented in commit 01d90f0d093f ("spport/check-bin-arch:
> accept arbitrary per-package ignore paths").
> 
> Looking at this feature (which hasn't changed since being added),
> we can see that check-bin-arch automatically adds a trailing slash
> to all entries specified using -i.
> 
> Thus, specifying a path to a file, e.g.
> "/usr/libexec/perf-core/tests/pe-file.exe" will cause check-bin-arch
> to add "/usr/libexec/perf-core/tests/pe-file.exe/" to the IGNORES array.
> 
> When running the main loop, the file
> "/usr/libexec/perf-core/tests/pe-file.exe" will thus not be ignored,
> since it will not trigger a match the pattern that was added to the
> IGNORES array ("/usr/libexec/perf-core/tests/pe-file.exe/").
> 
> This means that the -i option in check-bin-arch only supports directories
> and not files.
> 
> Fix the LINUX_TOOLS_BIN_ARCH_EXCLUDE in
> package/linux-tools/linux-tool-perf.mk.in to specify a directory, as the
> existing LINUX_TOOLS_BIN_ARCH_EXCLUDE can never have actually worked.
> 
> Fixes: a7ad7816262d ("package/linux-tools: Exclude checking PE binaries from perf test")
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
>  package/linux-tools/linux-tool-perf.mk.in | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/package/linux-tools/linux-tool-perf.mk.in b/package/linux-tools/linux-tool-perf.mk.in
> index df3030439e..d67318571a 100644
> --- a/package/linux-tools/linux-tool-perf.mk.in
> +++ b/package/linux-tools/linux-tool-perf.mk.in
> @@ -180,8 +180,7 @@ define PERF_INSTALL_REMOVE_SCRIPTS
>  endef
>  
>  LINUX_TOOLS_BIN_ARCH_EXCLUDE += \
> -	/usr/libexec/perf-core/tests/pe-file.exe \
> -	/usr/libexec/perf-core/tests/pe-file.exe.debug
> +	/usr/libexec/perf-core/tests/
>  endif
>  
>  define PERF_INSTALL_TARGET_CMDS
> -- 
> 2.48.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-02-24  8:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 10:48 [Buildroot] [PATCH 1/2] package/linux-tools: perf: Fix _BIN_ARCH_EXCLUDE Niklas Cassel via buildroot
2025-02-18 10:48 ` [Buildroot] [PATCH 2/2] package/linux-tools: selftests: Add path containing BPF binary to _BIN_ARCH_EXCLUDE Niklas Cassel via buildroot
2025-03-04 22:36   ` Florian Fainelli
2025-03-20  9:01   ` Niklas Cassel via buildroot
2025-04-16 20:56   ` Arnout Vandecappelle via buildroot
2025-02-24  8:14 ` Niklas Cassel via buildroot [this message]
2025-03-04 22:36 ` [Buildroot] [PATCH 1/2] package/linux-tools: perf: Fix _BIN_ARCH_EXCLUDE Florian Fainelli
2025-03-12  8:40 ` Niklas Cassel via buildroot
2025-03-20 21:47 ` Julien Olivain
2025-04-16 20:55 ` Arnout Vandecappelle via buildroot

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=Z7wqVXa7q_fACzly@ryzen \
    --to=buildroot@buildroot.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=yann.morin.1998@free.fr \
    --cc=yann.morin@orange.com \
    /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