All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: Allow to specify a list of patches
Date: Tue, 15 Jul 2014 20:53:41 +0200	[thread overview]
Message-ID: <20140715205341.77237719@free-electrons.com> (raw)
In-Reply-To: <1405448794-10517-1-git-send-email-ezequiel@vanguardiasur.com.ar>

Dear Ezequiel Garcia,

On Tue, 15 Jul 2014 15:26:34 -0300, Ezequiel Garcia wrote:
> It's often desirable to specify a list of patches, in addition to the current
> support to pass a directory full of uboot-*.patch files. This matches the
> option currently available for specifying Linux patches, except this commit
> doesn't add the URL option. Relying on URLs is fragile and makes a build hard
> to reproduce.
> 
> U-Boot is as special as Linux, in the sense that it needs to be customized more
> often than not, so having a flexible mechanism is useful.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
>  Config.in.legacy     | 14 ++++++++++++++
>  boot/uboot/Config.in | 11 ++++++-----
>  boot/uboot/uboot.mk  | 12 ++++++++----
>  3 files changed, 28 insertions(+), 9 deletions(-)

We now have BR2_GLOBAL_PATCH_DIR, so I believe that what we would
recommend to use from now on. We have even been talking about removing
the Linux-specific and U-Boot specific patching config options.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-07-15 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 18:26 [Buildroot] [PATCH] u-boot: Allow to specify a list of patches Ezequiel Garcia
2014-07-15 18:53 ` Thomas Petazzoni [this message]
2014-07-15 19:49   ` Ezequiel García
2014-07-15 20:13     ` Yann E. MORIN
2014-07-15 20:35       ` Thomas Petazzoni
2014-07-16  5:21         ` Thomas De Schampheleire
2014-07-16 22:23       ` Arnout Vandecappelle
2014-07-17  4:52         ` Thomas De Schampheleire
2014-07-17  7:48           ` Arnout Vandecappelle
2014-07-17 17:23             ` Yann E. MORIN
2014-07-17 23:20               ` Arnout Vandecappelle
2014-07-21 19:55                 ` Ezequiel García

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=20140715205341.77237719@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.