All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Sixth (and final?) release candidate for Xen 3.4.3
Date: Thu, 06 May 2010 13:17:08 -0700	[thread overview]
Message-ID: <4BE323C4.4090808@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1005062009380.3747@vega3.dur.ac.uk>

On 05/06/2010 12:13 PM, M A Young wrote:
> It was from stable-2.6.32.x circa 10th April. However I have lost the
> debuginfo rpm for that kernel, so I will try again with a more
> up-to-date kernel tomorrow.

Thanks.  No idea how that kernel was doing anything useful on a 3.4.2
Xen though, unless you'd also patched it?

    J

  reply	other threads:[~2010-05-06 20:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 12:00 Sixth (and final?) release candidate for Xen 3.4.3 Keir Fraser
2010-05-05  9:50 ` M A Young
2010-05-06 14:13 ` M A Young
2010-05-06 14:26   ` Keir Fraser
2010-05-06 16:13     ` M A Young
2010-05-06 16:34       ` Keir Fraser
2010-05-07  2:03         ` Zhang, Xiantao
2010-05-07  7:10           ` Keir Fraser
2010-05-07 23:11             ` Jeremy Fitzhardinge
2010-05-08  8:05               ` Keir Fraser
2010-05-08 11:00                 ` Boris Derzhavets
2010-05-08 15:14                   ` Errors when loading 2.6.32.12 under Xen 4.0 on ASUS P5Q-E Boris Derzhavets
2010-05-12 17:50                 ` Sixth (and final?) release candidate for Xen 3.4.3 Langsdorf, Mark
2010-05-12 19:21                   ` Keir Fraser
2010-05-12 19:42                     ` Langsdorf, Mark
2010-05-06 18:50   ` Jeremy Fitzhardinge
2010-05-06 19:13     ` M A Young
2010-05-06 20:17       ` Jeremy Fitzhardinge [this message]
2010-05-07 18:33         ` M A Young

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=4BE323C4.4090808@goop.org \
    --to=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=m.a.young@durham.ac.uk \
    --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 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.