From: Vladimir Zapolskiy <vz@mleia.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>,
sboyd@codeaurora.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@st.com, ysato@users.sourceforge.jp,
slemieux.tyco@gmail.com, vireshk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/6] clk: lpc32xx: pr_err() strings should end with newlines
Date: Sat, 25 Nov 2017 10:59:45 +0200 [thread overview]
Message-ID: <9a9fda0f-6da5-a6c3-439a-01db44f171b9@mleia.com> (raw)
In-Reply-To: <1dddfd71153339875c7bedf6e562483607180a4d.1511505932.git.arvind.yadav.cs@gmail.com>
Hello Arvind,
thank you for the change.
On 11/24/2017 08:55 AM, 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>
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
--
With best wishes,
Vladimir
WARNING: multiple messages have this Message-ID (diff)
From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] clk: lpc32xx: pr_err() strings should end with newlines
Date: Sat, 25 Nov 2017 10:59:45 +0200 [thread overview]
Message-ID: <9a9fda0f-6da5-a6c3-439a-01db44f171b9@mleia.com> (raw)
In-Reply-To: <1dddfd71153339875c7bedf6e562483607180a4d.1511505932.git.arvind.yadav.cs@gmail.com>
Hello Arvind,
thank you for the change.
On 11/24/2017 08:55 AM, 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>
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2017-11-25 8:59 UTC|newest]
Thread overview: 34+ 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 ` Arvind Yadav
2017-11-24 6:55 ` [PATCH 1/6] clk: stm32f4: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-12-07 6:40 ` Stephen Boyd
2017-12-07 6:40 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 2/6] clk: lpc32xx: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-11-25 8:59 ` Vladimir Zapolskiy [this message]
2017-11-25 8:59 ` Vladimir Zapolskiy
2017-12-07 6:41 ` Stephen Boyd
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 3/6] clk: SPEAr: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-11-28 2:42 ` Viresh Kumar
2017-11-28 2:42 ` Viresh Kumar
2017-12-07 6:41 ` Stephen Boyd
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 4/6] SPEAr: clk: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-11-28 2:42 ` Viresh Kumar
2017-11-28 2:42 ` Viresh Kumar
2017-12-07 6:41 ` Stephen Boyd
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 5/6] clk: h8s2678: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-12-07 6:41 ` Stephen Boyd
2017-12-07 6:41 ` Stephen Boyd
2017-11-24 6:55 ` [PATCH 6/6] clk: h8300: " Arvind Yadav
2017-11-24 6:55 ` Arvind Yadav
2017-12-07 6:41 ` Stephen Boyd
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=9a9fda0f-6da5-a6c3-439a-01db44f171b9@mleia.com \
--to=vz@mleia.com \
--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=sboyd@codeaurora.org \
--cc=slemieux.tyco@gmail.com \
--cc=vireshk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.