All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>,
	yocto-builds <yocto-builds@yoctoproject.org>,
	"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>,
	"saul.wold" <saul.wold@intel.com>,
	Denys Dmytriyenko <denys@ti.com>,
	"Hart, Darren" <darren.hart@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: meta-yocto-bsp changes and 3.14
Date: Fri, 28 Mar 2014 18:24:07 +0000	[thread overview]
Message-ID: <1396031047.14790.24.camel@ted> (raw)

I've merged Bruce's 3.14 patches into master-next. With the yocto-bsp
parts that I could pull together, there seemed to be some pieces
missing, specifically:

* the yocto-linux-dev.bbappend was underpopulated
* the yocto-linux-3.14.bbappend was missing
* no removal of beagleboard
* no addition to the README for beaglebone
* local.conf.sample needs updates
* missing edgerouter configuration in linux-yocto*
* should we be removing a mips BSP?
* need a layer version bump so beth can handle this on the autobuilder

I added commits for some of these, the 3.14 kernel bbappend is missing
SRCREVs though for example. The state of where I got to is:

http://git.yoctoproject.org/cgit.cgi/meta-yocto/log/?h=master-next

Beth: Your AR is to figure out the autobuilder side of this and build
the two new replacement BSPs (beaglebone and edgerouter) instead of the
old ones. When that and the current build on the AB is done, can we run
a build of master-next please?

Denys: I'm hoping you can help out with the README

Bruce: can you look at the linux-yocto-* changes, particularly the 3.14
SRCREVs and that linux-yocto-dev looks right?

Cheers,

Richard




             reply	other threads:[~2014-03-28 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 18:24 Richard Purdie [this message]
2014-03-28 18:27 ` meta-yocto-bsp changes and 3.14 Bruce Ashfield
2014-03-28 18:28   ` Bruce Ashfield
2014-03-28 18:34     ` Richard Purdie
2014-03-28 18:38       ` Bruce Ashfield
     [not found]         ` <CF5B1473.7DC1D%darren.hart@intel.com>
2014-03-28 18:59           ` Bruce Ashfield
     [not found]             ` <CF5B160D.7DC33%darren.hart@intel.com>
2014-03-28 19:08               ` Bruce Ashfield
2014-03-28 19:12                 ` Denys Dmytriyenko
2014-03-28 19:14                   ` Bruce Ashfield
     [not found]                     ` <CF5B18D7.7DC4F%darren.hart@intel.com>
2014-03-28 19:27                       ` Bruce Ashfield
     [not found]                         ` <CF5B2B7A.7DCA2%darren.hart@intel.com>
2014-03-28 20:41                           ` Bruce Ashfield
     [not found] ` <20140328183036.GG12929@edge>
2014-03-28 18:32   ` Bruce Ashfield
2014-03-28 18:38 ` Denys Dmytriyenko
2014-03-28 19:48 ` Flanagan, Elizabeth
2014-03-28 19:58 ` Bruce Ashfield
2014-03-29 23:12   ` Richard Purdie
2014-03-30 12:37     ` Richard Purdie
2014-03-30 19:22       ` Bruce Ashfield
2014-03-31 14:55       ` Denys Dmytriyenko
2014-03-31 15:07         ` Denys Dmytriyenko
2014-03-30 14:46     ` 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=1396031047.14790.24.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Bruce.Ashfield@windriver.com \
    --cc=darren.hart@intel.com \
    --cc=denys@ti.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@intel.com \
    --cc=yocto-builds@yoctoproject.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.