linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Sanjeev Premi <premi@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] omap3: boot message is not an error
Date: Tue, 17 May 2011 19:33:41 +0200	[thread overview]
Message-ID: <1305653621.2694.4.camel@vence> (raw)
In-Reply-To: <1305644565-26233-1-git-send-email-premi@ti.com>

Hi Sanjeev,

On Tue, 2011-05-17 at 20:32 +0530, Sanjeev Premi wrote:
> With current level, it shows up on the console
> despite using 'silent' in bootargs.
> 
> Signed-off-by: Sanjeev Premi <premi@ti.com>
> ---
> 
>  1) Couldn't find better text on commit message.
>     Any suggestions?
> 
>  2) Though pm34xx.x is changed, the change itself
>     is no related to power management. Hence, did
>     annotate "pm:"

Well, it's a change to PM core code, so PM prefix is fine.  How about:

OMAP3: PM: boot message is not an error, use pr_info

Also, please Cc linux-arm-kernel, and I will queue this fix for 2.6.40.

Minor comment below..

>  arch/arm/mach-omap2/pm34xx.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 343027f..7584ba8 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -901,7 +901,7 @@ static int __init omap3_pm_init(void)
>  
>  	pm_errata_configure();
>  
> -	printk(KERN_ERR "Power Management for TI OMAP3.\n");
> +	pr_info ("Power Management for TI OMAP3.\n");

Drop space before the opening '('.

>  	/* XXX prcm_setup_regs needs to be before enabling hw
>  	 * supervised mode for powerdomains */

Kevin



  reply	other threads:[~2011-05-17 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 15:02 [PATCH] omap3: boot message is not an error Sanjeev Premi
2011-05-17 17:33 ` Kevin Hilman [this message]
2011-05-18  5:45   ` Jarkko Nikula
2011-05-18  8:57     ` Kevin Hilman
2011-05-18  8:58       ` Premi, Sanjeev

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=1305653621.2694.4.camel@vence \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.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).