Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] linux-yocto: mips, -rt update and yocto-custom fix
Date: Mon, 1 Apr 2013 15:25:16 -0400	[thread overview]
Message-ID: <5159DF1C.7010000@windriver.com> (raw)
In-Reply-To: <146E9829-6FA3-4124-8BF2-5B31B8CA146C@gmail.com>

On 13-04-01 03:24 PM, Khem Raj wrote:
>
> On Apr 1, 2013, at 10:09 AM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>
>> [PATCH 1/3] linux-yocto/3.8: update mips SA_RESTORER fix
>>
>>     During the 3.8.4 integration there was a build issue on MIPS due to
>>     SA_RESTORER changes. A solution was put in place for mips, but it
>>     didn't cover other impacted architectures.
>>
>>     This is a backport of the proposed fix for the next 3.8-stable,
>>     since the full -stable might not be available in the right timeframe.
>
>
> Does this fix systemd/ crash and/or mips64 boot on qemu I wonder

It may .. since the fix is broader than the one that I did before.
Now that this it out, I'm gearing up to do systemd boots with
mips/mips64.

Bruce

>




      reply	other threads:[~2013-04-01 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 17:09 [PATCH 0/3] linux-yocto: mips, -rt update and yocto-custom fix Bruce Ashfield
2013-04-01 17:09 ` [PATCH 1/3] linux-yocto/3.8: update mips SA_RESTORER fix Bruce Ashfield
2013-04-01 17:09 ` [PATCH 2/3] kernel-yocto: use KBRANCH as default build branch Bruce Ashfield
2013-04-01 17:09 ` [PATCH 3/3] linux-yocto-rt: integrate 3.8.4-rt2 Bruce Ashfield
2013-04-01 19:24 ` [PATCH 0/3] linux-yocto: mips, -rt update and yocto-custom fix Khem Raj
2013-04-01 19:25   ` Bruce Ashfield [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=5159DF1C.7010000@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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