public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: david@lang.hm
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] strip: move driver to staging
Date: Mon, 26 Oct 2009 11:47:34 -0700	[thread overview]
Message-ID: <20091026184734.GA21591@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0910261013430.11504@asgard.lang.hm>

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

  parent reply	other threads:[~2009-10-26 18:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  5:17 [PATCH 1/4] strip: move driver to staging John W. Linville
2009-10-20  5:17 ` [PATCH 2/4] arlan: " John W. Linville
     [not found]   ` <1256015830-12700-3-git-send-email-linville@tuxdriver.com>
2009-10-20  5:17     ` [PATCH 4/4] netwave: " John W. Linville
2009-10-27 20:36       ` Staging: " Greg KH
2009-10-27 21:05         ` John W. Linville
2009-10-27 22:12           ` Greg KH
2009-10-20 16:06 ` [PATCH 1/4] strip: " Randy Dunlap
2009-10-26 16:46   ` John W. Linville
2009-10-26 17:02     ` Randy Dunlap
2009-10-26 18:48       ` Greg KH
2009-10-23 16:10 ` Pavel Machek
2009-10-23 16:54   ` Alan Cox
2009-10-26 16:55   ` John W. Linville
2009-10-26 17:18     ` david
2009-10-26 17:43       ` John W. Linville
2009-10-26 18:47       ` Greg KH [this message]
2009-10-27  4:17         ` david
2009-10-27  5:21           ` David Miller
2009-10-27  8:34           ` Stefan Richter
2009-10-27 14:08           ` Greg KH
2009-10-27 18:39             ` david
2009-10-27 20:38               ` Greg KH
2009-10-27 21:13               ` John W. Linville
2009-10-27 21:32               ` Alan Cox
2009-10-26 17:24     ` Pavel Machek
2009-10-26 17:29       ` Alan Cox
2009-10-26 17:34       ` John W. Linville
2009-10-26 18:48       ` Greg KH
2009-10-26 19:07         ` Joe Perches
2009-10-26 19:17           ` Greg KH
2009-10-26 19:20           ` John W. Linville
2009-10-26 19:36             ` Greg KH
2009-10-26 20:06             ` Joe Perches

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=20091026184734.GA21591@suse.de \
    --to=gregkh@suse.de \
    --cc=david@lang.hm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=pavel@ucw.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox