netdev - Re: [PATCH net-next 00/10] tipc: last batch from the sourceforge queue

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]

Date:	Mon, 30 Apr 2012 21:45:06 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	paul.gortmaker@...driver.com
Cc:	netdev@...r.kernel.org, allan.stephens@...driver.com,
	jon.maloy@...csson.com, erik.hugne@...csson.com,
	ying.xue@...driver.com
Subject: Re: [PATCH net-next 00/10] tipc: last batch from the sourceforge
 queue

From: Paul Gortmaker <paul.gortmaker@...driver.com>
Date: Mon, 30 Apr 2012 18:36:58 -0400

> I'm glad to say this represents the last batch of salvaged commits
> from what was the sourceforge queue of stuff misplaced on the older
> v2.6.19/v1.7.x baseline.  Going forward, folks got a clear message
> that they _must_ put forward any new/prospective changes on netdev
> for peer review and ask for continuous integration and not stockpile
> crap in a corner (cause I'm sure as hell not going to volunteer to
> be Winston Wolf for it again).
> 
> Anyway, knowing that there isn't any more "old" patches from that to
> worry about, I took the opportunity to close out by clobbering a bunch
> of needless extra blank lines following comments, since there isn't
> any pending patch context fallout to worry about.  This one cosmetic
> change alone makes up most of the diffstat, giving:
> 
>  32 files changed, 16 insertions(+), 530 deletions(-)
> 
> out of the total:
> 
>  34 files changed, 58 insertions(+), 567 deletions(-)

You must feel like you've just moved a mountain, Mr. Wolf.

> That aside, the meat of what is here is:
> 
>   -reduce some of the build up/tear down on configuration paths
> 
>   -more strict checks on published names and payload types
> 
>   -factor out some duplicated code;  +some redundant code deletion.
> 
> Testing has been the usual 64 <---> 32bit using tipc-utils ptts.
> 
> I still want to look at your suggestion of reusing existing code
> for the logging stuff someday, now that the queue is closed out,
> but that is completely separate from the backlog, and it probably
> isn't going to be happening in the 3.5 timeframe.

Pulled, thanks.
--
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