Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754753AbZJZSxv (ORCPT ); Mon, 26 Oct 2009 14:53:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754691AbZJZSxt (ORCPT ); Mon, 26 Oct 2009 14:53:49 -0400 Received: from cantor.suse.de ([195.135.220.2]:43470 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754468AbZJZSxs (ORCPT ); Mon, 26 Oct 2009 14:53:48 -0400 Date: Mon, 26 Oct 2009 11:47:34 -0700 From: Greg KH To: david@lang.hm Cc: "John W. Linville" , Pavel Machek , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] strip: move driver to staging Message-ID: <20091026184734.GA21591@suse.de> References: <1256015830-12700-1-git-send-email-linville@tuxdriver.com> <20091023161006.GA1580@ucw.cz> <20091026165518.GE2792@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 818 Lines: 20 On Mon, Oct 26, 2009 at 10:18:20AM -0700, david@lang.hm wrote: > if someone were to claim 'maintainership' and then do nothing other than > complain if someone else were to change an API but not fix this in the > process, how would this be different than the current situation? A person "claiming maintainership" would then be responsible for keeping the API up to date and ensuring that the driver worked. To do that, hardware would probably need to be present. Do you have this kind of hardware and are willing to accept ownership of this driver? 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/