From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x
Date: Wed, 30 May 2018 22:41:34 +0200 [thread overview]
Message-ID: <20180530224134.0b87b6ad@windsurf.home> (raw)
In-Reply-To: <a478a326-805a-0b80-2df6-4779211fdfd9@mind.be>
Hello,
On Wed, 30 May 2018 22:35:50 +0200, Arnout Vandecappelle wrote:
> How about:
>
> 1. Applying http://patchwork.ozlabs.org/patch/898748/, so the default is still
> 2.28, but the user can choose another version.
> 2. Reverting these two patches (no longer needed).
> 3. Add a conditional warning to linux/Config.in that an unpatched kernel will
> fail to boot.
> 4. Eventually, add the patch that fixes the kernel to the stm32* defconfigs.
Sounds like a good plan to me.
Christophe, do you think you can provide the patches implementing this ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-30 20:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 12:09 [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x Christophe PRIOUZEAU
2018-05-29 12:09 ` [Buildroot] [PATCH 2/2] configs/stm32f469: " Christophe PRIOUZEAU
2018-05-29 12:49 ` Romain Naour
2018-05-29 12:39 ` [Buildroot] [PATCH 1/2] configs/stm32f429: " Romain Naour
2018-05-29 12:47 ` Christophe PRIOUZEAU
2018-05-29 12:48 ` Romain Naour
2018-05-29 15:51 ` Peter Korsgaard
2018-05-29 21:32 ` Thomas Petazzoni
2018-05-30 12:12 ` Laurent GONZALEZ
2018-05-30 16:24 ` Yann E. MORIN
2018-05-30 15:24 ` Christophe PRIOUZEAU
2018-05-30 15:42 ` Thomas Petazzoni
2018-05-30 20:35 ` Arnout Vandecappelle
2018-05-30 20:41 ` Thomas Petazzoni [this message]
2018-05-30 20:46 ` Romain Naour
2018-05-31 8:34 ` Christophe PRIOUZEAU
2018-05-31 9:13 ` Arnout Vandecappelle
2018-05-31 9:16 ` Thomas Petazzoni
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=20180530224134.0b87b6ad@windsurf.home \
--to=thomas.petazzoni@bootlin.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