public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	intel-gfx@lists.freedesktop.org, woodys@xandros.com,
	stefan.bader@canonical.com, linux-kernel@vger.kernel.org,
	penberg@cs.helsinki.fi, apw@canonical.com,
	tim.gardner@canonical.com, torvalds@linux-foundation.org,
	stable@kernel.org
Subject: Re: [stable] [Intel-gfx] Intel 915GM MCHBAR bug
Date: Mon, 29 Jun 2009 10:33:08 -0700	[thread overview]
Message-ID: <20090629173308.GB3901@kroah.com> (raw)
In-Reply-To: <20090609152828.d82528f3.akpm@linux-foundation.org>

On Tue, Jun 09, 2009 at 03:28:28PM -0700, Andrew Morton wrote:
> On Tue, 9 Jun 2009 15:07:57 -0700
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> 
> > > > Andrew Morton wrote:
> > > > > These might end up being 2.6.30.1 material.
> > > > 
> > > > Yes, agreed completely. We probably want ACK from Jesse and Bjorn,
> > > > though.
> > > 
> > > I'm ok with it being 2.6.30.1 stuff, but given the significance of the
> > > change we were worried about putting it into 2.6.30 late in the cycle.
> > > But as you say, it's a very important performance fix for many
> > > machines...
> > > 
> > > Anyway, Eric may already have it merged.  Eric?
> > > 
> > 
> > It's merged now into the drm-intel-next tree, and therefore queued for
> > the merge window.
> 
> <hunts around for a while>
> 
> This? http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commitdiff;h=d765898970f35acef960581f678b9da9d5c779fa;hp=1b8e69662e1a086878bf930a6042daf7f8a076cc
> 
> It doesn't have cc:stable in the changelog, so there's a reasonable
> chance that it will get lost.
> 
> The -stable guys troll the commit list looking for mainline commits
> which mention stable@kernel.org in the changelog.

I got it for the next .30 release.

thanks,

greg k-h

  reply	other threads:[~2009-06-29 17:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A242C81.6020906@cs.helsinki.fi>
     [not found] ` <20090604112738.4c01d35e@jbarnes-x200>
2009-06-05  8:02   ` Intel 915GM MCHBAR bug Pekka Enberg
2009-06-05 20:00     ` Andrew Morton
2009-06-05 21:09       ` Woody Suwalski
2009-06-06  6:14         ` Pekka Enberg
2009-06-06  6:27           ` Andrew Morton
2009-06-06  6:37             ` Pekka Enberg
2009-06-06 20:27               ` Jesse Barnes
2009-06-09 22:07                 ` [Intel-gfx] " Jesse Barnes
2009-06-09 22:28                   ` Andrew Morton
2009-06-29 17:33                     ` Greg KH [this message]
2009-06-29 18:27                       ` [stable] " Greg KH
2009-06-29 18:51                         ` Ozan Çağlayan
2009-06-29 20:45                           ` Greg KH
2009-06-06 22:58               ` Andy Whitcroft

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=20090629173308.GB3901@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=stable@kernel.org \
    --cc=stefan.bader@canonical.com \
    --cc=tim.gardner@canonical.com \
    --cc=torvalds@linux-foundation.org \
    --cc=woodys@xandros.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