linux-kernel - Re: [PATCH] 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] [day] [month] [year] [list]

Message-ID: <20140930194510.GC1982@msilap.einon.net>
Date:	Tue, 30 Sep 2014 20:45:10 +0100
From:	Mark Einon <mark@...on.net>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Mark Einon <mark.einon@...il.com>, davem@...emloft.net,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH] et131x: Promote staging et131x driver to drivers/net

On Tue, Sep 30, 2014 at 12:32:01PM -0700, Greg KH wrote:
> 
> This is a fine way to make a patch, but it's no way that any of the
> netdev developers could ever review it to know what the code happens to
> look like in my staging-next branch :(
> 
> How about just sending a patch that adds the driver to drivers/net/...
> Don't worry about the staging driver at the moment.  If it gets added to
> drivers/net we can then delete the staging driver.
> 
> Sound easier?  Should make the patches half as big.

Sounds resonable, will do.

Cheers,

Mark
--
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/