Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Robert Yang <liezhi.yang@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] linux-yocto-tiny: fix KBRANCH
Date: Tue, 12 Apr 2016 08:33:17 -0400	[thread overview]
Message-ID: <570CEB0D.7090701@windriver.com> (raw)
In-Reply-To: <0877ab068513b9720c808aaeb0c8a90f9a45afc3.1460442964.git.liezhi.yang@windriver.com>

On 2016-04-12 2:36 AM, Robert Yang wrote:
> Fixed:
> WARNING: linux-yocto-tiny-4.4.3+gitAUTOINC+770996a263_73481a3abd-r0 do_patch: After meta data application, the kernel tree branch is standard/tiny/common-pc. The
> WARNING: linux-yocto-tiny-4.4.3+gitAUTOINC+770996a263_73481a3abd-r0 do_patch: SRC_URI specified branch standard/tiny/base. The branch will be forced to standard/tiny/base,
> WARNING: linux-yocto-tiny-4.4.3+gitAUTOINC+770996a263_73481a3abd-r0 do_patch: but this means the board meta data (.scc files) do not match the SRC_URI specification.
> WARNING: linux-yocto-tiny-4.4.3+gitAUTOINC+770996a263_73481a3abd-r0 do_patch: The meta data and branch standard/tiny/base should be inspected to ensure the proper
> WARNING: linux-yocto-tiny-4.4.3+gitAUTOINC+770996a263_73481a3abd-r0 do_patch: kernel is being built.
>
> Use standard/tiny/common-pc which is pointed by the .scc to fix problem.
> Btw, standard/tiny/base and standard/tiny/common-pc points to the same
> commit id.

When tiny eventually supports more architectures/boards we'll have
to change this again, but for the 2.1 release this is the change
with the least impact.

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

I can pick this patch up and put it in my queue, speak now if someone
else is going to grab it.

Bruce

>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>   meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +-
>   meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
> index 4c79bfd..37ff046 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
> @@ -1,4 +1,4 @@
> -KBRANCH ?= "standard/tiny/base"
> +KBRANCH ?= "standard/tiny/common-pc"
>   LINUX_KERNEL_TYPE = "tiny"
>   KCONFIG_MODE = "--allnoconfig"
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> index 9446da9..dcb545e 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> @@ -1,4 +1,4 @@
> -KBRANCH ?= "standard/tiny/base"
> +KBRANCH ?= "standard/tiny/common-pc"
>   LINUX_KERNEL_TYPE = "tiny"
>   KCONFIG_MODE = "--allnoconfig"
>
>



  reply	other threads:[~2016-04-12 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  6:36 [PATCH 0/1] linux-yocto-tiny: fix KBRANCH Robert Yang
2016-04-12  6:36 ` [PATCH 1/1] " Robert Yang
2016-04-12 12:33   ` Bruce Ashfield [this message]
2016-04-12 22:03     ` Richard Purdie
2016-04-13  2:54       ` Bruce Ashfield

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=570CEB0D.7090701@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox