From: Raag Jadav <raag.jadav@intel.com>
To: jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, jsd@semihalf.com,
andi.shyti@kernel.org
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v1 2/2] i2c: designware: constify regmap_config
Date: Mon, 22 Jan 2024 09:01:08 +0530 [thread overview]
Message-ID: <20240122033108.31053-2-raag.jadav@intel.com> (raw)
In-Reply-To: <20240122033108.31053-1-raag.jadav@intel.com>
We never modify regmap_config, mark it as const.
Signed-off-by: Raag Jadav <raag.jadav@intel.com>
---
drivers/i2c/busses/i2c-designware-platdrv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
index 855b698e99c0..d122ef349b1c 100644
--- a/drivers/i2c/busses/i2c-designware-platdrv.c
+++ b/drivers/i2c/busses/i2c-designware-platdrv.c
@@ -100,7 +100,7 @@ static int bt1_i2c_write(void *context, unsigned int reg, unsigned int val)
BT1_I2C_CTL_GO | BT1_I2C_CTL_WR | (reg & BT1_I2C_CTL_ADDR_MASK));
}
-static struct regmap_config bt1_i2c_cfg = {
+static const struct regmap_config bt1_i2c_cfg = {
.reg_bits = 32,
.val_bits = 32,
.reg_stride = 4,
--
2.35.3
next prev parent reply other threads:[~2024-01-22 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 3:31 [PATCH v1 1/2] i2c: designware: constify abort_sources Raag Jadav
2024-01-22 3:31 ` Raag Jadav [this message]
2024-01-22 9:44 ` [PATCH v1 2/2] i2c: designware: constify regmap_config Jarkko Nikula
2024-02-08 10:46 ` Raag Jadav
2024-03-04 7:58 ` Raag Jadav
2024-10-02 9:18 ` [PATCH v1 1/2] i2c: designware: constify abort_sources Andi Shyti
2024-10-03 2:58 ` Raag Jadav
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=20240122033108.31053-2-raag.jadav@intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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