From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/tegra: clk_get should not be fatal
Date: Tue, 25 Oct 2011 18:15:07 -0700 [thread overview]
Message-ID: <1319591707.16994.4.camel@Joe-Laptop> (raw)
In-Reply-To: <20111025170038.GT1001@tbergstrom-lnx.Nvidia.com>
On Tue, 2011-10-25 at 20:00 +0300, Peter De Schrijver wrote:
> Is pr_warn any different then pr_warning?
Other than being 3 characters shorter to type and it also
lets some format strings fit sub 80 chars line length? No.
It is more like dev_warn, netdev_warn, et al.
cheers, Joe
prev parent reply other threads:[~2011-10-26 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 16:15 [PATCH] arm/tegra: clk_get should not be fatal pdeschrijver at nvidia.com
2011-10-25 16:26 ` Joe Perches
2011-10-25 17:00 ` Peter De Schrijver
2011-10-26 1:15 ` Joe Perches [this message]
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=1319591707.16994.4.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).