From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [PATCH 0/3] gpio: drop a few unneeded irq_{request,release}_resources implementations
Date: Fri, 8 Feb 2019 12:51:58 +0100 [thread overview]
Message-ID: <20190208115201.7518-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
Three GPIO drivers in the tree implement the
irq_{request,release}_resources hooks with what is in fact the default
implementation provided by the GPIO core, making this driver-specific
code redundant.
It is worth mentioning that I do not own any of the affected
platforms, to the three patches have only been built-tested. Each is
Cc'ed to the appropriate maintainer, except gpio-em that has no
platform-specific maintainer.
Best regards,
Thomas Petazzoni
Thomas Petazzoni (3):
gpio: bcm-kona: drop ->irq_{request,release}_resources hooks
gpio: dwapb: drop ->irq_{request,release}_resources hooks
gpio: em: drop ->irq_{request,release}_resources hooks
drivers/gpio/gpio-bcm-kona.c | 16 ----------------
drivers/gpio/gpio-dwapb.c | 27 ---------------------------
drivers/gpio/gpio-em.c | 25 -------------------------
3 files changed, 68 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-08 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:51 Thomas Petazzoni [this message]
2019-02-08 11:51 ` [PATCH 1/3] gpio: bcm-kona: drop ->irq_{request,release}_resources hooks Thomas Petazzoni
2019-02-12 20:53 ` Scott Branden
2019-02-08 11:52 ` [PATCH 2/3] gpio: dwapb: " Thomas Petazzoni
2019-02-08 11:52 ` [PATCH 3/3] gpio: em: " Thomas Petazzoni
2019-02-08 14:44 ` [PATCH 0/3] gpio: drop a few unneeded irq_{request,release}_resources implementations 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=20190208115201.7518-1-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--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;
as well as URLs for NNTP newsgroup(s).