Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
	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 23:03:20 +0100	[thread overview]
Message-ID: <1460498600.9308.71.camel@linuxfoundation.org> (raw)
In-Reply-To: <570CEB0D.7090701@windriver.com>

On Tue, 2016-04-12 at 08:33 -0400, Bruce Ashfield wrote:
> 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.

I took this into -next on the basis that its better if I can test
things sooner. The tiny build passed so I can merge this if
appropriate.

Cheers,

Richard


  reply	other threads:[~2016-04-12 22:03 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
2016-04-12 22:03     ` Richard Purdie [this message]
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=1460498600.9308.71.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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