From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-pwm@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-tegra@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-riscv@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] pwm: Fix minor Kconfig whitespace issues
Date: Wed, 8 Jan 2020 14:00:52 +0100 [thread overview]
Message-ID: <20200108130052.GF1993114@ulmo> (raw)
In-Reply-To: <20191230172113.17222-1-krzk@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
On Mon, Dec 30, 2019 at 06:21:12PM +0100, Krzysztof Kozlowski wrote:
> Remove double whitespace after "config" keyword.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/pwm/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-08 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 17:21 [PATCH 1/2] pwm: Fix minor Kconfig whitespace issues Krzysztof Kozlowski
2019-12-30 17:21 ` [PATCH 2/2] pwm: Enable compile testing for some of drivers Krzysztof Kozlowski
2019-12-30 19:30 ` Florian Fainelli
2019-12-31 14:52 ` Martin Blumenstingl
2020-01-06 9:53 ` Claudiu.Beznea
2020-01-07 7:26 ` Uwe Kleine-König
2020-01-07 8:25 ` Krzysztof Kozlowski
2020-01-07 10:42 ` Uwe Kleine-König
2020-01-07 11:03 ` Krzysztof Kozlowski
2020-01-07 11:33 ` Uwe Kleine-König
2020-01-07 11:54 ` Krzysztof Kozlowski
2020-01-07 12:09 ` Uwe Kleine-König
2020-01-07 12:15 ` Krzysztof Kozlowski
2020-01-08 13:00 ` Thierry Reding [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=20200108130052.GF1993114@ulmo \
--to=thierry.reding@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-tegra@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).