Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
	linux-iio@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 0/8] IIO: Drop incorrect includes of linux/of.h
Date: Mon, 19 Feb 2024 10:20:17 +0100	[thread overview]
Message-ID: <6fff9a9c64c9ba13af4f272a63132dec7a97ae02.camel@gmail.com> (raw)
In-Reply-To: <20240218173323.1023703-1-jic23@kernel.org>

On Sun, 2024-02-18 at 17:33 +0000, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> These were false positives when I was looking at which drivers
> should be converted over to fwnode based handling from
> linux/property.h
> 
> None of them use anything defined in linux/of.h, so drop the include
> and include more specific headers (mostly linux/mod_devicetable.h)
> instead.
> 
> Jonathan Cameron (8):
>   iio: light: vl6180: Drop unused linux/of.h include
>   iio: light: al3320a: Drop unused linux/of.h include
>   iio: light: al3010: Switch from linux/of.h to linux/mod_devicetable.h
>   iio: adc: ads8688: Switch to mod_devicetable.h for struct of_device_id
>     definition
>   iio: accel: adxl372: Switch from linux/of.h to linux/mod_devicetable.h
>   iio: accel: bma180: Switch from linux/of.h to linux/mod_devicetable.h
>   iio: accel: kxsd9: Switch from linux/of.h to linux/mod_devicetable.h
>   iio: dac: mcp4821: Switch to including mod_devicetable.h for struct
>     of_device_id definition.
> 
>  drivers/iio/accel/adxl372_spi.c | 2 +-
>  drivers/iio/accel/bma180.c      | 2 +-
>  drivers/iio/accel/kxsd9-spi.c   | 2 +-
>  drivers/iio/adc/ti-ads8688.c    | 2 +-
>  drivers/iio/dac/mcp4821.c       | 2 +-
>  drivers/iio/light/al3010.c      | 2 +-
>  drivers/iio/light/al3320a.c     | 1 -
>  drivers/iio/light/vl6180.c      | 1 -
>  8 files changed, 6 insertions(+), 8 deletions(-)
> 

Reviewed-by: Nuno Sa <nuno.sa@analog.com>


  parent reply	other threads:[~2024-02-19  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 17:33 [PATCH 0/8] IIO: Drop incorrect includes of linux/of.h Jonathan Cameron
2024-02-18 17:33 ` [PATCH 1/8] iio: light: vl6180: Drop unused linux/of.h include Jonathan Cameron
2024-02-18 17:33 ` [PATCH 2/8] iio: light: al3320a: " Jonathan Cameron
2024-02-18 17:33 ` [PATCH 3/8] iio: light: al3010: Switch from linux/of.h to linux/mod_devicetable.h Jonathan Cameron
2024-02-18 17:33 ` [PATCH 4/8] iio: adc: ads8688: Switch to mod_devicetable.h for struct of_device_id definition Jonathan Cameron
2024-02-18 17:33 ` [PATCH 5/8] iio: accel: adxl372: Switch from linux/of.h to linux/mod_devicetable.h Jonathan Cameron
2024-02-18 17:33 ` [PATCH 6/8] iio: accel: bma180: " Jonathan Cameron
2024-02-18 17:33 ` [PATCH 7/8] iio: accel: kxsd9: " Jonathan Cameron
2024-02-18 17:33 ` [PATCH 8/8] iio: dac: mcp4821: Switch to including mod_devicetable.h for struct of_device_id definition Jonathan Cameron
2024-02-19  9:20 ` Nuno Sá [this message]
2024-02-19 12:24 ` [PATCH 0/8] IIO: Drop incorrect includes of linux/of.h Andy Shevchenko
2024-02-24 15:57   ` 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=6fff9a9c64c9ba13af4f272a63132dec7a97ae02.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.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