From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [GIT PATCH] STAGING fixes and new drivers for 2.6.35-git
Date: Fri, 4 Jun 2010 19:40:38 -0700 [thread overview]
Message-ID: <20100605024038.GA13792@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1006041528291.8175@i5.linux-foundation.org>
On Fri, Jun 04, 2010 at 03:30:40PM -0700, Linus Torvalds wrote:
>
>
> On Fri, 4 Jun 2010, Greg KH wrote:
> >
> > Here are a number of bugfixes for the drivers/staging tree, as well as 3
> > new stand-alone drivers. The new drivers kind of obscure the diffstat
> > showing the other fixes due to their size.
>
> I pulled, but quite frankly, I don't want to see this kind of pull request
> again. There's just no _point_.
>
> I'll take new drivers outside the merge window, but there has to be some
> _reason_ for them. See the whole SCSI discussion a few merge windows ago.
> The new driver needs to improve the life of somebody to the point where I
> want to feel that there is a _reason_ for pulling it outside the merge
> window.
Fair enough, I shouldn't have added them to the request this time,
sorry.
> These drivers? Not so much. Not even f*cking close.
>
> In other words: tell me why the new drivers couldn't just have waited for
> the next merge window? Really?
They could have, sorry, will not do it again.
greg k-h
prev parent reply other threads:[~2010-06-05 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 20:44 [GIT PATCH] STAGING fixes and new drivers for 2.6.35-git Greg KH
2010-06-04 20:48 ` Mike Frysinger
2010-06-04 21:03 ` Greg KH
2010-06-04 21:05 ` Mike Frysinger
2010-06-04 22:30 ` Linus Torvalds
2010-06-05 2:40 ` 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=20100605024038.GA13792@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@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.