From: Greg KH <greg@kroah.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Kyle McMartin <kyle@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
stable@kernel.org, James Dingwall <james.dingwall@amdocs.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot
Date: Fri, 1 Oct 2010 11:26:41 -0700 [thread overview]
Message-ID: <20101001182641.GA9588@kroah.com> (raw)
In-Reply-To: <4CA61080.6070709@goop.org>
On Fri, Oct 01, 2010 at 09:46:56AM -0700, Jeremy Fitzhardinge wrote:
> On 09/29/2010 05:06 PM, Greg KH wrote:
> > On Wed, Sep 29, 2010 at 08:48:07AM -0700, Jeremy Fitzhardinge wrote:
> >>
> >> I should have pointed out it is the same in the stable-2.6.32 tree as well.
> > Yes, sorry, I know, I only had the chance to get the .35 release out
> > yesterday, I'll do the .32 one now.
> >
>
> Ping? Looks like the fix hasn't hit stable-2.6.32/master yet.
No it hasn't, sorry. Turns out the Embedded Linux kernel "summit" was
too interesting to get a stable kernel out during it, and I've been in a
train/plane/train/ferry/taxi/bed since then.
Should now be out in a few hours...
thanks,
greg k-h
prev parent reply other threads:[~2010-10-01 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:23 Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot James Dingwall
2010-09-23 17:53 ` Paweł Zuzelski
2010-09-24 18:00 ` Jeremy Fitzhardinge
2010-09-27 2:40 ` Kyle McMartin
2010-09-27 6:13 ` [stable] " Greg KH
2010-09-27 6:34 ` Kyle McMartin
2010-09-27 8:37 ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot [PATCH] James Dingwall
2010-09-28 18:29 ` Greg KH
2010-09-27 18:08 ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot Jeremy Fitzhardinge
2010-09-28 18:29 ` Greg KH
2010-09-29 15:48 ` Jeremy Fitzhardinge
2010-09-30 0:06 ` Greg KH
2010-10-01 16:46 ` Jeremy Fitzhardinge
2010-10-01 18:26 ` Greg KH [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=20101001182641.GA9588@kroah.com \
--to=greg@kroah.com \
--cc=james.dingwall@amdocs.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.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