Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Samuel Kayode <samkay014@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 0/8] regulator: Use container_of_const() when all types are const
Date: Thu, 27 Nov 2025 08:51:08 +0200	[thread overview]
Message-ID: <f4d4169d-796b-49fd-b4d3-b74186e59b82@gmail.com> (raw)
In-Reply-To: <20251126-container-of-const-regulator-v2-0-7ad3408d6f29@oss.qualcomm.com>

Thanks again Krzysztof! :)

On 26/11/2025 19:40, Krzysztof Kozlowski wrote:
> Changes in v2:
> - Rebase on regulator/for-next, which does not have pf1550-regulator.c
>    so drop this part.
> - Link to v1: https://patch.msgid.link/20251126-container-of-const-regulator-v1-0-eeec378144d4@oss.qualcomm.com
> 
> Use container_of_const(), which is preferred over container_of(), when
> the argument 'ptr' and returned pointer are already const, for better
> code safety and readability.
> 
> Some drivers already have const everywhere, so container_of_const can be
> directly used. In few other drivers, the final pointer can be constified
> that way.
> 
> Best regards,
> Krzysztof
> 
> ---
> Krzysztof Kozlowski (8):

>        regulator: bd71815: Constify pointers to 'regulator_desc' wrap struct
>        regulator: bd71828: Constify pointers to 'regulator_desc' wrap struct
>        regulator: bd718x7: Constify pointers to 'regulator_desc' wrap struct
>        regulator: bd96801: Constify pointers to 'regulator_desc' wrap struct

For the above:
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>

Yours,
	-- Matti

      parent reply	other threads:[~2025-11-27  6:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 17:40 [PATCH v2 0/8] regulator: Use container_of_const() when all types are const Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 1/8] " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 2/8] regulator: bd71815: Constify pointers to 'regulator_desc' wrap struct Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 3/8] regulator: bd71828: " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 4/8] regulator: bd718x7: " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 5/8] regulator: bd96801: " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 6/8] regulator: mt6358: " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 7/8] regulator: pca9450: " Krzysztof Kozlowski
2025-11-26 17:40 ` [PATCH v2 8/8] regulator: pf9453: " Krzysztof Kozlowski
2025-11-27  6:51 ` Matti Vaittinen [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=f4d4169d-796b-49fd-b4d3-b74186e59b82@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=brgl@kernel.org \
    --cc=broonie@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=samkay014@gmail.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