netdev - Re: [PATCH] dp83640: Always decode received status frames

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, 8 Jul 2014 06:39:52 +0000
From:	Sørensen, Stefan 
	<Stefan.Sorensen@...ctralink.com>
To:	"davem@...emloft.net" <davem@...emloft.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"richardcochran@...il.com" <richardcochran@...il.com>
Subject: Re: [PATCH] dp83640: Always decode received status frames

On Wed, 2014-06-25 at 14:40 +0200, Stefan Sørensen wrote:
> Currently status frames are only handled when packet timestamping is
> enabled, but status frames are also needed for pin event timestamping.
> 
> Fix by moving packet timestamping check to after status frame decode.
> 
> Signed-off-by: Stefan Sørensen <stefan.sorensen@...ctralink.com>

Dave, I have noticed that this patch is marked as superseded in
patchworks (http://patchwork.ozlabs.org/patch/363989/), though I have
not posted any updated patch and only response is an Acked-By from
Richard.

Stefan