From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_LINUX_KERNEL_PATCH for linux-headers
Date: Wed, 11 Jul 2018 23:02:41 +0200 [thread overview]
Message-ID: <60e837dd-e80e-c0c3-a5b4-7cb60e87f7f3@mind.be> (raw)
In-Reply-To: <fea35efb-0134-f091-5cbd-30292f137b33@gmail.com>
On 11-07-18 16:32, Serj Kalichev wrote:
> Hello.
>
> Both linux and linux-headers package use BR2_LINUX_KERNEL_PATCH. But
> BR2_LINUX_KERNEL_PATCH is available if BR2_LINUX_KERNEL is selected. I want to
> build toolchain only. And don't want to build linux kernel. So I deselect
> BR2_LINUX_KERNEL and lose BR2_LINUX_KERNEL_PATCH for linux-headers.
>
> I think BR2_LINUX_KERNEL_PATCH must not depend on BR2_LINUX_KERNEL.
It's not easy to do that properly, because you'd still need to go to the kernel
menu to set the kernel patch list.
Anyway, we consider BR2_LINUX_KERNEL_PATCH as deprecated. Use
BR2_GLOBAL_PATCH_DIR instead, and add your patches in the linux-headers
subdirectory of that directory.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2018-07-11 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:32 [Buildroot] BR2_LINUX_KERNEL_PATCH for linux-headers Serj Kalichev
2018-07-11 21:02 ` Arnout Vandecappelle [this message]
2018-07-12 12:33 ` Serj Kalichev
2018-07-13 10:01 ` Arnout Vandecappelle
2018-07-13 12:24 ` Serj Kalichev
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=60e837dd-e80e-c0c3-a5b4-7cb60e87f7f3@mind.be \
--to=arnout@mind.be \
--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.