public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SCSI fixes for 2.6.32-rc3
Date: Thu, 08 Oct 2009 19:48:18 +0000	[thread overview]
Message-ID: <1255031298.4187.260.camel@mulgrave.site> (raw)
In-Reply-To: <alpine.LFD.2.01.0910080742230.3432@localhost.localdomain>

On Thu, 2009-10-08 at 07:54 -0700, Linus Torvalds wrote:
> 
> On Thu, 8 Oct 2009, Linus Torvalds wrote:
> > 
> > I'm taking it (and the parisc one I was also unhappy with)
> 
> Actually, looking at it again, I'm wavering.
> 
> That BFA driver isn't a "driver". It's a huge subsystem of it's own. It's 
> almost 50 _thousand_ lines of code for just a single "driver", and for 
> rare hardware at that.

It's a huge glue layer driver, like the aic7xxx, yes.

So the tradeoff here is that I estimate it would take years to get it to
where a linux driver should be.

Could I remind you that at the last kernel summit I was the one
advocating for holding drivers out of tree until they met our standards
and you were the one who told me not to do this ... Jon even captured
it:

https://lwn.net/Articles/298570/

I'll certainly offer this driver to Greg's drivers project to see if
they can unglue it ... I just think it's going to take a while.

> Quite frankly, the "bang per line" is almost zero. 
> 
> What the ^&@* is wrong with "enterprise SCSI" people? The amount of crazy 
> is overwhelming.
> 
> So I've pulled it, but I'm still considering just unpulling it. That 
> driver is _not_ "just a driver".  It's something more. Something dank and 
> smelly, that has grown in dark and forbidding places.
> 
> The whole crazy "high end SCSI" industry needs a f*cking exorcism.
> 
> Even if I don't unpull, I don't _ever_ want to see a driver like this 
> outside the merge window. And dammit, James, you should have realized 
> that.

Well certainly in an ideal world ... and in fact the world before KS2008
I wouldn't have accepted it until it was well cleaned up.

James



  reply	other threads:[~2009-10-08 19:49 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 15:46 [GIT PULL] SCSI fixes for 2.6.32-rc3 James Bottomley
2009-10-06 15:58 ` Linus Torvalds
2009-10-06 20:54   ` James Bottomley
2009-10-06 20:56     ` Randy Dunlap
2009-10-08 14:33     ` James Bottomley
2009-10-08 14:39       ` Linus Torvalds
2009-10-08 14:54         ` Linus Torvalds
2009-10-08 19:48           ` James Bottomley [this message]
2009-10-08 19:55             ` Linus Torvalds
2009-10-08 20:00               ` Linus Torvalds
2009-10-08 21:07                 ` Theodore Tso
2009-10-08 21:13                   ` Linus Torvalds
2009-10-09  9:15                     ` Ingo Molnar
2009-10-09 13:10                       ` Daniel Walker
2009-10-09 14:08                       ` James Bottomley
2009-10-09 19:25                         ` Greg KH
2009-10-12 13:06                         ` Ingo Molnar
2009-10-12 14:19                           ` James Bottomley
2009-10-12 14:54                             ` Ingo Molnar
2009-10-12 15:09                               ` Moving drivers into staging (was Re: [GIT PULL] SCSI fixes for 2.6.32-rc3) Greg KH
2009-10-12 15:42                                 ` Ingo Molnar
     [not found]                                   ` <20091012154244.GA13323-X9Un+BFzKDI@public.gmane.org>
2009-10-12 23:24                                     ` Greg KH
2009-10-13 18:08                                       ` Luis R. Rodriguez
2009-10-14  4:45                                         ` Greg KH
     [not found]                                           ` <20091014044519.GA19199-l3A5Bk7waGM@public.gmane.org>
2009-10-14  5:19                                             ` Joe Perches
2009-10-14  6:33                                               ` Ingo Molnar
2009-10-14 14:13                                                 ` James Smart
2009-10-14 17:52                                                 ` Stefan Richter
2009-10-14 18:36                                                   ` Ingo Molnar
2009-10-14 19:00                                                     ` Stefan Richter
2009-10-15  6:03                                                       ` Ingo Molnar
2009-10-14 19:11                                                 ` Greg KH
     [not found]                                 ` <20091012150911.GB1656-l3A5Bk7waGM@public.gmane.org>
2009-10-12 15:43                                   ` James Bottomley
2009-10-12 23:26                                     ` Greg KH
2009-10-12 15:25                               ` [GIT PULL] SCSI fixes for 2.6.32-rc3 James Bottomley
2009-10-12 17:24                                 ` Linus Torvalds
2009-10-13 14:29                                   ` James Bottomley
2009-10-12 14:25                           ` Greg KH
2009-10-08 20:04               ` James Bottomley
2009-10-08 20:25                 ` Linus Torvalds
2009-10-10 14:37                   ` James Bottomley
2009-10-08 14:56         ` James Bottomley

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=1255031298.4187.260.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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