All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: John Weber <rjohnweber@gmail.com>,
	 "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>
Subject: Re: Using a defconfig refers to an in-tree defconfig file
Date: Tue, 25 Feb 2014 15:10:53 -0700	[thread overview]
Message-ID: <530D14ED.9070705@boundarydevices.com> (raw)
In-Reply-To: <530D0B2B.7050006@gmail.com>

Hi John,

On 02/25/2014 02:29 PM, John Weber wrote:
> I thought I would bounce this one of the mailing list.
>
> Is there any reason why we shouldn't simply use the defconfig from the
> kernel tree if appropriate?
>
> We would do this by the defconfig file in the recipe refer to a filename
> in the kernel tree. For example, in the file
> recipes-kernel/linux/linux-wandboard-3.10.17/defconfig would be a single
> line:
>
>     use-kernel-config=wandboard_defconfig
>

In general, +1 from our end.

The primary down-side is that the Yocto needs may differ from other
distributions, but then again, any particular user will likely
want to tweak a bit anyway.

> I've tested this already and it works.
>
> As many of the kernels being used here are managing their own defconfigs
> in-tree, they are forced to keep the defconfig in the metadata in-sync.
 >
> This would be a way to remove that requirement.
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale



  reply	other threads:[~2014-02-25 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 21:29 Using a defconfig refers to an in-tree defconfig file John Weber
2014-02-25 22:10 ` Eric Nelson [this message]
2014-02-26  5:37   ` John Weber
2014-02-26 13:04     ` Otavio Salvador

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=530D14ED.9070705@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=rjohnweber@gmail.com \
    /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.