public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Williams, Mitch A" <mitch.a.williams@intel.com>
Cc: "Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
	linux-kernel@vger.kernel.org, mingo@redhat.com, "Ronciak,
	John" <john.ronciak@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [PATCH 2.6.20.3] Flush writes to MSI-X table
Date: Fri, 23 Mar 2007 17:30:30 -0700	[thread overview]
Message-ID: <20070324003030.GA18615@suse.de> (raw)
In-Reply-To: <20070324002802.GA18061@suse.de>

On Fri, Mar 23, 2007 at 05:28:02PM -0700, Greg KH wrote:
> On Fri, Mar 23, 2007 at 05:24:23PM -0700, Williams, Mitch A wrote:
> > Greg KH wrote:
> > >Well, I'm sure you can agree that it is _very_ late in the 2.6.21
> > >release cycle to expect to get this in for that kernel.  How about
> > >waiting for 2.6.22 and if it's a big deal, getting it into the
> > >2.6.21-stable tree if needed.
> > >
> > >So far I have not seen any bug reports that this patch would fix, have
> > >you?
> > 
> > Well, I've seen several bug reports on this issue -- but they're all
> > internal to Intel.
> > 
> > However, we do have here a real bug, which shows up on real hardware,
> > which will be released soon.  Obviously, I can't discuss release
> > schedules, but "soon" is a good word to use.  You might find out more if
> > you read The Register (wink, wink).
> 
> Ok, but again, as this is something that no one outside of a company can
> see, it doesn't really make sense to rush it into the kernel.
> 
> > Given the time frame for release of 2.6.21, I'd be fine with skipping
> > 2.6.20.x, and putting this in 2.6.21.  But we really don't want to wait
> > for 2.6.22.
> 
> I think it needs to wait, especially given that there is no public
> hardware yet.
> 
> I'll add this to my queue.

No, nevermind, I'll wait till it hits linux-pci and gets review from the
people there, as there are a _ton_ of other pending MSI patches that you
will need to be aware of, as they might conflict with this patch.
Please see the linux-pci archives for details of them.

thanks,

greg k-h

  reply	other threads:[~2007-03-24  0:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 21:08 [PATCH 2.6.20.3] Flush writes to MSI-X table Mitch Williams
2007-03-23 21:07 ` Greg KH
2007-03-23 21:50   ` Kok, Auke
2007-03-23 22:22     ` Greg KH
2007-03-24  0:24       ` Williams, Mitch A
2007-03-24  0:28         ` Greg KH
2007-03-24  0:30           ` Greg KH [this message]
2007-03-24 23:33             ` Kok, Auke
2007-03-24 23:41               ` Greg KH
2007-03-25  2:00                 ` Roland Dreier

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=20070324003030.GA18615@suse.de \
    --to=gregkh@suse.de \
    --cc=auke-jan.h.kok@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox