From: Stephen Boyd <sboyd@codeaurora.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 4/4] clk-u300: Fix a typo in two comment lines
Date: Mon, 13 Nov 2017 17:58:04 -0800 [thread overview]
Message-ID: <20171114015804.GF11955@codeaurora.org> (raw)
In-Reply-To: <c113ba39-e9b4-a4e5-6fa1-f83c9b59a4d5@users.sourceforge.net>
On 09/26, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 26 Sep 2017 19:57:50 +0200
>
> Add a missing character in these descriptions.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-14 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 18:20 [PATCH 0/4] U300 clock: Adjustments for three function implementations SF Markus Elfring
2017-09-26 18:21 ` [PATCH 1/4] clk-u300: Delete an error message for a failed memory allocation in two functions SF Markus Elfring
2017-11-14 1:58 ` Stephen Boyd
2017-09-26 18:22 ` [PATCH 2/4] clk-u300: Improve a size determination " SF Markus Elfring
2017-11-14 1:58 ` Stephen Boyd
2017-09-26 18:23 ` [PATCH 3/4] clk-u300: Add some spaces for better code readability SF Markus Elfring
2017-11-14 1:58 ` Stephen Boyd
2017-09-26 18:25 ` [PATCH 4/4] clk-u300: Fix a typo in two comment lines SF Markus Elfring
2017-11-14 1:58 ` Stephen Boyd [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=20171114015804.GF11955@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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).