All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-headers: remove 2.6 snapshot
Date: Mon, 24 Feb 2014 18:59:22 +0100	[thread overview]
Message-ID: <20140224175922.GA11048@free.fr> (raw)
In-Reply-To: <530AEFC9.1040508@mind.be>

Arnout, All,

On 2014-02-24 08:07 +0100, Arnout Vandecappelle spake thusly:
> On 02/23/14 21:34, Yann E. MORIN wrote:
> > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > 
> > As Thomas states:
> >     It is completely weird to ask the tarball to be named exactly
> >     linux-2.6.tar.bz2. IMO, we should simply get rid of this feature.
> > 
> > Make it so! ;-)
> > 
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> >  package/linux-headers/Config.in.host | 4 ----
> >  1 file changed, 4 deletions(-)
> > 
> > diff --git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
> > index 134e338..fcecd62 100644
> > --- a/package/linux-headers/Config.in.host
> > +++ b/package/linux-headers/Config.in.host
> > @@ -56,9 +56,6 @@ choice
> >  
> >  	config BR2_KERNEL_HEADERS_VERSION
> >  		bool "Manually specified Linux version"
> > -
> > -	config BR2_KERNEL_HEADERS_SNAP
> > -		bool "Local Linux snapshot (linux-2.6.tar.bz2)"
> >  endchoice
> >  
> >  config BR2_DEFAULT_KERNEL_VERSION
> > @@ -81,5 +78,4 @@ config BR2_DEFAULT_KERNEL_HEADERS
> >  	default "3.11.10"	if BR2_KERNEL_HEADERS_3_11
> >  	default "3.12.13"	if BR2_KERNEL_HEADERS_3_12
> >  	default "3.13.5"	if BR2_KERNEL_HEADERS_3_13
> > -	default "2.6"		if BR2_KERNEL_HEADERS_SNAP
> >  	default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
> > 
> 
>  This is missing Config.in.legacy support. The help text of the legacy
> support should mention that the same can be achieved by using
> BR2_LINUX_KERNEL_CUSTOM_TARBALL.

In retrospect, BR2_LINUX_KERNEL_CUSTOM_TARBALL is for building the
kernel. It is not used to install the headers, which is what we are
doing here.

We still need to add a legacy option, though.

Regarrds,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2014-02-24 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 20:34 [Buildroot] [PATCH] package/linux-headers: remove 2.6 snapshot Yann E. MORIN
2014-02-24  7:07 ` Arnout Vandecappelle
2014-02-24 17:19   ` Yann E. MORIN
2014-02-24 17:59   ` Yann E. MORIN [this message]
2014-02-24 20:28     ` Peter Korsgaard

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=20140224175922.GA11048@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.