linux-kernel - Re: [PATCH 1/4] strip: move driver to staging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091026184734.GA21591@suse.de>
Date:	Mon, 26 Oct 2009 11:47:34 -0700
From:	Greg KH <gregkh@...e.de>
To:	david@...g.hm
Cc:	"John W. Linville" <linville@...driver.com>,
	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] strip: move driver to staging

On Mon, Oct 26, 2009 at 10:18:20AM -0700, david@...g.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/