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: <f85455c2-9f78-c1e2-8570-84eb70baee23@redfish-solutions.com>
Date:	Thu, 18 Aug 2016 08:17:05 -0600
From:	Philp Prindeville <philipp@...fish-solutions.com>
To:	fgao@...vckh6395k16k5.yundunddos.com, mostrows@...thlink.net,
	jchapman@...alix.com, davem@...emloft.net, netdev@...r.kernel.org
Cc:	gfree.wind@...il.com
Subject: Re: [PATCH v1 1/1] pppoe: l2tp: the PPPOX_CONNECTED should be used
 with bit operation

Reviewed-by: Philip Prindeville <philipp@...fish-solutions.com>


On 08/17/2016 07:59 PM, fgao@...vckh6395k16k5.yundunddos.com wrote:
> From: Gao Feng<fgao@...ai8.com>
>
> There are some codes in pppoe and l2tp which use the PPPOX_CONNECTED
> as the value including assignment and condition check.
> They should keep consistent with other codes.
>
> Signed-off-by: Gao Feng<fgao@...ai8.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ