From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] clocksource: pr_err() strings should end with newlines
Date: Tue, 26 Sep 2017 01:35:20 +0200 [thread overview]
Message-ID: <f46f1d66-9120-9be3-dd5f-fa26579730eb@linaro.org> (raw)
In-Reply-To: <1506327401-30521-1-git-send-email-arvind.yadav.cs@gmail.com>
On 25/09/2017 10:16, Arvind Yadav wrote:
> pr_err() messages should terminated with a new-line to avoid
> other messages being concatenated onto the end.
>
> Arvind Yadav (3):
> [PATCH 1/3] clocksource: fttmr010: pr_err() strings should end with newlines
> [PATCH 2/3] clocksource: owl: pr_err() strings should end with newlines
> [PATCH 3/3] clocksource: rockchip: pr_err() strings should end with newlines
>
> drivers/clocksource/owl-timer.c | 4 ++--
> drivers/clocksource/rockchip_timer.c | 2 +-
> drivers/clocksource/timer-fttmr010.c | 4 ++--
> 3 files changed, 5 insertions(+), 5 deletions(-)
Applied and slightly changed the commit log to:
pr_err() messages should end with a new-line to avoid other messages
being concatenated.
In the future, please use the subject subsystem format to:
clocksource/drivers/<timer>: ....
Thanks.
-- Daniel
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2017-09-25 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 8:16 [PATCH 0/3] clocksource: pr_err() strings should end with newlines Arvind Yadav
2017-09-25 8:16 ` [PATCH 1/3] clocksource: fttmr010: " Arvind Yadav
2017-09-25 8:16 ` [PATCH 2/3] clocksource: owl: " Arvind Yadav
2017-09-25 8:45 ` Andreas Färber
2017-09-25 8:16 ` [PATCH 3/3] clocksource: rockchip: " Arvind Yadav
2017-09-25 23:35 ` Daniel Lezcano [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=f46f1d66-9120-9be3-dd5f-fa26579730eb@linaro.org \
--to=daniel.lezcano@linaro.org \
--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).