Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Scott Garman <scott.a.garman@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/58] denzil pull request 2
Date: Tue, 25 Sep 2012 09:11:52 +0100	[thread overview]
Message-ID: <1348560712.8662.28.camel@ted> (raw)
In-Reply-To: <cover.1348532322.git.scott.a.garman@intel.com>

On Mon, 2012-09-24 at 17:24 -0700, Scott Garman wrote:
> Hello,
> 
> If this works I'll hopefully be submitting the cover letter only,
> this patchset is pretty big. 
> 
> I've got a lot of patches for denzil now that I'd like to get merged
> before they get too out of hand, so here is my pull request for it,
> along with autobuilder output and explanation.
> 
> Note, the autobuilder run was done with my poky-based branch.
> 
> nightly-x86:
> http://autobuilder.yoctoproject.org:8010/builders/nightly-x86/builds/729
> 
> All builds green except for atom-pc, which fails during build_hddimg of
> do_bootimg due to the kernel image file not being found in the target
> sysroot.

Which broke due to:

http://cgit.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next-pull2&id=0e3e88f9f87d1083ddd7dcaa526b3cd7a1cd53ff

so I think you need:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d9302305faf4ec733dc9a98f91f5014eb814d62d

to fix the atom-pc errors.

I am nervous about the number of version upgrades in here. Perhaps
someone can summarise what the problem is and why we need them?

Cheers,

Richard




  reply	other threads:[~2012-09-25  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  0:24 [PATCH 00/58] denzil pull request 2 Scott Garman
2012-09-25  8:11 ` Richard Purdie [this message]
2012-09-25 16:09   ` Scott Garman
2012-09-28 15:54 ` Richard Purdie

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=1348560712.8662.28.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox