Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>,
	 Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (lm90) Switch channel parsing to fwnode APIs
Date: Tue, 14 Jul 2026 19:09:07 +0200	[thread overview]
Message-ID: <alZqpRFoMIsxfgS7@monoceros> (raw)
In-Reply-To: <9b8a49f4-2632-4984-a617-66f4161a3c5f@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]

Hello Guenter,

On Tue, Jul 14, 2026 at 07:43:13AM -0700, Guenter Roeck wrote:
> On 7/14/26 05:22, Uwe Kleine-König wrote:
> > On Mon, Jul 13, 2026 at 10:06:59PM +0300, Flaviu Nistor wrote:
> > > Replace OF property handling with fwnode API in the probe function to read
> > > the channels properties, improving the driver compatibility since this
> > > method is not limited to Device Tree only.
> > > Add also the needed headers for explicit include and clean up related
> > > function naming.
> > > 
> > > Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>
> > > ---
> > >   drivers/hwmon/lm90.c | 48 +++++++++++++++++++++-----------------------
> > >   1 file changed, 23 insertions(+), 25 deletions(-)
> > > 
> > > diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
> > > index 4b9c0ccdf260..045977e30cf4 100644
> > > --- a/drivers/hwmon/lm90.c
> > > +++ b/drivers/hwmon/lm90.c
> > > @@ -101,14 +101,16 @@
> > >   #include <linux/bits.h>
> > >   #include <linux/device.h>
> > >   #include <linux/err.h>
> > > +#include <linux/fwnode.h>
> > >   #include <linux/i2c.h>
> > >   #include <linux/init.h>
> > >   #include <linux/interrupt.h>
> > >   #include <linux/jiffies.h>
> > >   #include <linux/hwmon.h>
> > >   #include <linux/kstrtox.h>
> > > +#include <linux/mod_devicetable.h>
> > 
> > <linux/mod_devicetable.h> is going away soon. Please rely on
> > <linux/i2c.h> to provide of_device_id.
> 
> My hwmon-next branch is based off v7.2-rc1 and of_device_id
> is declared in mod_devicetable.h.

That sounds factual correct.

If you want to imply with that statement that my recommendation is
wrong, annoying or in other ways unsuitable to you I guess you either
have to be more explicit or live with it.

<linux/i2c.h> provides i2c_driver which uses of_device_id (via struct
device_driver) and thus includes a header that provides that struct.
That won't change in the foreseeable future. If that is not good enough
for you, find means to handle that in another way.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-07-14 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 19:06 [PATCH] hwmon: (lm90) Switch channel parsing to fwnode APIs Flaviu Nistor
2026-07-13 19:16 ` sashiko-bot
2026-07-14 12:22 ` Uwe Kleine-König
2026-07-14 14:43   ` Guenter Roeck
2026-07-14 17:09     ` Uwe Kleine-König [this message]

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=alZqpRFoMIsxfgS7@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=flaviu.nistor@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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