From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Xuanhao Shi <X15000177@gmail.com>, Anand Gadiyar <gadiyar@ti.com>,
michael@amarulasolutions.com, linux-amarula@amarulasolutions.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] boot/ti-k3-r5-loader: add support for patch files and URLs
Date: Wed, 7 Feb 2024 19:56:12 +0100 [thread overview]
Message-ID: <20240207195612.7ea08e54@windsurf> (raw)
In-Reply-To: <20231129172852.1684628-1-dario.binacchi@amarulasolutions.com>
On Wed, 29 Nov 2023 18:28:52 +0100
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> The patch adds support for URLs using similar code as found
> in linux/linux.mk and uboot/uboot.mk.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> boot/ti-k3-r5-loader/Config.in | 11 +++++++++++
> boot/ti-k3-r5-loader/ti-k3-r5-loader.mk | 18 ++++++++++++++++++
> 2 files changed, 29 insertions(+)
Thanks a lot for your proposal, but we no longer add package-specific
options to apply patches, as BR2_GLOBAL_PATCH_DIR allows to patch all
packages. We do have options that exist for linux and u-boot indeed,
because they predate BR2_GLOBAL_PATCH_DIR, and we need to keep them for
backwards compatibility. But we do not introduce such options for new
packages. For the example, the arm-trusted-firmware has no custom patch
option, because BR2_GLOBAL_PATCH_DIR can/should be used instead.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-07 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:28 [Buildroot] [PATCH 1/1] boot/ti-k3-r5-loader: add support for patch files and URLs Dario Binacchi
2024-02-07 18:56 ` Thomas Petazzoni via buildroot [this message]
2024-02-07 20:11 ` Dario Binacchi
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=20240207195612.7ea08e54@windsurf \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=gadiyar@ti.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=michael@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox