From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: blogic@openwrt.org, linus.walleij@linaro.org,
bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org
Cc: dev@kresin.me, linux-kernel@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/4] gpio: stp-xway: small cleanups and improvements
Date: Wed, 3 Jul 2019 00:32:44 +0200 [thread overview]
Message-ID: <20190702223248.31934-1-martin.blumenstingl@googlemail.com> (raw)
This series brings a few small cleanups and improvements to the stp-xway
driver:
- enable compile-testing
- preparation for whenever the lantiq target switches to the common clock
framework
- easier to read (for me)
None of these fixes any known bugs so there's no Fixes tag anywhere.
It's probably too late for inclusion into Linux 5.3. No need to rush,
I'm happy with 5.4 as well.
Martin Blumenstingl (4):
gpio: stp-xway: simplify error handling in xway_stp_probe()
gpio: stp-xway: improve module clock error handling
gpio: stp-xway: get rid of the #include <lantiq_soc.h> dependency
gpio: stp-xway: allow compile-testing
drivers/gpio/Kconfig | 3 ++-
drivers/gpio/gpio-stp-xway.c | 33 +++++++++++++++++----------------
2 files changed, 19 insertions(+), 17 deletions(-)
--
2.22.0
next reply other threads:[~2019-07-03 1:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 22:32 Martin Blumenstingl [this message]
2019-07-02 22:32 ` [PATCH 1/4] gpio: stp-xway: simplify error handling in xway_stp_probe() Martin Blumenstingl
2019-07-04 7:39 ` Linus Walleij
2019-07-02 22:32 ` [PATCH 2/4] gpio: stp-xway: improve module clock error handling Martin Blumenstingl
2019-07-04 7:40 ` Linus Walleij
2019-07-02 22:32 ` [PATCH 3/4] gpio: stp-xway: get rid of the #include <lantiq_soc.h> dependency Martin Blumenstingl
2019-07-04 7:41 ` Linus Walleij
2019-07-02 22:32 ` [PATCH 4/4] gpio: stp-xway: allow compile-testing Martin Blumenstingl
2019-07-04 7:44 ` Linus Walleij
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=20190702223248.31934-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=bgolaszewski@baylibre.com \
--cc=blogic@openwrt.org \
--cc=dev@kresin.me \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®