From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: matthias.bgg@gmail.com, fchiby@baylibre.com,
fparent@baylibre.com, s.hauer@pengutronix.de,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 0/3] soc: mediatek: pwrap: Constify some data and other improvements
Date: Tue, 30 Jul 2024 10:57:34 +0200 [thread overview]
Message-ID: <172232985478.56643.13436869801664543083.b4-ty@collabora.com> (raw)
In-Reply-To: <cover.1720331018.git.christophe.jaillet@wanadoo.fr>
On Sun, 07 Jul 2024 07:47:19 +0200, Christophe JAILLET wrote:
> This series is motivated by patch 1. The 2 other patches are some
> additionnal goodies spotted while looking at the code.
>
> Patch 1 constifies struct pmic_wrapper_type to move some data to a
> read-only section, in order to increase safety.
>
> Patch 2 does the same for some int arrays. This helps move about 7 ko of
> data to a read-only section. Not that bad!
>
> [...]
Applied to v6.11-next/soc, thanks!
[1/3] soc: mediatek: pwrap: Constify struct pmic_wrapper_type
commit: ded525f8ac5db53286b0eabb679ecf7edb974eaa
[2/3] soc: mediatek: pwrap: Constify some struct int[]
commit: 10c1ea1eaf4d107c323321e92237ba67848de291
[3/3] soc: mediatek: pwrap: Use devm_clk_bulk_get_all_enable()
commit: 1c28c9452d521bf21dc5d2c50a47c2e43002728d
Cheers,
Angelo
prev parent reply other threads:[~2024-07-30 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 5:47 Christophe JAILLET
2024-07-07 5:47 ` [PATCH v2 1/3] soc: mediatek: pwrap: Constify struct pmic_wrapper_type Christophe JAILLET
2024-07-07 5:47 ` [PATCH v2 2/3] soc: mediatek: pwrap: Constify some struct int[] Christophe JAILLET
2024-07-07 5:47 ` [PATCH v2 3/3] soc: mediatek: pwrap: Use devm_clk_bulk_get_all_enable() Christophe JAILLET
2024-07-30 8:57 ` AngeloGioacchino Del Regno [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=172232985478.56643.13436869801664543083.b4-ty@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=fchiby@baylibre.com \
--cc=fparent@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--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=s.hauer@pengutronix.de \
/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
all inboxes | Powered by JetHome®