Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: add config option to disable general patches
Date: Thu, 8 Jan 2009 19:17:16 +0100	[thread overview]
Message-ID: <200901081917.16406.markus.heidelberg@web.de> (raw)
In-Reply-To: <878wplsw9q.fsf@macbook.be.48ers.dk>

Peter Korsgaard, 08.01.2009:
> >>>>> "Markus" == Markus Heidelberg <markus.heidelberg@web.de> writes:
> 
>  Markus> The patches in target/u-boot/$(U_BOOT_VERSION)/ can conflict with custom
>  Markus> board specific patches, so this option is necessary.
> 
> I would rather get rid of any patches that are not strictly needed. We
> should only have patches for criticial bugfixes or build issues.

It's not that only big/many/feature patches can lead to conflicts, it's
rather possible that patches containing fixes conflict with custom
patches, at least with my current workflow. I don't base U-Boot
development on the state in Buildroot, but on U-Boot's git tree and then
create a patch against the release and put it into Buildroot.

It's the same as with the Linux kernel: you wouldn't like patches lying
around in Buildroot, which you can't disable and always get applied.

> The number of configuration options we have in target/u-boot nowadays
> is getty silly.

That's right, but this option is not one to be passed to U-Boot like all
this board specific stuff currently in Config.in.

Markus

  reply	other threads:[~2009-01-08 18:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  7:54 [Buildroot] [PATCH] u-boot: add config option to disable patching Markus Heidelberg
2008-11-14 13:37 ` Peter Korsgaard
2008-11-15 10:56   ` Markus Heidelberg
2009-01-08 14:10     ` [Buildroot] [PATCH] u-boot: add config option to disable general patches Markus Heidelberg
2009-01-08 14:33       ` Peter Korsgaard
2009-01-08 18:17         ` Markus Heidelberg [this message]
2009-01-09 10:54           ` Peter Korsgaard
2009-01-09 15:08             ` Markus Heidelberg
2009-01-09 15:15               ` Peter Korsgaard
2009-01-09 16:07                 ` Markus Heidelberg
2009-01-08 21:56         ` Ulf Samuelsson
2009-01-09 11:07           ` Thomas Lundquist
2009-01-09 11:26           ` Peter Korsgaard

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=200901081917.16406.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox