From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config
Date: Sun, 30 Aug 2015 22:41:43 +0200 [thread overview]
Message-ID: <87mvx8tsoo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55D8FE3F.8080206@mind.be> (Arnout Vandecappelle's message of "Sun, 23 Aug 2015 00:57:03 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> I haven't had the time to look into this in detail. It would be great
>> if Yann, or J?rg could have a look. I remain unhappy with solving such
>> a problem by using a patch against U-Boot 2015.07, because it means
>> anyone specifying a slightly different U-Boot version (but based on
>> 2015.07) will still have the problem.
> I assume the problem will be fixed soon upstream, so the chance that some chip
> vendor releases a U-Boot based on 2015.07 is not that high. And if someone is
> making their own modified git copy of 2015.07, they'll notice _very_ quickly
> that it fails and with any luck they'll notice the patch in buildroot.
> Not fixing the problem at all in 2015.08 is obviously worse.
Agreed.
> We could do a sed independent of the U-Boot version, but that runs the risk of
> breaking some other random non-2015.07 version completely.
Yeah, that sounds a bit scary.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-08-30 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 14:04 [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config Alexey Brodkin
2015-07-31 14:18 ` Thomas Petazzoni
2015-07-31 15:14 ` Alexey Brodkin
2015-08-03 11:16 ` Alexey Brodkin
2015-08-11 12:20 ` Alexey Brodkin
2015-08-12 8:23 ` Thomas Petazzoni
2015-08-16 21:43 ` Jörg Krause
2015-08-17 6:37 ` Alexey Brodkin
2015-08-17 9:31 ` Yann E. MORIN
2015-08-17 9:58 ` Alexey Brodkin
2015-08-22 22:57 ` Arnout Vandecappelle
2015-08-28 9:36 ` Alexey Brodkin
2015-08-30 20:41 ` Peter Korsgaard [this message]
2015-08-30 20:51 ` Peter Korsgaard
2015-08-31 16:43 ` Alexey Brodkin
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=87mvx8tsoo.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox