From: Jonathan Cameron <jic23@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: lsm6dsx: Use i3cdev_to_dev to get device pointer
Date: Sat, 9 Nov 2024 15:16:43 +0000 [thread overview]
Message-ID: <20241109151643.4e4608bf@jic23-huawei> (raw)
In-Reply-To: <20241109145430.3702482-1-linux@roeck-us.net>
On Sat, 9 Nov 2024 06:54:30 -0800
Guenter Roeck <linux@roeck-us.net> wrote:
> I3C client drivers should not include linux/i3c/master.h. Use
> i3cdev_to_dev() to get the device pointer from struct i3c_device
> to be able to avoid that include.
>
> Suggested-by: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Applied to the testing branch of iio.git. I'll be rebasing that
on 6.13-rc1 once available and then push out as togreg for linux-next
to pick up.
Thanks,
Jonathan
> ---
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c
> index 3b0c8b19c448..207dcc0ad988 100644
> --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c
> +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c
> @@ -9,7 +9,6 @@
> #include <linux/mod_devicetable.h>
> #include <linux/module.h>
> #include <linux/i3c/device.h>
> -#include <linux/i3c/master.h>
> #include <linux/slab.h>
> #include <linux/regmap.h>
>
> @@ -30,15 +29,16 @@ static int st_lsm6dsx_i3c_probe(struct i3c_device *i3cdev)
> };
> const struct i3c_device_id *id = i3c_device_match_id(i3cdev,
> st_lsm6dsx_i3c_ids);
> + struct device *dev = i3cdev_to_dev(i3cdev);
> struct regmap *regmap;
>
> regmap = devm_regmap_init_i3c(i3cdev, &st_lsm6dsx_i3c_regmap_config);
> if (IS_ERR(regmap)) {
> - dev_err(&i3cdev->dev, "Failed to register i3c regmap %ld\n", PTR_ERR(regmap));
> + dev_err(dev, "Failed to register i3c regmap %ld\n", PTR_ERR(regmap));
> return PTR_ERR(regmap);
> }
>
> - return st_lsm6dsx_probe(&i3cdev->dev, 0, (uintptr_t)id->data, regmap);
> + return st_lsm6dsx_probe(dev, 0, (uintptr_t)id->data, regmap);
> }
>
> static struct i3c_driver st_lsm6dsx_driver = {
prev parent reply other threads:[~2024-11-09 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 14:54 [PATCH] iio: imu: lsm6dsx: Use i3cdev_to_dev to get device pointer Guenter Roeck
2024-11-09 15:16 ` Jonathan Cameron [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=20241109151643.4e4608bf@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo@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