From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 1/1] iio: core: Convert to use firmware node handle instead of OF node
Date: Thu, 14 Apr 2022 15:53:56 +0300 [thread overview]
Message-ID: <YlgZZMPVDU9Yc7l5@smile.fi.intel.com> (raw)
In-Reply-To: <fd9aa60147aba2d76e4b2d1b82011c610d3e52d6.camel@gmail.com>
On Thu, Apr 14, 2022 at 09:17:22AM +0200, Nuno Sá wrote:
> On Wed, 2022-04-13 at 21:02 +0300, Andy Shevchenko wrote:
> > Switch the IIO core to use firmware node handle instead of OF node.
> > This will allow to get label from firmware on non-OF systems.
> >
> > Note, this doesn't change of_iio_*() APIs for now.
> So I was actually planning to send the same patch today or in the next
> few days. I do also have the conversion of inkern.c so I guess we can
> move in 3 different ways:
>
> 1. If you are planning or already have some work with it, I'm more than
> fine in just forgetting my patches and let you do it (you are cleaning
> all the drivers already)
>
> 2. I can send the patch (without this one) already for reviewing... It
> won't apply because I think there will be some conflicts with some of
> the drivers you changed already. Fun fact, remove of.h from iio.h and
> you see some drivers relying on it for property.h and mod_devicetable.h
>
> 3. Just wait for your latest patches to be merged and send mine next
> week.
>
> Up to you :)
Thanks for letting me know. I think the best course of actions now is
to settle down with what I have sent and you then rebase your stuff and
sent out for review. I will help with reviewing and I'm glad to hear
that you are step ahead of me. I wasn't planning to chase the inkern.c
in the future (at least nearest future).
That said, it seems like fits the #3 from the above list you provided.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-04-14 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 18:02 [PATCH v1 1/1] iio: core: Convert to use firmware node handle instead of OF node Andy Shevchenko
2022-04-13 18:07 ` Andy Shevchenko
2022-04-14 7:17 ` Nuno Sá
2022-04-14 12:53 ` Andy Shevchenko [this message]
2022-04-16 11:17 ` Jonathan Cameron
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=YlgZZMPVDU9Yc7l5@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.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