From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: James.Bottomley@hansenpartnership.com,
Christoph Hellwig <hch@lst.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
David Milburn <dmilburn@redhat.com>,
Ed Ciechanowski <ed.ciechanowski@intel.com>,
Ed Nadolski <edmund.nadolski@intel.com>,
Jacek Danecki <jacek.danecki@intel.com>,
Jeff Skirvin <jeffrey.d.skirvin@intel.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [GIT PULL] isci merge candidate
Date: Fri, 13 May 2011 13:34:20 -0700 [thread overview]
Message-ID: <BANLkTim3igaB8XXQkDY6GEutWfbK-o840A@mail.gmail.com> (raw)
In-Reply-To: <1305317680.21099.83.camel@dwillia2-linux>
On Fri, May 13, 2011 at 1:14 PM, Dan Williams <dan.j.williams@intel.com> wrote:
>
> [ Linus, only cc'ing you in case a new-driver merge exception can be
> entertained at this very late date. James made clear he needed this in
> advance of rc7, and this still needs Christoph's ack, but I would be
> remiss not to send this after reaching this milestone...]
So I can merge new drivers at any stage in the development cycle, but
I only do that for drivers with mass appeal.
What's the likely user base of this? Why is it a SCSI driver rather
than SATA? Why is it so f&*%ing big?
The size may be a massive improvement over what it has been, but if
this is some kind of replacement for the current AHCI situation, it's
still a massive step backwards.
So what does that mean in practical terms:
"This driver supports the 6Gb/s SAS/SATA capabilities of the upcoming
Intel(R) C600 series chipset family"
exactly? What's the market for that C600 series? Does that chipset
also do some AHCI emulation capability (making this driver be a "if
you need full capabilties thing" etc) Yadda yadda.
I don't want to merge 30k lines of driver that nobody will practically
speaking actually use.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-13 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:14 [GIT PULL] isci merge candidate Dan Williams
2011-05-13 20:34 ` Linus Torvalds [this message]
2011-05-13 21:45 ` Dan Williams
2011-05-13 22:16 ` Benjamin Herrenschmidt
2011-05-17 0:39 ` Dan Williams
2011-05-17 0:47 ` Jeff Garzik
2011-05-17 3:41 ` Douglas Gilbert
2011-05-13 21:46 ` Jeff Garzik
2011-05-14 8:49 ` Christoph Hellwig
2011-05-17 3:56 ` James Bottomley
2011-05-17 22:11 ` Dan Williams
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=BANLkTim3igaB8XXQkDY6GEutWfbK-o840A@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=hch@lst.de \
--cc=jacek.danecki@intel.com \
--cc=jeff@garzik.org \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).