netdev - Re: [RFC PATCH v3 linux-next] et131x: Promote staging et131x driver to drivers/net

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: <CANK3SE1W5O5Df95MpCCWHaQO_tN7OaA1jJ60zrH5Zx66ZGdNiw@mail.gmail.com>
Date:	Wed, 23 Jan 2013 14:51:39 +0000
From:	Mark Einon <mark.einon@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	davem@...emloft.net, sfr@...b.auug.org.au,
	devel@...verdev.osuosl.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, dan.carpenter@...cle.com
Subject: Re: [RFC PATCH v3 linux-next] et131x: Promote staging et131x driver
 to drivers/net

On 23 January 2013 14:32, Greg KH <gregkh@...uxfoundation.org> wrote:
> I usually recommend just creating a new patch, that adds the driver to
> the proper place in the kernel, and sending that in.  If the subsystem
> maintainers accept it, then I can just delete the staging driver.
>
> Yes, this looses the history of the code, but usually no one cares about
> that for staging drivers.
>
> If that's not ok, I have no problem accepting this, if I get an ack from
> the subsystem maintainers that it's ok, but again, this patch makes it
> pretty hard for them to know that or not.

I can see how that works - I'll send a v4 update shorty.

Cheers,

Mark
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html