All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [PATCH 0/1] qemuppc: fix 2.6.37 build failure
Date: Mon, 13 Dec 2010 10:37:06 -0800	[thread overview]
Message-ID: <4D0667D2.20507@linux.intel.com> (raw)
In-Reply-To: <cover.1292218710.git.bruce.ashfield@windriver.com>

On 12/12/2010 09:41 PM, Bruce Ashfield wrote:
> Somehow the ppc32 irq routines were only partially updated
> to 2.6.37. I'll have to check later to see what happened, since
> these were all built and booted here.
>
> The fix is simple enough, here's the update for the SRCREV
> that gets qemuppc building again.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
>    qemuppc: update 2.6.37 SRCREV
>
>   .../conf/distro/include/poky-default-revisions.inc |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Bruce,

Thanks for the fast turn on these fixes, there are pulled into master 
and the 1.0 M2 branch.

Sau!


WARNING: multiple messages have this Message-ID (diff)
From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [poky] [PATCH 0/1] qemuppc: fix 2.6.37 build failure
Date: Mon, 13 Dec 2010 10:37:06 -0800	[thread overview]
Message-ID: <4D0667D2.20507@linux.intel.com> (raw)
In-Reply-To: <cover.1292218710.git.bruce.ashfield@windriver.com>

On 12/12/2010 09:41 PM, Bruce Ashfield wrote:
> Somehow the ppc32 irq routines were only partially updated
> to 2.6.37. I'll have to check later to see what happened, since
> these were all built and booted here.
>
> The fix is simple enough, here's the update for the SRCREV
> that gets qemuppc building again.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
>    qemuppc: update 2.6.37 SRCREV
>
>   .../conf/distro/include/poky-default-revisions.inc |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Bruce,

Thanks for the fast turn on these fixes, there are pulled into master 
and the 1.0 M2 branch.

Sau!


  parent reply	other threads:[~2010-12-13 18:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13  5:41 [PATCH 0/1] qemuppc: fix 2.6.37 build failure Bruce Ashfield
2010-12-13  5:41 ` [PATCH 1/1] qemuppc: update 2.6.37 SRCREV Bruce Ashfield
2010-12-13 18:37 ` Saul Wold [this message]
2010-12-13 18:37   ` [poky] [PATCH 0/1] qemuppc: fix 2.6.37 build failure Saul Wold

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=4D0667D2.20507@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.