From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivien Didelot Date: Mon, 04 Jul 2016 11:18:46 -0400 Subject: [Buildroot] [PATCH] package/linux-headers: do not default to any version for custom headers In-Reply-To: <1467389013-24303-1-git-send-email-yann.morin.1998@free.fr> References: <1467389013-24303-1-git-send-email-yann.morin.1998@free.fr> Message-ID: <87bn2dbfe1.fsf@ketchup.mtl.sfl> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi, "Yann E. MORIN" 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 > Signed-off-by: "Yann E. MORIN" > Cc: Thomas Petazzoni 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 Thanks, Vivien