All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-yocto-custom: Clarify defconfig usage
Date: Wed, 3 Oct 2012 00:38:21 -0400	[thread overview]
Message-ID: <506BC13D.9030909@windriver.com> (raw)
In-Reply-To: <52507f028d9ec0e88078673e15e238d010cfaead.1349239001.git.dvhart@linux.intel.com>

On 12-10-03 12:36 AM, Darren Hart wrote:
> It is necessary to supply file://defconfig to the SRC_URI when using
> a defconfig (it is not implicitly understood as the commentary might
> currently suggest).

Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>

>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> CC: Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>   meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
> index 1f0b3a2..4115d2f 100644
> --- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
> +++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
> @@ -13,7 +13,8 @@
>   #
>   #   You must also provide a Linux kernel configuration. The most direct
>   #   method is to copy your .config to files/defconfig in your layer,
> -#   in the same directory as the bbappend.
> +#   in the same directory as the bbappend and add file://defconfig to
> +#   your SRC_URI.
>   #
>   #   To use the yocto kernel tooling to generate a BSP configuration
>   #   using modular configuration fragments, see the yocto-bsp and




  reply	other threads:[~2012-10-03  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03  4:36 [PATCH] linux-yocto-custom: Clarify defconfig usage Darren Hart
2012-10-03  4:38 ` Bruce Ashfield [this message]
2012-10-03 12:10   ` Andrea Adami
2012-10-03 12:33     ` Bruce Ashfield
2012-10-03 14:07       ` Andrea Adami
2012-10-03 14:41         ` Bruce Ashfield
2012-10-03 14:43         ` Darren Hart

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=506BC13D.9030909@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.