linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Icenowy Zheng <icenowy@aosc.io>, Eduardo Valentin <edubezval@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: core: fix some format issues on critical shutdown string
Date: Tue, 08 Aug 2017 17:17:59 +0800	[thread overview]
Message-ID: <1502183879.4296.26.camel@intel.com> (raw)
In-Reply-To: <20170723142149.43869-1-icenowy@aosc.io>

On Sun, 2017-07-23 at 22:21 +0800, Icenowy Zheng wrote:
> The critical shutdown notice string used to have some spaces missing,
> which makes it not so pretty.
> 
> Add the spaces to satisfy usual English space rules.
> 
> Reported-by: Mingcong Bai <jeffbai@aosc.io>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>

applied.

thanks,
rui
> ---
>  drivers/thermal/thermal_core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/thermal/thermal_core.c
> b/drivers/thermal/thermal_core.c
> index 5a51c740e372..671e4d15599d 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -390,7 +390,7 @@ static void handle_critical_trips(struct
> thermal_zone_device *tz,
>  
>  	if (trip_type == THERMAL_TRIP_CRITICAL) {
>  		dev_emerg(&tz->device,
> -			  "critical temperature reached(%d
> C),shutting down\n",
> +			  "critical temperature reached (%d C),
> shutting down\n",
>  			  tz->temperature / 1000);
>  		mutex_lock(&poweroff_lock);
>  		if (!power_off_triggered) {

      reply	other threads:[~2017-08-08  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23 14:21 [PATCH] thermal: core: fix some format issues on critical shutdown string Icenowy Zheng
2017-08-08  9:17 ` Zhang Rui [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=1502183879.4296.26.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=edubezval@gmail.com \
    --cc=icenowy@aosc.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.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).