From: Roger Quadros <rogerq@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
MD Danish Anwar <danishanwar@ti.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] net: ti: icss-iep: constify struct regmap_config
Date: Thu, 4 Jul 2024 17:42:56 +0300 [thread overview]
Message-ID: <ae1447c3-6e91-410f-9a3b-142e4da5f6d8@kernel.org> (raw)
In-Reply-To: <20240703-net-const-regmap-v1-2-ff4aeceda02c@gmail.com>
On 04/07/2024 00:46, Javier Carrasco wrote:
> `am654_icss_iep_regmap_config` is only assigned to a pointer that passes
> the data as read-only.
>
> Add the const modifier to the struct and pointer to move the data to a
> read-only section.
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
next prev parent reply other threads:[~2024-07-04 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 21:46 [PATCH 0/4] net: constify struct regmap_bus/regmap_config Javier Carrasco
2024-07-03 21:46 ` [PATCH 1/4] net: dsa: qca8k: constify struct regmap_config Javier Carrasco
2024-07-04 17:33 ` Vladimir Oltean
2024-07-03 21:46 ` [PATCH 2/4] net: ti: icss-iep: " Javier Carrasco
2024-07-04 14:42 ` Roger Quadros [this message]
2024-07-05 4:41 ` MD Danish Anwar
2024-07-03 21:46 ` [PATCH 3/4] net: encx24j600: constify struct regmap_bus/regmap_config Javier Carrasco
2024-07-03 21:46 ` [PATCH 4/4] net: dsa: ar9331: constify struct regmap_bus Javier Carrasco
2024-07-04 17:30 ` Vladimir Oltean
2024-07-06 0:10 ` [PATCH 0/4] net: constify struct regmap_bus/regmap_config patchwork-bot+netdevbpf
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=ae1447c3-6e91-410f-9a3b-142e4da5f6d8@kernel.org \
--to=rogerq@kernel.org \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).