Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code"
Date: Sat, 27 Aug 2016 22:23:53 +0200	[thread overview]
Message-ID: <20160827222353.02bc0df2@free-electrons.com> (raw)
In-Reply-To: <1467066844-28355-1-git-send-email-yann.morin.1998@free.fr>

Peter, Yann,

Peter: do you have an opinion on this patch. If not, I think I'm going
to apply it, so please raise your opinion if you disagree.

Yann: a few questions below.

On Tue, 28 Jun 2016 00:34:04 +0200, Yann E. MORIN wrote:
> -config BR2_LINUX_KERNEL_CUSTOM_LOCAL
> -	bool "Local directory"
> -	help
> -	  This option allows Buildroot to get the Linux kernel source
> -	  code from a local directory.

What about Config.in.legacy handling?

>  # Compute LINUX_SOURCE and LINUX_SITE from the configuration
> -ifeq ($(BR2_LINUX_KERNEL_CUSTOM_TARBALL),y)
> +ifeq ($(LINUX_VERSION),custom)

Why are you doing this change?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-27 20:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 22:34 [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code" Yann E. MORIN
2016-08-27 20:23 ` Thomas Petazzoni [this message]
2016-08-27 22:54   ` Yann E. MORIN
2016-08-28  7:23     ` Thomas Petazzoni
2016-08-28 20:37   ` Peter Korsgaard
2016-08-28 21:48     ` Yann E. MORIN
2016-08-29  7:16       ` Thomas Petazzoni
2016-12-12  3:06         ` James Knight
2016-12-12 16:27           ` Thomas Petazzoni
2016-12-12 17:35           ` Yann E. MORIN
2016-12-12 17:52             ` Thomas Petazzoni
2016-12-12 22:31               ` James Knight

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=20160827222353.02bc0df2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox