All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joe Perches <joe@perches.com>
Cc: Valdis.Kletnieks@vt.edu, Greg KH <gregkh@suse.de>,
	devel@driverdev.osuosl.org, Scott Smedley <ss@aao.gov.au>,
	Jason Baldus <jason.baldus@gmail.com>,
	linux-kernel@vger.kernel.org,
	Harley Sweeten <hsweeten@visionengravers.com>,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH 1/3] drivers/staging/dt3155: Integrate 3 badly styled files into 1 clean file
Date: Wed, 28 Apr 2010 10:22:31 -0700	[thread overview]
Message-ID: <20100428172231.GA14343@kroah.com> (raw)
In-Reply-To: <1272472405.18228.16.camel@Joe-Laptop.home>

On Wed, Apr 28, 2010 at 09:33:25AM -0700, Joe Perches wrote:
> On Wed, 2010-04-28 at 12:12 -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 27 Apr 2010 23:00:30 PDT, Joe Perches said:
> > > On Tue, 2010-04-27 at 22:52 -0700, Greg KH wrote:
> > > > > I seem to be learning that you little taste.
> > > > -ENOPARSE
> > > 
> > > Choosing competing patches based on date received
> > > order not quality is poor taste.
> > 
> > So you're saying when Greg gets a somewhat ugly but passable patch 2 weeks ago,
> > he's supposed to *just know* that you'll be submitting a possibly better one 2
> > weeks later and wait for it to show up?
> 
> No, I'm saying that when Greg gets multiple
> patches for the same module and doesn't act on
> any of them for several weeks, (in this case
> one 6 weeks ago, and two others 4 weeks ago)
> he should select the better patches, not just
> apply the first one in chronological order.

In this case, I _did_ select the best patches.  Your "do it all in one
patch" was not acceptable, especially as others sent small,
do-one-thing, type patches.

I'm sorry you don't agree with this decision, but that was my call.

thanks,

greg k-h

  reply	other threads:[~2010-04-28 17:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 15:26 Staging: dt3155: fixed some checkpatch.pl warnings and errors in dt3155_drv.c Olimpiu Pascariu
2010-03-29  3:23 ` Simon Horman
2010-03-29  7:34   ` [PATCH 0/3] drivers/staging/dt3155: Large cleanups Joe Perches
2010-03-29  7:34     ` [PATCH 1/3] drivers/staging/dt3155: Integrate 3 badly styled files into 1 clean file Joe Perches
2010-04-27 23:02       ` Greg KH
2010-04-28  5:30         ` Joe Perches
2010-04-28  5:34           ` Greg KH
2010-04-28  5:44             ` Joe Perches
2010-04-28  5:52               ` Greg KH
2010-04-28  6:00                 ` Joe Perches
2010-04-28 16:12                   ` Valdis.Kletnieks
2010-04-28 16:33                     ` Joe Perches
2010-04-28 17:22                       ` Greg KH [this message]
2010-04-28 12:18         ` Dan Carpenter
2010-03-29  7:34     ` [PATCH 2/3] drivers/staging/dt3155/allocator: sparse cleanups Joe Perches
2010-03-29  7:34     ` [PATCH 3/3] drivers/staging/dt3155: Remove old files Joe Perches
2010-03-29 17:35   ` Staging: dt3155: fixed some checkpatch.pl warnings and errors in dt3155_drv.c Olimpiu Pascariu

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=20100428172231.GA14343@kroah.com \
    --to=greg@kroah.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=horms@verge.net.au \
    --cc=hsweeten@visionengravers.com \
    --cc=jason.baldus@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ss@aao.gov.au \
    /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.