From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org>
Cc: <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 0/8] iio: add new backend framework
Date: Sun, 21 Jan 2024 17:57:24 +0000 [thread overview]
Message-ID: <20240121175724.76ff9be3@jic23-huawei> (raw)
In-Reply-To: <20240119-iio-backend-v6-0-189536c35a05@analog.com>
On Fri, 19 Jan 2024 17:00:46 +0100
Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> wrote:
> Changes in v6:
> - Patch 2
> * Add '#io-backends-cells' property to the example dts.
> - Patch 6
> * Improve comment on struct iio_backend_buffer_pair;
> * Be consistent with dots in kernel-docs. So dots only exist now in
> description and return. Also be consistent on device managed APIs
> subject and @dev description;
> * Added devm_iio_backend_enable() and hence (and for now)
> iio_backend_disable is static;
> * Fixed __devm_iio_backend_get_from_fwnode_lookup() kernel-doc;
> * Improved english in devm_iio_backend_register() comment;
> * Don't make private data mandatory;
> - Patch 7
> * Use local ad9467_chip_info *info variable;
> * Improve error handling for optional devm_iio_backend_get();
> * Make use of devm_iio_backend_enable().
> - Patch 8
> * Also change string format in version error path.
Hi Nuno,
Other than wanting a few acks (one for 2nd DT patch with the fix and one
for the device link changes) this looks good to me.
Ideally of course I'd like to see the second user if that happens to be
available in the first few weeks of this cycle, but I don't propose to hold
this indefinitely to wait for additional users as the framework seems logical
and it's all in kernel anyway so we can probably change whatever is needed
later without too much trouble.
Jonathan
>
next prev parent reply other threads:[~2024-01-21 17:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 16:00 [PATCH v6 0/8] iio: add new backend framework Nuno Sa via B4 Relay
2024-01-19 16:00 ` [PATCH v6 1/8] dt-bindings: adc: ad9467: add new io-backend property Nuno Sa via B4 Relay
2024-01-19 17:15 ` Rob Herring
2024-01-22 15:37 ` Rob Herring
2024-01-22 16:01 ` Nuno Sá
2024-01-22 19:16 ` Jonathan Cameron
2024-01-19 16:00 ` [PATCH v6 2/8] dt-bindings: adc: axi-adc: update bindings for backend framework Nuno Sa via B4 Relay
2024-01-19 17:15 ` Rob Herring
2024-01-21 17:17 ` Jonathan Cameron
2024-01-22 15:34 ` Rob Herring
2024-01-22 19:18 ` Jonathan Cameron
2024-01-19 16:00 ` [PATCH v6 3/8] driver: core: allow modifying device_links flags Nuno Sa via B4 Relay
2024-01-21 17:20 ` Jonathan Cameron
2024-01-19 16:00 ` [PATCH v6 4/8] of: property: add device link support for io-backends Nuno Sa via B4 Relay
2024-01-19 16:00 ` [PATCH v6 5/8] iio: buffer-dmaengine: export buffer alloc and free functions Nuno Sa via B4 Relay
2024-01-19 16:00 ` [PATCH v6 6/8] iio: add the IIO backend framework Nuno Sa via B4 Relay
2024-01-19 16:00 ` [PATCH v6 7/8] iio: adc: ad9467: convert to " Nuno Sa via B4 Relay
2024-01-21 17:52 ` Jonathan Cameron
2024-01-22 8:33 ` Nuno Sá
2024-01-19 16:00 ` [PATCH v6 8/8] iio: adc: adi-axi-adc: move " Nuno Sa via B4 Relay
2024-01-21 17:57 ` Jonathan Cameron [this message]
2024-01-22 8:36 ` [PATCH v6 0/8] iio: add new " Nuno Sá
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=20240121175724.76ff9be3@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+nuno.sa.analog.com@kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).