All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mitch Williams <mitch.a.williams@intel.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, auke-jan.h.kok@intel.com
Subject: Re: [PATCH 2.6.20.4] Flush MSI-X table writes (rev 3)
Date: Fri, 30 Mar 2007 12:48:54 -0700	[thread overview]
Message-ID: <20070330194854.GA7857@suse.de> (raw)
In-Reply-To: <m1ejn6il0m.fsf@ebiederm.dsl.xmission.com>

On Fri, Mar 30, 2007 at 01:33:45PM -0600, Eric W. Biederman wrote:
> Greg KH <gregkh@suse.de> writes:
> >
> > Sorry, but this isn't going to go into 2.6.20 any time soon as it
> > doesn't fit the rules for the -stable tree.
> >
> > But I'll take an updated version for my pci tree to go to Linus after
> > 2.6.21 is out.
> 
> Greg this does fix a bug that affects 2.6.21.  We have hardware in 2.6.21 that
> is affected And it at least seems to meet the obviously correct
> criteria.  So at least for 2.6.21 I think it is interesting.

We do?  What hardware has this reported problem showed up on?  I haven't
seen any bug reports yet.

And I think it's way too late for something like this.  If it's really
needed, I don't have a problem adding it to the 2.6.21-stable tree in a
few weeks.

thanks,

greg k-h

      reply	other threads:[~2007-03-30 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 19:03 [PATCH 2.6.20.4] Flush MSI-X table writes (rev 3) Mitch Williams
2007-03-30 19:09 ` Greg KH
2007-03-30 19:12   ` Greg KH
2007-03-30 19:33   ` Eric W. Biederman
2007-03-30 19:48     ` 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=20070330194854.GA7857@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mitch.a.williams@intel.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.