All of lore.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 14:56:50 +0000	[thread overview]
Message-ID: <1255013810.4187.34.camel@mulgrave.site> (raw)
In-Reply-To: <alpine.LFD.2.01.0910080736490.3432@localhost.localdomain>

On Thu, 2009-10-08 at 07:39 -0700, Linus Torvalds wrote:
> 
> On Thu, 8 Oct 2009, James Bottomley wrote:
> > 
> > So what do you want to do about this? 
> 
> I'm taking it (and the parisc one I was also unhappy with), but I'm a bit 
> grumpy as usual. The parisc pull came totally outside the merge window, 
> and the SCSI fix pull is technically perfectly fine, but what makes me 
> grumpy is that I get the strong feeling that people aren't even _trying_ 
> to hit the merge window with new drivers, because they decide that they 
> instead can just push them any time.

OK, so we still have a bit of a mismatch here.  I *do* tell people who
come to SCSI with new drivers that for the *first* submission they don't
need to worry about the merge window because of the new driver
exception.  This allows us to clean them up ready for going in without
the submitter feeling huge pressure to hit the merge window rather than
concentrating on code quality and what we need to make a technically
correct submission.

I think this is the correct thing to do for new drivers (which often
come with new writers) because training people to hit the merge window
is often long an painful (when I say not yet to their important driver
enhancements) ... starting people off with the carrot is better than the
stick.

> So I don't think I necessarily want to change the "new driver" policy per 
> se, but I want people to see the merge window as the _primary_ time you 
> get any new code in. The "yes, we'll take new drivers" thing should be the 
> exception rather than the rule. It doesn't seem to be an exception.

Like I said, this will be my fourth new driver under the exception in
the whole year it's been going.  On the other hand, I do have pm8001
still going ... it just got resubmitted after another round of fixes.
If it's ready for the next rc submissions round, it will be my fifth ...

James



      parent reply	other threads:[~2009-10-08 14:57 UTC|newest]

Thread overview: 46+ 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
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
2009-10-12 23:24                                   ` Greg KH
2009-10-12 23:24                                     ` Greg KH
2009-10-13 18:08                                     ` Luis R. Rodriguez
2009-10-13 18:08                                       ` Luis R. Rodriguez
2009-10-14  4:45                                       ` Greg KH
2009-10-14  5:19                                         ` Joe Perches
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
2009-10-12 15:43                                 ` James Bottomley
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 [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=1255013810.4187.34.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.