From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Fri, 31 May 2013 08:07:52 +0100 [thread overview]
Message-ID: <1369984072.14887.338.camel@ted> (raw)
In-Reply-To: <51A83FDB.4010309@linux.intel.com>
On Fri, 2013-05-31 at 15:14 +0900, Saul Wold wrote:
> On 05/31/2013 12:28 PM, Bruce Ashfield wrote:
> > Richard/Saul,
> >
> > While I continue to battle with gcc 4.8, I've got a collection of other fixes
> > that don't need to wait. Here's part of those pending changes.
> >
> > - Remove the yocto 3.2 kernel, early in the Yocto 1.5 cycle as promised
>
> Did I miss a request to remove the .bbappend from meta-yocto-bsp? There
> seems to be a 3.2 bbappend still.
In the interests of getting roughly caught up with patches, I've added a
patch to delete this as well...
Cheers,
Richard
next prev parent reply other threads:[~2013-05-31 7:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 3:28 [PATCH 0/4] kernel-yocto: consolidated pull request Bruce Ashfield
2013-05-31 3:28 ` [PATCH 1/4] linux-yocto: remove 3.2 kernel recipes Bruce Ashfield
2013-05-31 3:28 ` [PATCH 2/4] qemu*: restrict NFSD to linux-yocto only Bruce Ashfield
2013-05-31 3:28 ` [PATCH 3/4] linux-yocto: v3.8.13 and v3.4.46 Bruce Ashfield
2013-05-31 3:28 ` [PATCH 4/4] kern-tools: expand kernel features that point to a directory name Bruce Ashfield
2013-05-31 6:14 ` [PATCH 0/4] kernel-yocto: consolidated pull request Saul Wold
2013-05-31 7:07 ` Richard Purdie [this message]
2013-05-31 12:29 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 21:36 Bruce Ashfield
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
2019-12-30 3:07 bruce.ashfield
2020-03-04 14:55 bruce.ashfield
2020-08-03 12:30 Bruce Ashfield
2025-04-10 18:55 bruce.ashfield
2025-04-10 20:24 ` 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=1369984072.14887.338.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.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