linux-kernel - Re: CONFIG_MTD_DEBUG vs generic DEBUG support in kernel.h

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:	Fri, 19 Mar 2010 01:36:22 +0100
From:	Wolfram Sang <w.sang@...gutronix.de>
To:	Ferenc Wagner <wferi@...f.hu>
Cc:	dedekind1@...il.com, linux-mtd@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_MTD_DEBUG vs generic DEBUG support in kernel.h

> something standard as dev_(v)dbg or pr_debug/devel (btw. what's the
> difference?) instead.

pr_devel will never produce code if !DEBUG. For pr_debug, it may be different
as we have DYNAMIC_DEBUG meanwhile (see kernel.h)

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)