linux-kernel - Re: [RFC PATCH 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: <20140923095004.GB5130@leicester.auvation.com>
Date:	Tue, 23 Sep 2014 10:50:04 +0100
From:	Mark Einon <mark.einon@...il.com>
To:	Joe Perches <joe@...ches.com>
Cc:	gregkh@...uxfoundation.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: Re: [RFC PATCH linux-next] et131x: Promote staging et131x driver to
 drivers/net

On Mon, Sep 22, 2014 at 06:57:25PM -0700, Joe Perches wrote:
> On Mon, 2014-09-22 at 22:28 +0100, Mark Einon wrote:
> > This patch moves the et131x gigabit ethernet driver from drivers/staging
> > to drivers/net/ethernet/agere.
> > 
> > There are no known issues at this time.
> 
> This doesn't apply to -next or -linux

Hi Joe,

Thanks for the review.

Yes, there are a further (minor) 8 patches by me on the driver-devel
list that are needed that this patch is based upon, as per my comment
below. As the merge window is close, I've put this out an an RFC to
get feedback ASAP.

> 
> []
> > This patch will only apply once the last few pending changes
> > make their way from staging-next to linux-next, but posting
> > now in the hope that feedback can be given and this change can
> > make it in before the next merge window.n yo
> 
> When you do post the actual patch, can you please use
> "git format-patch -M" so that the patch is significantly
> smaller and the renames are obvious?

Will do, thanks.

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/