From: arvind.yadav.cs@gmail.com (Arvind Yadav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] clk: pr_err() strings should end with newlines
Date: Fri, 24 Nov 2017 12:25:27 +0530 [thread overview]
Message-ID: <cover.1511505932.git.arvind.yadav.cs@gmail.com> (raw)
pr_err() messages should end with a new-line to avoid other messages
being concatenated.
Arvind Yadav (6):
[PATCH 1/6] clk: stm32f4: pr_err() strings should end with newlines
[PATCH 2/6] clk: lpc32xx: pr_err() strings should end with newlines
[PATCH 3/6] clk: SPEAr: pr_err() strings should end with newlines
[PATCH 4/6] SPEAr: clk: pr_err() strings should end with newlines
[PATCH 5/6] clk: h8s2678: pr_err() strings should end with newlines
[PATCH 6/6] clk: h8300: pr_err() strings should end with newlines
drivers/clk/clk-stm32f4.c | 2 +-
drivers/clk/h8300/clk-div.c | 4 ++--
drivers/clk/h8300/clk-h8s2678.c | 6 +++---
drivers/clk/nxp/clk-lpc32xx.c | 4 ++--
drivers/clk/spear/clk-frac-synth.c | 2 +-
drivers/clk/spear/clk-gpt-synth.c | 2 +-
6 files changed, 10 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2017-11-24 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 6:55 Arvind Yadav [this message]
2017-11-24 6:55 ` [PATCH 1/6] clk: stm32f4: pr_err() strings should end with newlines Arvind Yadav
2017-12-07 6:40 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 2/6] clk: lpc32xx: " Arvind Yadav
2017-11-25 8:59 ` Vladimir Zapolskiy
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 3/6] clk: SPEAr: " Arvind Yadav
2017-11-28 2:42 ` Viresh Kumar
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 4/6] SPEAr: clk: " Arvind Yadav
2017-11-28 2:42 ` Viresh Kumar
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 5/6] clk: h8s2678: " Arvind Yadav
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 6/6] clk: h8300: " Arvind Yadav
2017-12-07 6:41 ` Stephen Boyd
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=cover.1511505932.git.arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@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).