From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: nattan <nattanferreira58@gmail.com>
Cc: subhajit.ghosh@tweaklogic.com, jic23@kernel.org,
Lucas Antonio <lucasantonio.santos@usp.br>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: light: apds9306: Refactor threshold get/set functions to use helper
Date: Tue, 3 Jun 2025 22:33:23 -0300 [thread overview]
Message-ID: <aD-iY4aUWTcv1etN@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20250526235906.6598-1-nattanferreira58@gmail.com>
Hello Nattan, Lucas,
This version looks good to me.
One minor thing below.
On 05/26, nattan wrote:
> From: Nattan Ferreira <nattanferreira58@gmail.com>
>
> Refactor the apds9306_event_thresh_get and apds9306_event_thresh_set
> functions to use a helper function (apds9306_get_thresh_reg) for obtaining the
nitpicking: commit message and description are wrapped to 75 columns.
> correct register based on the direction of the event. This improves code
> readability and maintains consistency
I think part of the description from the line below could also fit into the line above.
> in accessing threshold registers.
>
> Signed-off-by: Nattan Ferreira <nattanferreira58@gmail.com>
> Co-developed-by: Lucas Antonio <lucasantonio.santos@usp.br>
> Signed-off-by: Lucas Antonio <lucasantonio.santos@usp.br>
> ---
Friendly reminder to add a change log below the --- if you send a v4 (or v5?).
> drivers/iio/light/apds9306.c | 36 ++++++++++++++++++++----------------
> 1 file changed, 20 insertions(+), 16 deletions(-)
>
Regards,
Marcelo
next prev parent reply other threads:[~2025-06-04 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 23:59 [PATCH v3] iio: light: apds9306: Refactor threshold get/set functions to use helper nattan
2025-05-31 17:23 ` Jonathan Cameron
2025-06-05 18:55 ` Nattan Ferreira
2025-06-04 1:33 ` Marcelo Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-22 19:11 nattan
2025-04-24 13:04 ` Subhajit Ghosh
2025-05-26 23:33 ` Nattan Ferreira
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=aD-iY4aUWTcv1etN@debian-BULLSEYE-live-builder-AMD64 \
--to=marcelo.schmitt1@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lucasantonio.santos@usp.br \
--cc=nattanferreira58@gmail.com \
--cc=subhajit.ghosh@tweaklogic.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