From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] toolchain: Add necessary options to support 5.0 kernel headers
Date: Tue, 19 Mar 2019 22:23:19 +0100 [thread overview]
Message-ID: <20190319222319.60fd2f2d@windsurf> (raw)
In-Reply-To: <20190319000638.6259-3-joel@jms.id.au>
Hello Joel,
On Tue, 19 Mar 2019 10:36:37 +1030
Joel Stanley <joel@jms.id.au> wrote:
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> toolchain/Config.in | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index bcbc3cf98432..f0bde8fbc870 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -397,10 +397,15 @@ config BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_20
> bool
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_19
>
> +config BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
> + bool
> + select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
This patch should come first in your series, because your PATCH 1/3
does this:
+ select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
i.e PATCH 1/3 depends on PATCH 2/3.
Another thing that is missing in your series is another patch to add
the 5.0 kernel header selection to
toolchain/toolchain-external/toolchain-external-custom/Config.in.options.
Could you fix these two issues and resend ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-19 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 0:06 [Buildroot] [PATCH 0/3] Linux kernel 5.0 support Joel Stanley
2019-03-19 0:06 ` [Buildroot] [PATCH 1/3] package/linux-headers: add support for Linux 5.0 kernel headers Joel Stanley
2019-03-19 0:06 ` [Buildroot] [PATCH 2/3] toolchain: Add necessary options to support " Joel Stanley
2019-03-19 21:23 ` Thomas Petazzoni [this message]
2019-03-19 0:06 ` [Buildroot] [PATCH 3/3] linux: add support for Linux 5.0 Joel Stanley
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=20190319222319.60fd2f2d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox