Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762132AbYA1W4B (ORCPT ); Mon, 28 Jan 2008 17:56:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759844AbYA1Wzo (ORCPT ); Mon, 28 Jan 2008 17:55:44 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:54035 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756431AbYA1Wzn (ORCPT ); Mon, 28 Jan 2008 17:55:43 -0500 Date: Mon, 28 Jan 2008 14:53:34 -0800 From: Greg KH To: Matthew Wilcox Cc: Tony Camuso , Grant Grundler , Loic Prylli , Adrian Bunk , Linus Torvalds , Arjan van de Ven , Benjamin Herrenschmidt , Ivan Kokshaysky , Greg KH , linux-kernel@vger.kernel.org, Jeff Garzik , linux-pci@atrey.karlin.mff.cuni.cz, Martin Mares Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in Message-ID: <20080128225334.GD4720@kroah.com> References: <20080113090108.3224698c@laptopd505.fenrus.org> <20080114225225.GQ18741@parisc-linux.org> <20080114230448.GL9847@does.not.exist> <478CD8A5.5090608@myri.com> <20080115174643.GB28238@kroah.com> <20080115175641.GE18741@parisc-linux.org> <20080119165809.GB11553@colo.lackof.org> <479E1FA6.1030708@redhat.com> <20080128204431.GA15227@kroah.com> <20080128223141.GA31101@parisc-linux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080128223141.GA31101@parisc-linux.org> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2133 Lines: 46 On Mon, Jan 28, 2008 at 03:31:42PM -0700, Matthew Wilcox wrote: > On Mon, Jan 28, 2008 at 12:44:31PM -0800, Greg KH wrote: > > On Mon, Jan 28, 2008 at 01:32:06PM -0500, Tony Camuso wrote: > > > Greg, > > > > > > Have you given Grant's suggestion any further consideration? > > > > > > I'd like to know how the MMCONFIG issues discussed in this thread are going > > > to be handled upstream. I have a patch implemented in RHEL 5.2, but I would > > > rather have the upstream patch implemented, whatever it is. > > > > Well, everyone still doesn't seem to agree on the proper way forward > > here, so for me to just "pick one" isn't very appropriate. > > > > So, can we try again? > > > > Can people submit, what they think the change should be? Right now I > > have Arjan's patch in my kernel tree, but will not send it to Linus for > > .25 for now, unless everyone thinks that is the best solution at the > > moment (which, for me, I'm leaning toward right now...) > > My opinion is that Ivan's patch followed by my patch is the best way > forward. I see Arjan's patch as a good prototype, but it introduces a lot > of unnecessary infrastructure (and a userspace interface that I dislike). > > I would like to see Ivan's patch merged ASAP as it does fix one of > my machines. akpm has the patch from me to disable io decoding, and > intends to send it to Linus during this merge window ... that patch > becomes unnecessary if we merge Ivan's patch. > > My patch is an incremental improvement that adds some of the features > of Arjan's patch without the extra infrastructure. I don't think it's > urgent, but it does make some of our internal interfaces cleaner. Please send me patches, in a form that can be merged, along with a proper changelog entry, in the order in which you wish them to be applied, so I know exactly what changes you are referring to. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/