From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: make custom versions and patches exclusive
Date: Wed, 7 Jan 2015 21:47:00 +0100 [thread overview]
Message-ID: <20150107214700.5474b6ea@free-electrons.com> (raw)
In-Reply-To: <1420582613-27692-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Dear Vivien Didelot,
On Tue, 6 Jan 2015 17:16:53 -0500, Vivien Didelot wrote:
> When using a custom kernel (custom tarball, repository or local tree),
> we're using the OVERRIDE_SRCDIR internally, which means we do not apply
> patches. Since this is the expected behavior, show the
> LINUX_KERNEL_PATCH option only when using a vanilla kernel.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> Cc: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> linux/Config.in | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/linux/Config.in b/linux/Config.in
> index bf30426..3845758 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -119,6 +119,9 @@ config BR2_LINUX_KERNEL_VERSION
>
> config BR2_LINUX_KERNEL_PATCH
> string "Custom kernel patches"
> + depends on BR2_LINUX_KERNEL_LATEST_VERSION || \\
> + BR2_LINUX_KERNEL_SAME_AS_HEADERS || \\
> + BR2_LINUX_KERNEL_CUSTOM_VERSION
> help
> A space-separated list of patches to apply to the
> kernel. Each patch can be described as an URL, a local file
While I agree that we cannot apply patches when using
BR2_LINUX_KERNEL_CUSTOM_LOCAL, I think there is no reason to not
support patches when using a custom Git or Mercurial repository. It
works currently (contrary to the local case, which doesn't work), and I
don't see a reason to prevent these use cases. To me, they are very
valid: I can be using a custom vendor-provided kernel tree, and still
need to have some local patches to adapt the kernel to my board. Of
course, I could put those patches in my own kernel Git repository, but
if I don't have many of them, it might be more convenient to just have
those few patches in the Buildroot tree.
So, I think the patch should be changed to use instead:
depends on !BR2_LINUX_KERNEL_CUSTOM_LOCAL
I've marked the patch as Changes Requested in patchwork.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-07 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 22:16 [Buildroot] [PATCH] linux: make custom versions and patches exclusive Vivien Didelot
2015-01-06 22:22 ` Yann E. MORIN
2015-01-07 20:47 ` Thomas Petazzoni [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=20150107214700.5474b6ea@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.