All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Markus Mayer via buildroot <buildroot@buildroot.org>
Cc: Markus Mayer <mmayer@broadcom.com>
Subject: Re: [Buildroot] [PATCH] support/scripts/apply-patches.sh: introduce envvar BR_PATCH_ARGS
Date: Tue, 28 Jan 2025 22:09:20 +0100	[thread overview]
Message-ID: <20250128220920.535ecc14@windsurf> (raw)
In-Reply-To: <20250127215356.3175741-1-mmayer@broadcom.com>

Hello Markus,

On Mon, 27 Jan 2025 13:53:54 -0800
Markus Mayer via buildroot <buildroot@buildroot.org> wrote:

> Introduce the environment variable BR_PATCH_ARGS as a means for the
> caller to pass additional arguments to the patch(1) command. These
> arguments can be new arguments not originally used -- or they can
> override one of the default arguments.
> 
> In addition, provide a mechanism to add patch parameters on a
> per-package basis using the <PACKAGENAME>_PATCH_ARGS makefile variable,
> for example "PROCPS_NG_PATCH_ARGS". This allows individual packages to
> specify extra arguments or override defaults while not affecting any
> other part of the build environment.

Thanks for the proposed patch. Do you have some details on the actual
(not theoretical) use-case(s) ?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-01-28 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 21:53 [Buildroot] [PATCH] support/scripts/apply-patches.sh: introduce envvar BR_PATCH_ARGS Markus Mayer via buildroot
2025-01-28 21:09 ` Thomas Petazzoni via buildroot [this message]
2025-02-05 16:58   ` Markus Mayer via buildroot
2025-02-05 19:28     ` Arnout Vandecappelle via buildroot
2025-02-05 22:08       ` Markus Mayer 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=20250128220920.535ecc14@windsurf \
    --to=buildroot@buildroot.org \
    --cc=mmayer@broadcom.com \
    --cc=thomas.petazzoni@bootlin.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 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.