From: Joe Perches <joe@perches.com>
To: Neshama Parhoti <pneshama@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pr_* versus dev_*
Date: Tue, 30 Mar 2010 22:48:19 -0700 [thread overview]
Message-ID: <1270014499.14822.1.camel@Joe-Laptop.home> (raw)
In-Reply-To: <u2y912ec82a1003302242sb4f1ac2arb9c464d35993b7a1@mail.gmail.com>
On Wed, 2010-03-31 at 08:42 +0300, Neshama Parhoti wrote:
> so i should use whatever print call that adds most information right ?
I think so.
> even if that means that some part of the driver uses pr_* and some
> part of the driver use dev_* ?
Yes.
next prev parent reply other threads:[~2010-03-31 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:07 Neshama Parhoti
2010-03-30 16:52 ` Joe Perches
2010-03-31 5:42 ` Neshama Parhoti
2010-03-31 5:48 ` Joe Perches [this message]
2010-03-31 5:57 ` Neshama Parhoti
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=1270014499.14822.1.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pneshama@gmail.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
all inboxes | Powered by JetHome®