From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1
Date: Wed, 11 Feb 2009 07:42:19 -0500 [thread overview]
Message-ID: <1234356139.3295.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20090211040806.GQ31509@parisc-linux.org>
On Tue, 2009-02-10 at 21:08 -0700, Matthew Wilcox wrote:
> On Sat, Jan 17, 2009 at 02:17:23PM -0700, Matthew Wilcox wrote:
> > On Fri, Jan 16, 2009 at 09:56:11AM -0500, James Bottomley wrote:
> > > mpt fusion: Add separate msi enable disable for FC,SPI,SAS
> >
> > I thought we rejected this one as being completely bogus? I certainly
> > don't remember seeing even an excuse for it after I challenged it.
>
> ... no response?
>From whom? It's no less bogus than what they were doing previously. I
happen to think the whole idea of drivers chosing msi/not msi by
parameters is bogus ... we just don't have a good platform way of
sorting it out at the moment. In that absence, the driver maintainer
gets to fix up.
James
prev parent reply other threads:[~2009-02-11 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:56 [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1 James Bottomley
2009-01-16 17:09 ` Andrew Morton
2009-01-16 18:48 ` James Bottomley
2009-01-16 19:07 ` Andrew Morton
2009-01-16 20:28 ` James Bottomley
2009-01-16 19:09 ` David Miller
2009-01-16 19:02 ` Grant Grundler
2009-01-16 19:10 ` David Miller
2009-01-16 20:09 ` Grant Grundler
2009-01-16 20:15 ` James Bottomley
2009-01-17 21:17 ` Matthew Wilcox
2009-02-11 4:08 ` Matthew Wilcox
2009-02-11 12:42 ` James Bottomley [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=1234356139.3295.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox