All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/{ea3250, fdi3250, phy3250}: lock down kernel headers version
Date: Wed, 06 Feb 2013 17:52:00 -0300	[thread overview]
Message-ID: <5112C270.90503@zacarias.com.ar> (raw)
In-Reply-To: <5112C01E.2090807@mind.be>

On 02/06/2013 05:42 PM, Arnout Vandecappelle wrote:
>  This should really be done for all defconfigs that build a custom
> kernel version:
> 
> arm_foundationv8_defconfig
> armadeus_apf9328_defconfig
> at91sam9g20dfc_defconfig
> atstk100x_defconfig
> beaglebone_defconfig
> calao_snowball_defconfig
> kb9202_defconfig
> mini2440_defconfig
> mx53loco_defconfig
> sheevaplug_defconfig
> 
>  And the ones that allow it should probably set
> BR2_LINUX_KERNEL_SAME_AS_HEADERS.
> 
>  But all that is a lot of testing :-)

Yes, i'm sending as i'm testing :)
I'll also be switching these ones (*3250*) configs to git tags/releases
!= master because there's a filename clash possibility there.
Not at the moment though since those use the same upstream and no other
BSP config does that, but it could happen.

>  Only BR2_DEFAULT_KERNEL_VERSION is necessary -
> BR2_DEFAULT_KERNEL_HEADERS is derived from it by Kconfig.

Cool, i'll minimize them then.
Regards.

  reply	other threads:[~2013-02-06 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 20:21 [Buildroot] [PATCH] configs/{ea3250, fdi3250, phy3250}: lock down kernel headers version Gustavo Zacarias
2013-02-06 20:42 ` Arnout Vandecappelle
2013-02-06 20:52   ` Gustavo Zacarias [this message]
2013-02-07 16:07 ` 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=5112C270.90503@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.