From: Kevin Hilman <khilman@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: Re: omap_device prints
Date: Thu, 21 Jul 2011 07:57:00 -0700 [thread overview]
Message-ID: <87mxg7d6mb.fsf@ti.com> (raw)
In-Reply-To: <20110721095109.GC28942@n2100.arm.linux.org.uk> (Russell King's message of "Thu, 21 Jul 2011 10:51:09 +0100")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> I spotted this while booting the OMAP4430 SDP:
>
> omap_device: omap4-keypad.-1: new worst case activate latency 0: 61035
>
[...]
> Is there something wrong with dev_name(&od->pdev.dev) so that we have
> consistent naming of devices, rather than poking about inside the
> platform_device accessing the name initializers directly ?
I've been meaning to convert most of these from pr_debug() to dev_dbg().
There are a few that have to remain pr_debug() because they are used
before the platform_device (and struct device) are initialized, but most
of them can be converted.
Patch coming shortly.
Kevin
prev parent reply other threads:[~2011-07-21 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 9:51 omap_device prints Russell King - ARM Linux
2011-07-21 9:58 ` Felipe Balbi
2011-07-21 14:57 ` Kevin Hilman [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=87mxg7d6mb.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.