From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Paweł Zuzelski" <pawelz@pld-linux.org>
Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
lkml <linux-kernel@vger.kernel.org>,
James Dingwall <james.dingwall@amdocs.com>
Subject: Re: [Xen-devel] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot
Date: Fri, 24 Sep 2010 11:00:03 -0700 [thread overview]
Message-ID: <4C9CE723.5090308@goop.org> (raw)
In-Reply-To: <20100924054000.GA4689@pzz.touk.pl>
On 09/23/2010 10:40 PM, Paweł Zuzelski wrote:
> Have you seen the message from James Dingwall?
>
> He had found the typo in fb412a178502dc498430723b082a932f797e4763
> commit and sent the patch to lkml that fixes it.
>
> Please, see https://patchwork.kernel.org/patch/202282/ if you have
> not received James' mail. That patch resolves the problem for me and
> for James.
>
(!) Oh, well. Yes, that would explain it. I'd noticed the missing 'x',
but assumed I'd just done it with an editor fat-finger...
Looks like upstream is OK, so it crept in with the stable
cherry-pick/backport to both stable-2.6.32/master and stable-2.6.35/master.
J
prev parent reply other threads:[~2010-09-24 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 19:05 PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot Paweł Zuzelski
2010-09-24 0:02 ` [Xen-devel] " Jeremy Fitzhardinge
2010-09-24 2:13 ` Dan Magenheimer
2010-09-24 19:04 ` [Xen-devel] " Jeremy Fitzhardinge
2010-09-24 5:40 ` Paweł Zuzelski
2010-09-24 18:00 ` Jeremy Fitzhardinge [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=4C9CE723.5090308@goop.org \
--to=jeremy@goop.org \
--cc=james.dingwall@amdocs.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawelz@pld-linux.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).