From: Viresh Kumar <viresh.kumar@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Linux PM list <linux-pm@vger.kernel.org>
Cc: Jiri Kosina <trivial@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH/TRIVIAL 1/4] cpufreq: cpufreq-dt: Move newline to end of error message
Date: Wed, 19 Nov 2014 13:36:51 +0530 [thread overview]
Message-ID: <CAOh2x=kB2QMTXbNg7gCdHoo9QWUG-vc_VQ77iGKz-gfqMd1+KQ@mail.gmail.com> (raw)
In-Reply-To: <1414057977-4191-1-git-send-email-geert+renesas@glider.be>
On Thu, Oct 23, 2014 at 3:22 PM, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Currently the error message is needlessly splitted across two lines.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> ---
> drivers/cpufreq/cpufreq-dt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq-dt.c b/drivers/cpufreq/cpufreq-dt.c
> index 92c162af5045a2da..685f59598137ea03 100644
> --- a/drivers/cpufreq/cpufreq-dt.c
> +++ b/drivers/cpufreq/cpufreq-dt.c
> @@ -192,7 +192,7 @@ static int cpufreq_init(struct cpufreq_policy *policy)
>
> ret = allocate_resources(policy->cpu, &cpu_dev, &cpu_reg, &cpu_clk);
> if (ret) {
> - pr_err("%s: Failed to allocate resources\n: %d", __func__, ret);
> + pr_err("%s: Failed to allocate resources: %d\n", __func__, ret);
> return ret;
> }
Please add me and linux-pm in cc next time.
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
prev parent reply other threads:[~2014-11-19 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 9:52 [PATCH/TRIVIAL 1/4] cpufreq: cpufreq-dt: Move newline to end of error message Geert Uytterhoeven
2014-10-23 9:52 ` [PATCH/TRIVIAL 2/4] drm/i915: " Geert Uytterhoeven
2014-10-23 9:52 ` [PATCH/TRIVIAL 3/4] iwlegacy: 4965-rs: Remove bogus colon after newline from debug message Geert Uytterhoeven
2014-10-23 9:52 ` [PATCH/TRIVIAL 4/4] uwb: " Geert Uytterhoeven
2014-11-19 8:06 ` Viresh Kumar [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='CAOh2x=kB2QMTXbNg7gCdHoo9QWUG-vc_VQ77iGKz-gfqMd1+KQ@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=trivial@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).