public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sutharshan Ramamoorthy / Prod" <srmt@cypress.com>
To: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Cc: odc@cypress.com
Subject: printk(KERN_x...) vs dev_x()
Date: Thu, 20 Jan 2011 22:38:12 -0800	[thread overview]
Message-ID: <20110121062844.M9817@cypress.com> (raw)

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


             reply	other threads:[~2011-01-21  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  6:38 Sutharshan Ramamoorthy / Prod [this message]
2011-01-21  8:55 ` printk(KERN_x...) vs dev_x() Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110121062844.M9817@cypress.com \
    --to=srmt@cypress.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=odc@cypress.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox