Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2][rocko] linux-yocto/4.12: update to v4.12.20
Date: Tue, 20 Feb 2018 00:12:11 +0000	[thread overview]
Message-ID: <1519085531.24236.271.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4MjxCe1gY2zf6iro3DdQYs6_HZ9kH9SymcvhBJ8FJm1WA@mail.gmail.com>

On Mon, 2018-02-19 at 11:45 -0500, Bruce Ashfield wrote:
> On Mon, Feb 19, 2018 at 11:37 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Mon, 2018-02-19 at 08:16 -0800, akuster808 wrote:
> > > 
> > > Bruce,
> > > 
> > > thanks. I hand applied this as I have another kernel change
> > > sitting
> > > in
> > > stable/rocko-next
> > > 
> > > I will build this once RP is done with master
> > You correctly pointed out I needed to sort master first! :)
> > 
> > Bruce: Is there an update for 4.9 in rocko? If so we should perhaps
> > pull that in too before we rebuild 2.4.2?
> I haven't done a patch for 4.9 in rocko, but can. Give me a few
> minutes and
> will send one out.

Thanks. Master is sorted apart from the scripts sigs issue which should
be simple to fix.

Rocko is looking a bit tricky, the qemuarm64 kernel is failing to boot:

https://autobuilder.yocto.io/builders/nightly-arm64/builds/755/steps/Running%20Sanity%20Tests/logs/stdio

so 4.12 qemuarm64 looks like it may be bust. Armin ran it twice and it
happened twice on different builders.

Cheers,

Richard


      reply	other threads:[~2018-02-20  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 15:40 [PATCH v2][rocko] linux-yocto/4.12: update to v4.12.20 Bruce Ashfield
2018-02-19 16:16 ` akuster808
2018-02-19 16:37   ` Richard Purdie
2018-02-19 16:45     ` Bruce Ashfield
2018-02-20  0:12       ` Richard Purdie [this message]

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=1519085531.24236.271.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.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