From: Stephen Boyd <sboyd@codeaurora.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
ysato@users.sourceforge.jp, vz@mleia.com,
slemieux.tyco@gmail.com, vireshk@kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/6] clk: SPEAr: pr_err() strings should end with newlines
Date: Wed, 6 Dec 2017 22:41:03 -0800 [thread overview]
Message-ID: <20171207064103.GR4283@codeaurora.org> (raw)
In-Reply-To: <03a5ce213323863375e1fb3f85c0c3cc8c921a41.1511505932.git.arvind.yadav.cs@gmail.com>
On 11/24, Arvind Yadav wrote:
> pr_err() messages should end with a new-line to avoid other messages
> being concatenated.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-07 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 6:55 [PATCH 0/6] clk: pr_err() strings should end with newlines Arvind Yadav
2017-11-24 6:55 ` [PATCH 1/6] clk: stm32f4: " 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 [this message]
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=20171207064103.GR4283@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alexandre.torgue@st.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=slemieux.tyco@gmail.com \
--cc=vireshk@kernel.org \
--cc=vz@mleia.com \
--cc=ysato@users.sourceforge.jp \
/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).