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 20:59:27 +0000	[thread overview]
Message-ID: <20070711205927.GA22475@kroah.com> (raw)
In-Reply-To: <20070710165532.GP9704@parisc-linux.org>

On Wed, Jul 11, 2007 at 02:20:54PM -0600, Matthew Wilcox wrote:
> On Tue, Jul 10, 2007 at 05:30:01PM -0700, Greg KH wrote:
> > 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 :)
> 
> I suppose that's one way of looking at it.  It just feels wrong -- git
> is supposed to show how development happened, and I didn't base my patch
> on Alan's.
> 
> It sucks that Alan sent his patch three months ago and it
> still didn't make it into the 2.6.22 release.  It's not even
> controversial.  Indeed, as far as I can tell, it didn't even
> make it into your tree until *after* I'd sent off this patch yesterday!
> http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=commit;hÞ575d18a94e63c681435a16f5c72a3c13dd3345
> is why I think that -- please tell me if I'm confused.

Yes, that is because Alan sent it to Andrew and not me, so it was in the
-mm tree for a while before Andrew sent it on to me.

> > 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.
> 
> How much testing has Alan's patch actually had?

As much testing as any -mm release does :)

> So is there anyone testing -mm on Alpha, and running X?

I do not know, try asking on lkml.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2007-07-11 20:59 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
2007-07-11 20:20 ` Matthew Wilcox
2007-07-11 20:59 ` Greg KH [this message]
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=20070711205927.GA22475@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.