All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Remove BKL from PCI syscalls
Date: Wed, 11 Jul 2007 00:30:01 +0000	[thread overview]
Message-ID: <20070711003001.GA30585@kroah.com> (raw)
In-Reply-To: <20070710165532.GP9704@parisc-linux.org>

On Tue, Jul 10, 2007 at 06:16:14PM -0600, Matthew Wilcox wrote:
> On Tue, Jul 10, 2007 at 04:49:36PM -0700, Greg KH wrote:
> > On Tue, Jul 10, 2007 at 05:42:18PM -0600, Matthew Wilcox wrote:
> > > I believe my patch to be a superset of this one, and recommend just
> > > dropping Alan's patch.
> > 
> > How about just doing your patch on top of Alan's instead?
> 
> Seems like a lot more work; wasn't the point of keeping patches in a git
> tree like this to make it easy to drop old patches?  I'd understand if
> it meant pulling apart and rebasing a git tree.

Well, it depends.  Alan's patch fixes up the api to do the proper thing
now, and your patch builds on that showing that we can now just drop the
BKL safely.  They are two different things in a way as is shown by the
fact that two different people approached this differently :)

Also, Alan's patch has already gotten a lot of testing in -mm for a
while and is about to be sent to Linus, while your's would be a bit
further back in the queue.

thanks,

greg k-h

  parent reply	other threads:[~2007-07-11  0:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 16:55 [PATCH] Remove BKL from PCI syscalls Matthew Wilcox
2007-07-10 23:14 ` Greg KH
2007-07-10 23:36 ` Matthew Wilcox
2007-07-10 23:42 ` Matthew Wilcox
2007-07-10 23:49 ` Greg KH
2007-07-11  0:16 ` Matthew Wilcox
2007-07-11  0:30 ` Greg KH [this message]
2007-07-11 20:20 ` Matthew Wilcox
2007-07-11 20:59 ` Greg KH
2007-07-13 10:35 ` Alan Cox
2007-07-19 19:05 ` Matthew Wilcox
2007-07-19 23:22 ` Alan Cox

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=20070711003001.GA30585@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@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 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.