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: Thu, 31 May 2018 11:16:08 +0200 [thread overview]
Message-ID: <20180531111608.2ebbd4a0@windsurf> (raw)
In-Reply-To: <cd9bc020-7228-60f5-187e-70c9c4274c37@st.com>
Hello Christophe,
It would be nice if you could avoid top-posting. It's the same best
practice on the Linux kernel mailing lists.
On Thu, 31 May 2018 08:34:08 +0000, Christophe PRIOUZEAU wrote:
> I'm ok to provide the patches.
Great!
> For the warning, can you point to me an example or a documentation
> to write a "conditional warning" on Kconfig.
comment "Linux kernel < v4.12 will not boot with the selected binutils version"
depends on BR2_ARMV7M
depends on !BR2_BINUTILS_2_28_X
or something like that (I haven't checked the exact option names, nor
the kernel version, nor anything else, it's just an example).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-31 9:16 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
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 [this message]
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=20180531111608.2ebbd4a0@windsurf \
--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 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.