Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-doc@vger.kernel.org>, <linux-iio@vger.kernel.org>,
	<Jonathan.Cameron@huawei.com>, <corbet@lwn.net>
Subject: Re: [PATCH RESEND] Documentation: devres: add missing IIO helpers
Date: Sat, 5 Nov 2022 15:08:12 +0000	[thread overview]
Message-ID: <20221105150812.66d81f40@jic23-huawei> (raw)
In-Reply-To: <20221103023402.1024437-1-yangyingliang@huawei.com>

On Thu, 3 Nov 2022 10:34:02 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:

> Add some missing device-managed helpers of iio to devres.rst.
> 
> devm_iio_kfifo_buffer_setup_ext() is introduced by commit 0a21526bc1d4 ("iio:
> kfifo: add devm_iio_triggered_buffer_setup_ext variant").
> 
> devm_iio_triggered_buffer_setup_ext() is introduced by commit 5164c7889857 ("iio:
> triggered-buffer: add {devm_}iio_triggered_buffer_setup_ext variants").
> 
> devm_iio_hw_consumer_alloc() is introduced by b688c18d3006 ("IIO: hw_consumer:
> add devm_iio_hw_consumer_alloc").
> 
> devm_fwnode_iio_channel_get_by_name() is introduced by commit 1e64b9c5f9a0 ("iio:
> inkern: move to fwnode properties").
> 
> Fixes: 0a21526bc1d4 ("iio: kfifo: add devm_iio_triggered_buffer_setup_ext variant")
> Fixes: 5164c7889857 ("iio: triggered-buffer: add {devm_}iio_triggered_buffer_setup_ext variants")
> Fixes: b688c18d3006 ("IIO: hw_consumer: add devm_iio_hw_consumer_alloc")
> Fixes: 1e64b9c5f9a0 ("iio: inkern: move to fwnode properties")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
You didn't pick up my

Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

or mention that my assumption is that this will go via the docs tree.

Thanks,

Jonathan

> ---
> The previous patch link:
> https://patchwork.kernel.org/project/linux-iio/patch/20220927074043.942836-1-yangyingliang@huawei.com/
> ---
>  Documentation/driver-api/driver-model/devres.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/driver-api/driver-model/devres.rst b/Documentation/driver-api/driver-model/devres.rst
> index e0cb7df0f782..4249eb4239e0 100644
> --- a/Documentation/driver-api/driver-model/devres.rst
> +++ b/Documentation/driver-api/driver-model/devres.rst
> @@ -287,12 +287,16 @@ IIO
>    devm_iio_device_register()
>    devm_iio_dmaengine_buffer_setup()
>    devm_iio_kfifo_buffer_setup()
> +  devm_iio_kfifo_buffer_setup_ext()
>    devm_iio_map_array_register()
>    devm_iio_triggered_buffer_setup()
> +  devm_iio_triggered_buffer_setup_ext()
>    devm_iio_trigger_alloc()
>    devm_iio_trigger_register()
>    devm_iio_channel_get()
>    devm_iio_channel_get_all()
> +  devm_iio_hw_consumer_alloc()
> +  devm_fwnode_iio_channel_get_by_name()
>  
>  INPUT
>    devm_input_allocate_device()


  reply	other threads:[~2022-11-05 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  2:34 [PATCH RESEND] Documentation: devres: add missing IIO helpers Yang Yingliang
2022-11-05 15:08 ` Jonathan Cameron [this message]
2022-11-07  1:25   ` Yang Yingliang
2022-11-07 16:46     ` Jonathan Cameron
2022-11-09 21:01 ` Jonathan Corbet

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=20221105150812.66d81f40@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --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