netdev - Re: respin of __dev* removal patches

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: <20121130.222021.1095074411846638107.davem@davemloft.net>
Date:	Fri, 30 Nov 2012 22:20:21 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	gregkh@...uxfoundation.org
Cc:	wfp5p@...idian.itc.virginia.edu, netdev@...r.kernel.org
Subject: Re: respin of __dev* removal patches

From: Greg KH <gregkh@...uxfoundation.org>
Date: Fri, 30 Nov 2012 15:39:47 -0800

> On Fri, Nov 30, 2012 at 05:15:54PM -0500, Bill Pemberton wrote:
>> I've got a respin of the hotplug removal patches for the networking
>> subsystem.  I don't want to irritate you like the big patch set did,
>> so before I submit them, what do you want to see that will keep your
>> pain to a minimum?
>> 
>> I've redone them so that all the __dev* removals are done at once so
>> there won't be one patch for __devinit, one for __devexit, etc.  I've
>> also broken them down into chunks following what's in the MAINTAINERS
>> file.  The result is 103 patches.
> 
> As that's a lot of patches to handle through patchwork, would it be
> easier for the network maintainers for me to just put these in a tree
> they can pull from?  I will base it off of net-next.

That might work.
--
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