From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Puranjay Mohan <puranjay12@gmail.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
heikki.krogerus@linux.intel.com, kuba@kernel.org,
saravanak@google.com, linux-kernel@vger.kernel.org,
lars@metafoo.de, Michael.Hennerich@analog.com,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: accel: adxl355: use fwnode_irq_get_byname()
Date: Sun, 27 Feb 2022 12:41:34 +0000 [thread overview]
Message-ID: <20220227124134.4d4e4644@jic23-huawei> (raw)
In-Reply-To: <YflfEpKj0ilHnQQm@smile.fi.intel.com>
On Tue, 1 Feb 2022 18:25:54 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Wed, Nov 10, 2021 at 01:38:40AM +0530, Puranjay Mohan wrote:
> > Use the generic fwnode_irq_get_byname() in place of of_irq_get_byname()
> > to get the IRQ number from the interrupt pin.
>
> Heads up, the fwnode_irq_get_byname() is in I2C tree and if Jonathan wants to
> apply this one, the PR [1] can be used.
>
> [1]: https://lore.kernel.org/linux-i2c/YfRiGR3AT8tzyweG@shikoro/T/#u
>
Thanks Andy.
I'm going to let this go the slow way and pick up this patch after the
merge window when I can avoid pulling in that PR.
Basically I'm feeling lazy today :)
Jonathan
next prev parent reply other threads:[~2022-02-27 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:08 [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname() Puranjay Mohan
2021-11-09 20:08 ` [PATCH v2 1/2] device property: Add fwnode_irq_get_byname() Puranjay Mohan
2021-11-10 8:53 ` Andy Shevchenko
2021-11-10 17:04 ` Puranjay Mohan
2021-11-10 17:27 ` Andy Shevchenko
2021-11-09 20:08 ` [PATCH v2 2/2] iio: accel: adxl355: use fwnode_irq_get_byname() Puranjay Mohan
2022-02-01 16:25 ` Andy Shevchenko
2022-02-27 12:41 ` Jonathan Cameron [this message]
2022-04-10 17:13 ` Jonathan Cameron
2022-04-11 10:17 ` Andy Shevchenko
2021-11-09 22:42 ` [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname() Saravana Kannan
2021-11-10 8:32 ` Andy Shevchenko
2021-11-10 8:32 ` 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=20220227124134.4d4e4644@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kuba@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.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