netdev - Re: [PATCH net-next] r8169: use standard debug output functions

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: <20180630.204555.2203105561774707639.davem@davemloft.net>
Date:   Sat, 30 Jun 2018 20:45:55 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     hkallweit1@...il.com
Cc:     nic_swsd@...ltek.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] r8169: use standard debug output functions

From: Heiner Kallweit <hkallweit1@...il.com>
Date: Thu, 28 Jun 2018 20:36:15 +0200

> I see no need to define a private debug output symbol, let's use the
> standard debug output functions instead. In this context also remove
> the deprecated PFX define.
> 
> The one assertion is wrong IMO anyway, this code path is used also
> by chip version 01.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@...il.com>

Applied.