netdev - Re: [PATCH v2 net-next 2/2] tipc: add name distributor resiliency 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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Aug 2014 16:48:16 +0200
From:	Erik Hugne <erik.hugne@...csson.com>
To:	Jon Maloy <jon.maloy@...csson.com>
CC:	"ying.xue@...driver.com" <ying.xue@...driver.com>,
	Richard Alpe <richard.alpe@...csson.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"tipc-discussion@...ts.sourceforge.net" 
	<tipc-discussion@...ts.sourceforge.net>
Subject: Re: [PATCH v2 net-next 2/2] tipc: add name distributor resiliency
 queue

On Tue, Aug 26, 2014 at 04:44:34PM +0200, Jon Maloy wrote:
> (netdev removed from receiver list)
> 
> > -----Original Message-----
> > From: Erik Hugne
> > Sent: August-26-14 10:33 AM
> > To: Jon Maloy; ying.xue@...driver.com; Richard Alpe;
> > netdev@...r.kernel.org
> > Cc: tipc-discussion@...ts.sourceforge.net
> > Subject: Re: [PATCH v2 net-next 2/2] tipc: add name distributor resiliency
> > queue
> > 
> > if (e->expiry > now) should in fact be
> > if (time_after(e->expiry, now) to handle timer wraps correctly.
> > 
> > Thanks Niklas Söderlund for pointing this out.
> > 
> > v2 removed from patchwork
> > 
> > //E
> 
> Also, don't use the version label an comment when you send this
> to David. This has only relevance to us who are reviewing the
> series. (I assume it was  a mistake)

No, this is in the general guidelines for submitting patches section 15.
https://www.kernel.org/doc/Documentation/SubmittingPatches

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