From: Michael Ellerman <mpe@ellerman.id.au>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-geode@lists.infradead.org,
Matt Mackall <mpm@selenic.com>, Olof Johansson <olof@lixom.net>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] drivers: char: hw_random: printk replacement
Date: Fri, 29 Aug 2014 17:04:47 +1000 [thread overview]
Message-ID: <1409295887.9191.6.camel@concordia> (raw)
In-Reply-To: <1409238178-16496-1-git-send-email-sudipm.mukherjee@gmail.com>
On Thu, 2014-08-28 at 20:32 +0530, Sudip Mukherjee wrote:
> as pr_* macros are more preffered over printk, so printk replaced with corresponding pr_* macros
I suppose ...
> drivers/char/hw_random/pasemi-rng.c | 2 +-
> drivers/char/hw_random/pseries-rng.c | 2 +-
These look OK to me.
cheers
next prev parent reply other threads:[~2014-08-29 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 15:02 [PATCH] drivers: char: hw_random: printk replacement Sudip Mukherjee
2014-08-29 7:04 ` Michael Ellerman [this message]
2014-09-08 8:43 ` Sudip Mukherjee
2014-09-15 11:41 ` Herbert Xu
2014-09-15 12:03 ` Sudip Mukherjee
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=1409295887.9191.6.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=herbert@gondor.apana.org.au \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpm@selenic.com \
--cc=olof@lixom.net \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).