From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] defconfigs: use the new headers-version-same-as-kernel-version option
Date: Wed, 20 Jan 2016 22:29:44 +0100 [thread overview]
Message-ID: <87powwrlbr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160120213824.686c94fb@free-electrons.com> (Thomas Petazzoni's message of "Wed, 20 Jan 2016 21:38:24 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Dear Yann E. MORIN,
> On Wed, 20 Jan 2016 19:34:29 +0100, Yann E. MORIN wrote:
>> Now that we can say that the linux headers version should match that of
>> the kernel to be built, we inverse the logic in our defconfigs, as it is
>> more sensible that way.
>>
>> And also because we'll get rid of the former, converse kernel-same-as-headers
>> option.
>>
>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> In this commit, you are changing the defconfigs that use
> BR2_LINUX_KERNEL_SAME_AS_HEADERS. But I am wondering if we shouldn't
> simply change *all* defconfigs to use this new feature. Essentially all
> defconfigs have to worry about selecting a kernel headers version that
> matches the kernel version they use. We could switch them all to use
> your new mechanism, no?
> Of course, this can be done as a separate effort, this is not a call
> to change this particular patch, but rather a discussion on what to do
> next.
Agreed. As long as we use the internal toolchain for our defconfigs and
build a kernel (and we so far always do), it makes sense to use this
option.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-01-20 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 18:34 [Buildroot] [PATCH 0/3] toolchain: add possibility to use kernel version for linux-headers (branch yem/kenrel-headers) Yann E. MORIN
2016-01-20 18:34 ` [Buildroot] [PATCH 1/3] package/linux-headers: add option to use same sources as the kernel Yann E. MORIN
2016-01-20 20:36 ` Thomas Petazzoni
2016-01-20 21:03 ` Yann E. MORIN
2016-02-02 9:05 ` Peter Korsgaard
2016-01-20 18:34 ` [Buildroot] [PATCH 2/3] defconfigs: use the new headers-version-same-as-kernel-version option Yann E. MORIN
2016-01-20 20:38 ` Thomas Petazzoni
2016-01-20 21:29 ` Peter Korsgaard [this message]
2016-01-20 21:37 ` Steve Calfee
2016-01-20 22:05 ` Thomas Petazzoni
2016-01-20 22:08 ` Yann E. MORIN
2016-01-20 21:58 ` Yann E. MORIN
2016-01-20 22:07 ` Thomas Petazzoni
2016-01-20 22:15 ` Yann E. MORIN
2016-01-20 18:34 ` [Buildroot] [PATCH 3/3] linux: drop the option to use the same version as that of the headers Yann E. MORIN
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=87powwrlbr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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