All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Ian Campbell" <ijc@hellion.org.uk>,
	"Daniel Schröder" <mail@dschroeder.info>,
	"Ingo Molnar" <mingo@elte.hu>, "Yinghai Lu" <yinghai@kernel.org>,
	"Stable Kernel" <stable@kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [stable] Change 5c371b31be3203 in stable breaks Xen
Date: Tue, 25 Nov 2008 16:03:40 -0800	[thread overview]
Message-ID: <20081126000340.GB1091@kroah.com> (raw)
In-Reply-To: <492C897E.1010509@goop.org>

On Tue, Nov 25, 2008 at 03:25:50PM -0800, Jeremy Fitzhardinge wrote:
> Ian Campbell wrote:
> > On Tue, 2008-11-25 at 13:26 -0800, Jeremy Fitzhardinge wrote:
> >   
> >> I have a report of Xen breaking between 2.6.27.5 and .6.  I bisected
> >> it 
> >> down to change:
> >>
> >> commit 5c371b31be32033b0a4a993431484da8a2305369
> >> Author: Yinghai Lu <yhlu.kernel@gmail.com>
> >> Date:   Mon Sep 22 02:52:26 2008 -0700
> >>
> >>     x86: fix CONFIG_X86_RESERVE_LOW_64K=y
> >>    
> >>     commit 2216d199b1430d1c0affb1498a9ebdbd9c0de439 upstream
> >>     
> >
> > Looks like 5dc64a3442b98eaa0e3730c35fcf00cf962a93e7 might be needed in
> > stable too?
> >   
> 
> Ah, yes, that looks like the right fix.  I'll see if it helps.

If so, let us know and we will add it to the next -stable release.

thanks,

greg k-h

  reply	other threads:[~2008-11-26  0:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:26 Change 5c371b31be3203 in stable breaks Xen Jeremy Fitzhardinge
2008-11-25 23:06 ` Ian Campbell
2008-11-25 23:25   ` Jeremy Fitzhardinge
2008-11-26  0:03     ` Greg KH [this message]
2008-11-26 20:41       ` [stable] " Jeremy Fitzhardinge

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=20081126000340.GB1091@kroah.com \
    --to=greg@kroah.com \
    --cc=ijc@hellion.org.uk \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@dschroeder.info \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    --cc=yinghai@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 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.