From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-headers: do not default to any version for custom headers
Date: Mon, 04 Jul 2016 11:18:46 -0400 [thread overview]
Message-ID: <87bn2dbfe1.fsf@ketchup.mtl.sfl> (raw)
In-Reply-To: <1467389013-24303-1-git-send-email-yann.morin.1998@free.fr>
Hi,
"Yann E. MORIN" <yann.morin.1998@free.fr> writes:
> Currently, for a custom headers version, or for the same headers as the
> kernel, wedefault to a "very old" version (i.e. 2.6.x in practice).
>
> However, as Vivien explained, when using the same headers as the kernel,
> and the kernel is set to use the default version (aka latest version
> known to Buildroot) of the kernel, one would expect the headers are
> automatically tracking the latest version. Off course, that expectation
> is broken because of the above.
>
> However, whatever version we default to, it will probably not be
> correct, whether we default to the latest version or to the "very old"
> version.
>
> So, simply drop the specific default version, so the default is now the
> latest version.
>
> Note: that has the potential to break existing defconfig files that
> relied on the "very old" version to be the default. Well, whatever,
> they'll get a build failre quite early, and it is easy to fix.
>
> Reported-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Sorry I didn't get time to get back on this... Thanks Yann for digging
that up! I like this new approach.
For what it's worth:
Reviewed-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Thanks,
Vivien
prev parent reply other threads:[~2016-07-04 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 16:03 [Buildroot] [PATCH] package/linux-headers: do not default to any version for custom headers Yann E. MORIN
2016-07-01 20:42 ` Thomas Petazzoni
2016-07-04 15:18 ` Vivien Didelot [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=87bn2dbfe1.fsf@ketchup.mtl.sfl \
--to=vivien.didelot@savoirfairelinux.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