From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bertin Salvador <lorenzobs@usp.br>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/2] IIO: Use of device_for_each_child_node_scoped() in ti-ads131e08
Date: Sun, 21 Apr 2024 18:40:50 +0100 [thread overview]
Message-ID: <20240421184050.1f350636@jic23-huawei> (raw)
In-Reply-To: <20240420182744.153184-1-lorenzobs@usp.br>
On Sat, 20 Apr 2024 15:27:42 -0300
Lorenzo Bertin Salvador <lorenzobs@usp.br> wrote:
> This series is making use of device_for_each_child_node_scoped() to avoid
> the need to remember to call fwnode_handle_put() in early exits from
> loops over the child nodes. It is also correcting a minor style problem
> in drivers/iio/adc/ti-ads131e08.c
>
> Lorenzo Bertin Salvador (2):
> iio: adc: ti-ads131e08: Use device_for_each_child_node_scoped() to
> simplify error paths.
> iio: adc: ti-ads131e08: Fix a style problem in struct declaration.
The title of the cover letter only reflects one of these patches and
needs to cover them both. However, for tidying up type actions a vague
title like iio: adc: ti-ads131e08: code style improvements
would be fine as long as the description gives a more detailed listing
of what is going on. That's covered by your description above.
Thanks,
Jonathan
>
> drivers/iio/adc/ti-ads131e08.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2024-04-21 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 18:27 [PATCH 0/2] IIO: Use of device_for_each_child_node_scoped() in ti-ads131e08 Lorenzo Bertin Salvador
2024-04-20 18:27 ` [PATCH 1/2] iio: adc: ti-ads131e08: Use device_for_each_child_node_scoped() to simplify error paths Lorenzo Bertin Salvador
2024-04-21 17:43 ` Jonathan Cameron
2024-04-20 18:27 ` [PATCH 2/2] iio: adc: ti-ads131e08: Fix a style problem in struct declaration Lorenzo Bertin Salvador
2024-04-21 17:27 ` Jonathan Cameron
2024-04-21 17:40 ` 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=20240421184050.1f350636@jic23-huawei \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzobs@usp.br \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).