From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH v1 1/1] iio: adc: mxs-lradc-adc: Get rid of OF specifics
Date: Tue, 21 Jun 2022 13:35:44 +0300 [thread overview]
Message-ID: <YrGfAD/zNdsH4cw/@smile.fi.intel.com> (raw)
In-Reply-To: <YrGc1WKpZ/ik3Bt+@smile.fi.intel.com>
On Tue, Jun 21, 2022 at 01:26:29PM +0300, Andy Shevchenko wrote:
> On Mon, Jun 20, 2022 at 06:56:27PM -0300, Fabio Estevam wrote:
> > On Mon, Jun 20, 2022 at 6:34 PM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
...
> > If you send a v2 with "#include <linux/property.h>" then you can add:
>
> Actually the entire thingy with setting node is not needed in this driver.
I stand corrected, the fwnode assignment is done fore the IIO parent's parent,
it's needed...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-21 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 17:33 Andy Shevchenko
2022-06-03 17:10 ` Jonathan Cameron
2022-06-20 19:42 ` Jonathan Cameron
2022-09-06 13:36 ` Andy Shevchenko
2022-09-11 9:52 ` Jonathan Cameron
2022-09-12 10:21 ` Andy Shevchenko
2022-09-12 10:24 ` Andy Shevchenko
2022-06-20 21:13 ` Fabio Estevam
[not found] ` <CAHp75Vd9yah3D8dUOPinhj=nm9GQs3xOsWZRL=6CvaROZC3OCQ@mail.gmail.com>
2022-06-20 21:56 ` Fabio Estevam
2022-06-21 10:26 ` Andy Shevchenko
2022-06-21 10:35 ` Andy Shevchenko [this message]
2022-06-21 10:58 ` Andy Shevchenko
2022-06-21 11:06 ` Fabio Estevam
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=YrGfAD/zNdsH4cw/@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=festevam@gmail.com \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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
all inboxes | Powered by JetHome®