From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 RESEND] OMAP2+: pm: fix typos
Date: Tue, 30 Aug 2011 18:48:16 +0200 [thread overview]
Message-ID: <1314722897-25040-1-git-send-email-jhovold@gmail.com> (raw)
In-Reply-To: <87r543rkdk.fsf@ti.com>
Fix typos in comment and error message.
Signed-off-by: Johan Hovold <jhovold@gmail.com>
---
arch/arm/mach-omap2/pm.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
index 3feb359..fd77cf4 100644
--- a/arch/arm/mach-omap2/pm.c
+++ b/arch/arm/mach-omap2/pm.c
@@ -163,11 +163,11 @@ err:
}
/*
- * This API is to be called during init to put the various voltage
+ * This API is to be called during init to set the various voltage
* domains to the voltage as per the opp table. Typically we boot up
* at the nominal voltage. So this function finds out the rate of
* the clock associated with the voltage domain, finds out the correct
- * opp entry and puts the voltage domain to the voltage specifies
+ * opp entry and sets the voltage domain to the voltage specified
* in the opp entry
*/
static int __init omap2_set_init_voltage(char *vdd_name, char *clk_name,
@@ -218,7 +218,7 @@ static int __init omap2_set_init_voltage(char *vdd_name, char *clk_name,
return 0;
exit:
- printk(KERN_ERR "%s: Unable to put vdd_%s to its init voltage\n\n",
+ printk(KERN_ERR "%s: Unable to set vdd_%s to its init voltage\n\n",
__func__, vdd_name);
return -EINVAL;
}
--
1.7.6
next parent reply other threads:[~2011-08-30 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r543rkdk.fsf@ti.com>
2011-08-30 16:48 ` Johan Hovold [this message]
2011-08-30 16:48 ` [PATCH 2/2 RESEND] OMAP2+: pm: clean up error messages Johan Hovold
2011-08-30 21:15 ` Kevin Hilman
2011-08-30 21:14 ` [PATCH 1/2 RESEND] OMAP2+: pm: fix typos Kevin Hilman
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=1314722897-25040-1-git-send-email-jhovold@gmail.com \
--to=jhovold@gmail.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).