From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Keerthy <j-keerthy@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v2 0/2] drivers: new helper for ioremapping memory resources
Date: Wed, 20 Feb 2019 12:12:38 +0100 [thread overview]
Message-ID: <20190220111240.10041-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
There are currently 1200+ instances of using platform_get_resource()
and devm_ioremap_resource() together in the kernel tree. It's a minor
redundancy, but consolidation is always good.
The first patch in this series adds a wrapper for these two calls and
the second uses it in a driver I could test.
If accepted I'll prepare a coccinelle script that'll make it easier
to convert all users.
v1 -> v2:
- EXPORT_SYMBOL() -> EXPORT_SYMBOL_GPL()
Bartosz Golaszewski (2):
drivers: provide devm_platform_ioremap_resource()
gpio: davinci: use devm_platform_ioremap_resource()
drivers/base/platform.c | 18 ++++++++++++++++++
drivers/gpio/gpio-davinci.c | 4 +---
include/linux/platform_device.h | 3 +++
3 files changed, 22 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-20 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 11:12 Bartosz Golaszewski [this message]
2019-02-20 11:12 ` [PATCH v2 1/2] drivers: provide devm_platform_ioremap_resource() Bartosz Golaszewski
2019-02-20 11:16 ` Greg Kroah-Hartman
2019-02-20 11:21 ` Bartosz Golaszewski
2019-02-20 12:15 ` Greg Kroah-Hartman
2019-02-21 9:53 ` Bartosz Golaszewski
2019-02-21 12:06 ` Linus Walleij
2019-02-20 11:12 ` [PATCH v2 2/2] gpio: davinci: use devm_platform_ioremap_resource() Bartosz Golaszewski
2019-02-20 12:04 ` [PATCH v2 0/2] drivers: new helper for ioremapping memory resources Andy Shevchenko
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=20190220111240.10041-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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.