From: Yicong Yang <yangyicong@huawei.com>
To: Yang Yingliang <yangyingliang@huawei.com>, <linux-i2c@vger.kernel.org>
Cc: <yangyicong@hisilicon.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Osipenko <digetx@gmail.com>, Wolfram Sang <wsa@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: devres: add missing I2C helper
Date: Wed, 2 Nov 2022 15:29:56 +0800 [thread overview]
Message-ID: <bc4ad590-a051-f0d2-9f7d-c5ccb1ffee19@huawei.com> (raw)
In-Reply-To: <20221102034053.1708845-1-yangyingliang@huawei.com>
On 2022/11/2 11:40, Yang Yingliang wrote:
> Add missing devm_i2c_add_adapter() to devres.rst. It's introduced by
> commit 07740c92ae57 ("i2c: core: add managed function for adding i2c
> adapters").
>
> Fixes: 07740c92ae57 ("i2c: core: add managed function for adding i2c adapters")
> Cc: Yicong Yang <yangyicong@hisilicon.com>
I forgot to update the doc, sorry for that.
Acked-by: Yicong Yang <yangyicong@hisilicon.com>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Dmitry Osipenko <digetx@gmail.com>
> Cc: Wolfram Sang <wsa@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> Documentation/driver-api/driver-model/devres.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/driver-api/driver-model/devres.rst b/Documentation/driver-api/driver-model/devres.rst
> index 853396d19419..ec97261530da 100644
> --- a/Documentation/driver-api/driver-model/devres.rst
> +++ b/Documentation/driver-api/driver-model/devres.rst
> @@ -280,6 +280,7 @@ GPIO
>
> I2C
> devm_i2c_new_dummy_device()
> + devm_i2c_add_adapter()
>
> IIO
> devm_iio_device_alloc()
>
next prev parent reply other threads:[~2022-11-02 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 3:40 [PATCH] Documentation: devres: add missing I2C helper Yang Yingliang
2022-11-02 7:29 ` Yicong Yang [this message]
2022-11-02 10:38 ` Andy Shevchenko
2022-11-02 13:22 ` Yang Yingliang
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=bc4ad590-a051-f0d2-9f7d-c5ccb1ffee19@huawei.com \
--to=yangyicong@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=digetx@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyingliang@huawei.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