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-next>] [day] [month] [year] [list]
Message-Id: <20110121062844.M9817@cypress.com>
Date:	Thu, 20 Jan 2011 22:38:12 -0800
From:	"Sutharshan Ramamoorthy / Prod" <srmt@...ress.com>
To:	kernelnewbies@...linux.org, linux-kernel@...r.kernel.org
Cc:	odc@...ress.com
Subject: printk(KERN_x...) vs dev_x()

Hi,

I'm submitting patches to linux kernel.
I'd like to know, Which is the acceptable practice to print debug messages?

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...)?

Please let me know correct format of print messages.

Thanks,
Sutharsan.

---------------------------------------------------------------
This message and any attachments may contain Cypress (or its
subsidiaries) confidential information. If it has been received
in error, please advise the sender and immediately delete this
message.
---------------------------------------------------------------

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ