linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: "Cosmin Tanislav" <cosmin.tanislav@analog.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Dan Robertson" <dan@dlrobertson.com>,
	"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Jagath Jog J" <jagathjog1996@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH 03/10] iio: accel: bmi088: Constify struct regmap_bus
Date: Wed, 03 Jul 2024 23:04:46 +0200	[thread overview]
Message-ID: <20240703-iio-cont-regmap_bus-v1-3-34754f355b65@gmail.com> (raw)
In-Reply-To: <20240703-iio-cont-regmap_bus-v1-0-34754f355b65@gmail.com>

`bmi088_regmap_bus` 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>
---
 drivers/iio/accel/bmi088-accel-spi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/accel/bmi088-accel-spi.c b/drivers/iio/accel/bmi088-accel-spi.c
index 7b419a7b2478..df1adc059aa9 100644
--- a/drivers/iio/accel/bmi088-accel-spi.c
+++ b/drivers/iio/accel/bmi088-accel-spi.c
@@ -36,7 +36,7 @@ static int bmi088_regmap_spi_read(void *context, const void *reg,
 	return spi_write_then_read(spi, addr, sizeof(addr), val, val_size);
 }
 
-static struct regmap_bus bmi088_regmap_bus = {
+static const struct regmap_bus bmi088_regmap_bus = {
 	.write = bmi088_regmap_spi_write,
 	.read = bmi088_regmap_spi_read,
 };

-- 
2.40.1


  parent reply	other threads:[~2024-07-03 21:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 21:04 [PATCH 00/10] iio: Constify struct regmap_bus Javier Carrasco
2024-07-03 21:04 ` [PATCH 01/10] iio: accel: adxl367: " Javier Carrasco
2024-07-03 21:04 ` [PATCH 02/10] iio: accel: bma400: " Javier Carrasco
2024-07-03 21:04 ` Javier Carrasco [this message]
2024-07-03 21:04 ` [PATCH 04/10] iio: adc: ad7091r8: " Javier Carrasco
2024-07-04 11:16   ` Nuno Sá
2024-07-04 13:04   ` Schmitt, Marcelo
2024-07-03 21:04 ` [PATCH 05/10] iio: chemical: bme680: " Javier Carrasco
2024-07-06 10:51   ` [PATCH 05/10]: " Vasileios Amoiridis
2024-07-07 15:24     ` Jonathan Cameron
2024-07-03 21:04 ` [PATCH 06/10] iio: dac: ltc2688: " Javier Carrasco
2024-07-04  7:13   ` Nuno Sá
2024-07-03 21:04 ` [PATCH 07/10] iio: imu: bmi323: " Javier Carrasco
2024-07-03 21:04 ` [PATCH 08/10] iio: imu: bno055: " Javier Carrasco
2024-07-03 21:04 ` [PATCH 09/10] iio: light: gp2ap002: " Javier Carrasco
2024-07-03 21:04 ` [PATCH 10/10] iio: pressure: bmp280: " Javier Carrasco
2024-07-06 10:54   ` [PATCH 10/10]: " Vasileios Amoiridis
2024-07-06 10:43 ` [PATCH 00/10] iio: " Jonathan Cameron

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=20240703-iio-cont-regmap_bus-v1-3-34754f355b65@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=cosmin.tanislav@analog.com \
    --cc=dan@dlrobertson.com \
    --cc=jagathjog1996@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt@analog.com \
    --cc=nuno.sa@analog.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).