From: Dejin Zheng <zhengdejin5@gmail.com>
To: corbet@lwn.net, gregkh@linuxfoundation.org, f.fainelli@gmail.com,
michal.simek@xilinx.com, wsa+renesas@sang-engineering.com,
paul@crapouillou.net, shawnguo@kernel.org,
linus.walleij@linaro.org, linux-doc@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dejin Zheng <zhengdejin5@gmail.com>
Subject: [PATCH v3 0/2] drivers: provide devm_platform_request_irq()
Date: Wed, 27 May 2020 22:21:44 +0800 [thread overview]
Message-ID: <20200527142146.8940-1-zhengdejin5@gmail.com> (raw)
It will call devm_request_irq() after platform_get_irq() function
in many drivers, sometimes, it is not right for the error handling
of these two functions in some drivers. so provide this function
to simplify the driver.
the first patch will provide devm_platform_request_irq(), and the
other patch will convert to devm_platform_request_irq() in some
i2c bus dirver.
v2 -> v3:
- add devm_platform_request_irq() to devres.rst by Grygorii's
suggestion.
- And also Thanks Michal, Wolfram and Linus's review and
comments.
v1 -> v2:
- I give up this series of patches in v1 version. I resend this
patches v2 by that discussion:
https://patchwork.ozlabs.org/project/linux-i2c/patch/20200520144821.8069-1-zhengdejin5@gmail.com/
The patch content has not changed.
Dejin Zheng (2):
drivers: provide devm_platform_request_irq()
i2c: busses: convert to devm_platform_request_irq()
.../driver-api/driver-model/devres.rst | 1 +
drivers/base/platform.c | 33 +++++++++++++++++++
drivers/i2c/busses/i2c-bcm-kona.c | 16 ++-------
drivers/i2c/busses/i2c-cadence.c | 10 ++----
drivers/i2c/busses/i2c-digicolor.c | 10 ++----
drivers/i2c/busses/i2c-emev2.c | 5 ++-
drivers/i2c/busses/i2c-jz4780.c | 5 ++-
drivers/i2c/busses/i2c-meson.c | 13 +++-----
drivers/i2c/busses/i2c-mxs.c | 9 ++---
drivers/i2c/busses/i2c-pnx.c | 9 ++---
drivers/i2c/busses/i2c-rcar.c | 9 ++---
drivers/i2c/busses/i2c-rk3x.c | 14 ++------
drivers/i2c/busses/i2c-sirf.c | 10 ++----
drivers/i2c/busses/i2c-stu300.c | 4 +--
drivers/i2c/busses/i2c-synquacer.c | 12 ++-----
include/linux/platform_device.h | 4 +++
16 files changed, 73 insertions(+), 91 deletions(-)
--
2.25.0
reply other threads:[~2020-05-27 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200527142146.8940-1-zhengdejin5@gmail.com \
--to=zhengdejin5@gmail.com \
--cc=corbet@lwn.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=paul@crapouillou.net \
--cc=shawnguo@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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).