All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dejin Zheng <zhengdejin5@gmail.com>
To: corbet@lwn.net, gregkh@linuxfoundation.org,
	michal.simek@xilinx.com, wsa+renesas@sang-engineering.com,
	linus.walleij@linaro.org, linux-doc@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v3 1/2] drivers: provide devm_platform_request_irq()
Date: Fri, 17 Jul 2020 22:30:30 +0800	[thread overview]
Message-ID: <20200717143030.GB25998@nuc8i5> (raw)
In-Reply-To: <20200527142611.9006-1-zhengdejin5@gmail.com>

On Wed, May 27, 2020 at 10:26:10PM +0800, Dejin Zheng wrote:
Hi Jonathan, Greg, Rafael, Linus, Michal and Wolfram:

Could you help me review this patch if you have free time?
Thank you very very much!

BR,
Dejin
> 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.
> 
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Signed-off-by: Dejin Zheng <zhengdejin5@gmail.com>
> ---
> v2 -> v3:
> 	- add devm_platform_request_irq() to devres.rst by Grygorii's
> 	  suggestion.
> v1 -> v2:
> 	- The patch content has not changed. just resend it by this discussion:
> 	  https://patchwork.ozlabs.org/project/linux-i2c/patch/20200520144821.8069-1-zhengdejin5@gmail.com/
> 
 

  parent reply	other threads:[~2020-07-17 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 14:26 [PATCH v3 1/2] drivers: provide devm_platform_request_irq() Dejin Zheng
2020-05-27 14:26 ` [PATCH v3 2/2] i2c: busses: convert to devm_platform_request_irq() Dejin Zheng
2020-05-28  7:10   ` Michal Simek
2020-07-17 14:30 ` Dejin Zheng [this message]
2020-07-17 14:59   ` [PATCH v3 1/2] drivers: provide devm_platform_request_irq() Greg KH
2020-07-17 15:06     ` Dejin Zheng
2020-05-27 18:45 Markus Elfring
2020-05-27 18:45 ` Markus Elfring

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=20200717143030.GB25998@nuc8i5 \
    --to=zhengdejin5@gmail.com \
    --cc=corbet@lwn.net \
    --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=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.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 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.