LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Michael Ellerman <michael@ellerman.id.au>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 0/3] Basic msi bug fixes..
Date: Fri, 2 Mar 2007 12:52:40 -0800	[thread overview]
Message-ID: <20070302205240.GB24716@kroah.com> (raw)
In-Reply-To: <m1tzx7l7z2.fsf@ebiederm.dsl.xmission.com>

On Tue, Feb 27, 2007 at 12:24:17PM -0700, Eric W. Biederman wrote:
> 
> While looking at some other irq issues I realized that the current msi code
> has a serious issue in that we don't have support for masking msi interrupts
> on all variations of the msi capabilities.
> 
> Closing that hole is simple, but it requires the msi enable/disable
> logic to be sorted out. Which is a little more complicated...
> 
> These are moderately simples fixes so the should be safe for 2.6.21.

Unless these fix a reported bug, I'd like to hold on to these and wait
for 2.6.22 so they get some testing in a few -mm releases.

thanks,

greg k-h

      parent reply	other threads:[~2007-03-02 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 19:24 Eric W. Biederman
2007-02-27 19:28 ` [PATCH 1/3] msi: Sanely support hardware level msi disabling Eric W. Biederman
2007-02-27 19:31   ` [PATCH 2/3] msi: Fixup the msi enable/disable logic Eric W. Biederman
2007-02-27 19:33     ` [PATCH 3/3] msi: Support masking msi irqs without a mask bit Eric W. Biederman
2007-03-02  2:26     ` [PATCH 2/3] msi: Fixup the msi enable/disable logic Michael Ellerman
2007-03-07  5:19       ` Eric W. Biederman
2007-03-07  8:51         ` Michael Ellerman
2007-03-02 20:52 ` 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=20070302205240.GB24716@kroah.com \
    --to=greg@kroah.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=michael@ellerman.id.au \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [PATCH 0/3] Basic msi bug fixes..' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).