All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Tom Zanussi <tom.zanussi@intel.com>,
	Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH 0/2] linux-yocto: intel staging and bxt backports
Date: Thu, 26 May 2016 12:40:56 -0400	[thread overview]
Message-ID: <bb17ec70-9bad-74af-27fd-cbf79d2a8e96@windriver.com> (raw)
In-Reply-To: <CAJTo0LYrq-TnfMbD-1_u-F56Xiq7pW-SRQv++Vo4-OzHcb355Q@mail.gmail.com>

On 2016-05-26 12:34 PM, Burton, Ross wrote:
>
> On 26 May 2016 at 16:36, Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>
>     We have a couple of patches to integrate broxton backports, and to
>     create some intel staging branches.
>
>
> With qemux86-64:
>
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: After meta data application, the kernel tree branch is
> standard/intel.
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: The SRC_URI specified branch standard/base.
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0 do_patch:
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: The branch will be forced to standard/base, but this means the
> board meta data
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: (.scc files) do not match the SRC_URI specification.
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0 do_patch:
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: The meta data and branch standard/base should be inspected to
> ensure the proper
> WARNING: linux-yocto-4.4.11+gitAUTOINC+1465ac389f_53e84104c5-r0
> do_patch: kernel is being built.

Crap. We'll have to adjust things, we want qemu to be using
standard/base.

Tom ?

Bruce

>
> Ross



  reply	other threads:[~2016-05-26 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 15:36 [PATCH 0/2] linux-yocto: intel staging and bxt backports Bruce Ashfield
2016-05-26 15:36 ` [PATCH 1/2] linux-yocto:4.4: broxton backports Bruce Ashfield
2016-05-26 15:36 ` [PATCH 2/2] linux-yocto: create intel branches Bruce Ashfield
2016-05-26 16:34 ` [PATCH 0/2] linux-yocto: intel staging and bxt backports Burton, Ross
2016-05-26 16:40   ` Bruce Ashfield [this message]
2016-05-26 17:06   ` 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=bb17ec70-9bad-74af-27fd-cbf79d2a8e96@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=saul.wold@intel.com \
    --cc=tom.zanussi@intel.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.