From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] Documentation: media: convert to use i2c_new_client_device()
Date: Mon, 15 Jun 2020 10:37:10 +0200 [thread overview]
Message-ID: <20200615103710.5e61104c@coco.lan> (raw)
In-Reply-To: <20200615075816.2848-6-wsa+renesas@sang-engineering.com>
Em Mon, 15 Jun 2020 09:58:14 +0200
Wolfram Sang <wsa+renesas@sang-engineering.com> escreveu:
> Move away from the deprecated API and advertise the new one.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
> I'd like to push it via I2C for 5.8-rc2.
OK!
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Documentation/driver-api/media/v4l2-subdev.rst | 2 +-
> Documentation/userspace-api/media/conf_nitpick.py | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/driver-api/media/v4l2-subdev.rst b/Documentation/driver-api/media/v4l2-subdev.rst
> index 6e71f67455bb..bc7e1fc40a9d 100644
> --- a/Documentation/driver-api/media/v4l2-subdev.rst
> +++ b/Documentation/driver-api/media/v4l2-subdev.rst
> @@ -451,7 +451,7 @@ The bridge driver also has some helper functions it can use:
> "module_foo", "chipid", 0x36, NULL);
>
> This loads the given module (can be ``NULL`` if no module needs to be loaded)
> -and calls :c:func:`i2c_new_device` with the given ``i2c_adapter`` and
> +and calls :c:func:`i2c_new_client_device` with the given ``i2c_adapter`` and
> chip/address arguments. If all goes well, then it registers the subdev with
> the v4l2_device.
>
> diff --git a/Documentation/userspace-api/media/conf_nitpick.py b/Documentation/userspace-api/media/conf_nitpick.py
> index d0c50d75f518..0a8e236d07ab 100644
> --- a/Documentation/userspace-api/media/conf_nitpick.py
> +++ b/Documentation/userspace-api/media/conf_nitpick.py
> @@ -27,7 +27,7 @@ nitpick_ignore = [
> ("c:func", "copy_to_user"),
> ("c:func", "determine_valid_ioctls"),
> ("c:func", "ERR_PTR"),
> - ("c:func", "i2c_new_device"),
> + ("c:func", "i2c_new_client_device"),
> ("c:func", "ioctl"),
> ("c:func", "IS_ERR"),
> ("c:func", "KERNEL_VERSION"),
Thanks,
Mauro
next prev parent reply other threads:[~2020-06-15 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 7:58 [PATCH 0/6] remove deprecated i2c_new_device API Wolfram Sang
2020-06-15 7:58 ` [PATCH 1/6] drm: encoder_slave: fix refcouting error for modules Wolfram Sang
2020-06-15 7:58 ` [PATCH 2/6] drm: encoder_slave: use new I2C API Wolfram Sang
2020-06-15 7:58 ` [PATCH 3/6] x86/platform/intel-mid: convert to use i2c_new_client_device() Wolfram Sang
2020-06-15 7:58 ` [PATCH 4/6] video: backlight: tosa_lcd: " Wolfram Sang
2020-06-18 8:43 ` Lee Jones
2020-06-15 7:58 ` [PATCH 5/6] Documentation: media: " Wolfram Sang
2020-06-15 8:37 ` Mauro Carvalho Chehab [this message]
2020-06-15 7:58 ` [PATCH 6/6] i2c: remove deprecated i2c_new_device API Wolfram Sang
2020-06-16 12:12 ` [PATCH 0/6] " Daniel Vetter
2020-06-16 14:05 ` Emil Velikov
2020-06-19 7:21 ` Wolfram Sang
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=20200615103710.5e61104c@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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