From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: wireless (was Re: 2.6.18 -mm merge plans) Date: Mon, 05 Jun 2006 15:42:04 +0200 Message-ID: <1149514924.3111.72.camel@laptopd505.fenrus.org> References: <20060604135011.decdc7c9.akpm@osdl.org> <20060605010636.GB17361@havoc.gtf.org> <20060605085451.GA26766@infradead.org> <20060605132732.GA23350@tuxdriver.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , Jeff Garzik , Andrew Morton , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:27044 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1751097AbWFENmL (ORCPT ); Mon, 5 Jun 2006 09:42:11 -0400 To: "John W. Linville" In-Reply-To: <20060605132732.GA23350@tuxdriver.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > Of course, I didn't know there were serious concerns about this > driver's origin. I hope we aren't confusing this with the atheros > driver...? > > > Please don't let this reverse engineering idiocy hinder wireless driver > > adoption, we're already falling far behind openbsd who are very successfull > > reverse engineering lots of wireless chipsets. > > This bugbear does seem to keep visiting us. It is a bit of a > minefield. > > I'm inclined to think that Christoph and Arjan are right, that we > have been too cautious. Of course, neither of these fine gentlemen > are known for their timidity... :-) > > Does not the Signed-off-by: line on a patch submission give us some > level of "good faith" protection? I would suggest asking them an explicit "did you copy anything" and make sure their "we didn't copy" answer is in the description of the original patch submission. > > I'm tempted to take contributors at their word, that they have produced > their own work and not copied from others. What else do we need? to a large degree that's all you can do. (of course you can look at the code for something that looks "obviously not from here" as well, and we all tend to do that anyway since such stuff tends to highly violate coding style anyway)