linux-kernel - Re: printk(KERN_x...) vs dev

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]

Date:	Fri, 21 Jan 2011 08:55:26 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Sutharshan Ramamoorthy / Prod" <srmt@...ress.com>
Cc:	kernelnewbies@...linux.org, linux-kernel@...r.kernel.org,
	odc@...ress.com
Subject: Re: printk(KERN_x...) vs dev_x()

> At some places in the code, there is no valid 'dev' pointer to pass to
> dev_xx() macro, at such places is it ok to use printk(KERN_XXX...)?

pr_debug() is the equivalent you want. Ideally tweak the code so the dev
pointer is available. I know that right now is a bit of a problem in a
few cases (some tty stuff for example only just acquired a usable dev
pointer)

Alan
			-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/