From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Michael Turquette <mturquette@baylibre.com>,
Michal Simek <michal.simek@amd.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Samuel Holland <samuel@sholland.org>,
Vladimir Zapolskiy <vz@mleia.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-sunxi@lists.linux.dev,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH 07/10] clk: lpc32xx: Constify struct regmap_config
Date: Mon, 08 Jul 2024 13:32:51 -0700 [thread overview]
Message-ID: <ee7380278b81195fbaac652c99c29936.sboyd@kernel.org> (raw)
In-Reply-To: <20240703-clk-const-regmap-v1-7-7d15a0671d6f@gmail.com>
Quoting Javier Carrasco (2024-07-03 02:50:20)
> `lpc32xx_scb_regmap_config` is not modified and can be declared as const
> to move its data to a read-only section.
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2024-07-08 20:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 9:50 [PATCH 00/10] clk: constify struct regmap_config Javier Carrasco
2024-07-03 9:50 ` [PATCH 01/10] clk: meson: a1: peripherals: Constify " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-15 12:08 ` [DMARC error][DKIM error] " Dmitry Rokosov
2024-07-03 9:50 ` [PATCH 02/10] clk: meson: a1: pll: " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-15 12:10 ` [DMARC error][DKIM error] " Dmitry Rokosov
2024-07-03 9:50 ` [PATCH 03/10] clk: meson: c3: peripherals: " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-03 9:50 ` [PATCH 04/10] clk: meson: c3: pll: " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-03 9:50 ` [PATCH 05/10] clk: meson: s4: peripherals: " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-03 9:50 ` [PATCH 06/10] clk: meson: s4: pll: " Javier Carrasco
2024-07-03 10:54 ` Neil Armstrong
2024-07-03 9:50 ` [PATCH 07/10] clk: lpc32xx: " Javier Carrasco
2024-07-08 20:32 ` Stephen Boyd [this message]
2024-07-03 9:50 ` [PATCH 08/10] clk: qcom: lpasscc-sc8280xp: " Javier Carrasco
2024-07-03 10:50 ` Dmitry Baryshkov
2024-07-03 9:50 ` [PATCH 09/10] clk: sunxi-ng r40: " Javier Carrasco
2024-07-03 11:17 ` Andre Przywara
2024-07-10 16:53 ` Chen-Yu Tsai
2024-07-10 19:47 ` Stephen Boyd
2024-07-03 9:50 ` [PATCH 10/10] clk: xilinx: " Javier Carrasco
2024-07-08 20:32 ` Stephen Boyd
2024-07-06 22:01 ` (subset) [PATCH 00/10] clk: constify " Bjorn Andersson
2024-07-10 12:41 ` Jerome Brunet
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=ee7380278b81195fbaac652c99c29936.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=andersson@kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=jernej.skrabec@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=samuel@sholland.org \
--cc=vz@mleia.com \
--cc=wens@csie.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