public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/9] kernel-yocto: consolidated pull request
Date: Tue, 22 Aug 2017 16:28:57 +0100	[thread overview]
Message-ID: <1503415737.32591.112.camel@linuxfoundation.org> (raw)
In-Reply-To: <7f1c93bd-0d0d-b4c4-d084-2a75d7362481@windriver.com>

On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
> On 08/22/2017 10:24 AM, Richard Purdie wrote:
> > 
> > Thanks, I think you got that one but the /bin/awk issue remained
> > after
> > your changes. Its easy to reproduce with "bitbake core-image-sato-
> > sdk",
> > or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this
> > change
> > to fix it:
> Yah, I noticed all of those references as well. Saul had dealt with
> the one that hit us before, but I wasn't able to trigger any installs
> of the other parts in the images I built .. so they were being left
> be for now, just to keep our footprint low.
> 
> > 
> > 
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=
> > a28acfa6c5890df4f5cb09962ef0c53837ac3b37
> > 
> > which I appreciate you won't like but it illustrates the problem.
> > Any
> > preference on what to do with that patch?
> I can merge it directly into linux-yocto, since that is what we did
> with Saul's change before, and at the same time, we can submit it
> upstream and drop it next release.

Ok, Should I merge my patch for now and you and then deal with it in
due course or do you want to do that directly?

I can take care of the mips issue but we have one final problem:

"oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"

is failing, it works with 4.10, fails with 4.12. Did some key config
option for booting isos go missing?

Cheers,

Richard


  reply	other threads:[~2017-08-22 15:28 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  2:58 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2017-08-21  2:58 ` [PATCH 1/9] kernel-yocto: configuration updates: x86 features Bruce Ashfield
2017-08-21  2:58 ` [PATCH 2/9] linux-yocto/4.1: fix fsl-ls10xx sdhci Bruce Ashfield
2017-08-21  2:58 ` [PATCH 3/9] linux-yocto: add usb-net configs by default Bruce Ashfield
2017-08-21  2:58 ` [PATCH 4/9] linux-yocto: introduce 4.12 recipes Bruce Ashfield
2017-08-21  2:58 ` [PATCH 5/9] linux-yocto: remove 4.1 recipes Bruce Ashfield
2017-08-21  2:58 ` [PATCH 6/9] libc-headers: update to 4.12 Bruce Ashfield
2017-08-21  2:58 ` [PATCH 7/9] qemu: bump default version " Bruce Ashfield
2017-08-21  2:58 ` [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built Bruce Ashfield
2017-08-21 15:00   ` Peter Kjellerstedt
2017-08-21 15:03     ` Bruce Ashfield
2017-08-21 15:13       ` Bruce Ashfield
2017-08-21 15:16         ` Peter Kjellerstedt
2017-08-21 15:18           ` Bruce Ashfield
2017-08-23  3:40   ` Khem Raj
2017-08-23 12:37     ` Bruce Ashfield
2017-08-23 14:40       ` Khem Raj
2017-08-23 14:42         ` Bruce Ashfield
2017-08-23 14:58           ` Richard Purdie
2017-08-23 15:00             ` Bruce Ashfield
2017-08-23 15:07             ` Khem Raj
2017-08-23 18:31   ` Denys Dmytriyenko
2017-08-23 18:56     ` Bruce Ashfield
2017-08-21  2:58 ` [PATCH 9/9] linux-yocto/4.10: CVE & misc fixes Bruce Ashfield
2017-08-21  3:05 ` ✗ patchtest: failure for kernel-yocto: consolidated pull request Patchwork
2017-08-21 11:42 ` [PATCH 0/9] " Richard Purdie
2017-08-21 12:11   ` Bruce Ashfield
2017-08-21 13:01     ` Bruce Ashfield
2017-08-21 15:55 ` Richard Purdie
2017-08-21 15:57   ` Bruce Ashfield
2017-08-21 16:12   ` Bruce Ashfield
2017-08-22 14:24     ` Richard Purdie
2017-08-22 14:54       ` Bruce Ashfield
2017-08-22 15:28         ` Richard Purdie [this message]
2017-08-22 15:34           ` Bruce Ashfield
2017-08-22 16:00             ` Richard Purdie
2017-08-22 16:04               ` Bruce Ashfield
2017-08-22 16:07                 ` Richard Purdie
2017-08-22 16:20                   ` Bruce Ashfield
2017-08-22 17:13                   ` Bruce Ashfield
2017-08-22 20:34                   ` Bruce Ashfield
2017-08-22 21:56                     ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2017-09-14 13:46 Bruce Ashfield
2018-03-06 18:11 Bruce Ashfield
2018-06-07  2:07 Bruce Ashfield
2020-02-05 23:12 bruce.ashfield
2020-02-06  9:03 ` Richard Purdie
2020-02-06 13:25   ` Bruce Ashfield
2021-05-17 22:16 Bruce Ashfield
2022-09-19 14:28 bruce.ashfield
2022-09-20  9:45 ` Richard Purdie
2022-09-20 12:21 ` Richard Purdie
2022-09-20 12:53   ` Bruce Ashfield
2022-09-20 12:55     ` Richard Purdie
2022-09-20 20:29       ` 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=1503415737.32591.112.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@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