From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] linux-yocto: perf, unionfs, yaffs2 fixes
Date: Tue, 10 Jul 2012 13:28:43 -0400 [thread overview]
Message-ID: <4FFC664B.7020202@windriver.com> (raw)
In-Reply-To: <4FFC6403.7070702@windriver.com>
On 12-07-10 01:18 PM, Bruce Ashfield wrote:
> On 12-07-10 01:18 PM, Saul Wold wrote:
>> On 07/10/2012 10:11 AM, Bruce Ashfield wrote:
>>> Saul,
>>>
>>> Here are the SRCREV updates to activate Tom's mips perf fix (3.2
>>> and 3.4).
>>>
>>> For 3.4, we also have a yaffs2 and unionfs fix.
>>>
>> Bruce, Tom:
>>
>> Can you generate a single patch set that contains both the kernel update
>> and any perf recipe changes. That will avoid any further confusion.
>
> At this point, I'd rather not. My changes are complete with perf +
> other fixes in a consolidated pull .. and I'm juggling my own set
> of integrations.
>
> I'm honestly not seeing the complexity.
Any by this, I mean that my kernel update builds and works independently
and happens to contain a fix to the perf problem you are seeing. So it
should be merged independently, and then you can layer on any commits
from tom.
Cheers,
Bruce
>
> Cheers,
>
> Bruce
>
>>
>> Thanks
>> Sau!
>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>> The following changes since commit
>>> 029e3cea52f86438a1d6868020b8888b5c93d623:
>>>
>>> bitbake: fetch2/wget: Use FETCHCMD_wget to provide the commandline and
>>> options (2012-07-10 14:25:38 +0100)
>>>
>>> are available in the git repository at:
>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>
>>> Bruce Ashfield (2):
>>> linux-yocto/3.2: perf: fix mips build
>>> linux-yocto/3.4: perf, unionfs and yaffs2 fixes
>>>
>>> meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 4 ++--
>>> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 4 ++--
>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb | 2 +-
>>> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 12 ++++++------
>>> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 12 ++++++------
>>> 5 files changed, 17 insertions(+), 17 deletions(-)
>>>
>>
>
next prev parent reply other threads:[~2012-07-10 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 17:11 [PATCH 0/2] linux-yocto: perf, unionfs, yaffs2 fixes Bruce Ashfield
2012-07-10 17:11 ` [PATCH 1/2] linux-yocto/3.2: perf: fix mips build Bruce Ashfield
2012-07-10 17:11 ` [PATCH 2/2] linux-yocto/3.4: perf, unionfs and yaffs2 fixes Bruce Ashfield
2012-07-10 17:18 ` [PATCH 0/2] linux-yocto: perf, unionfs, " Saul Wold
2012-07-10 17:18 ` Bruce Ashfield
2012-07-10 17:28 ` Bruce Ashfield [this message]
2012-07-10 18:23 ` Tom Zanussi
2012-07-10 19:27 ` 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=4FFC664B.7020202@windriver.com \
--to=bruce.ashfield@windriver.com \
--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