From: srini@kernel.org
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Felix Gu <ustc.gu@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
Srinivas Kandagatla <srini@kernel.org>
Subject: [PATCH 2/9] nvmem: qnap-mcu-eeprom: Fix struct assignments using commas instead of semicolons
Date: Fri, 27 Mar 2026 13:17:44 +0000 [thread overview]
Message-ID: <20260327131751.3026030-3-srini@kernel.org> (raw)
In-Reply-To: <20260327131751.3026030-1-srini@kernel.org>
From: Felix Gu <ustc.gu@gmail.com>
The nvcfg struct member assignments were incorrectly using commas instead
of semicolons.
Signed-off-by: Felix Gu <ustc.gu@gmail.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Srinivas Kandagatla <srini@kernel.org>
---
drivers/nvmem/qnap-mcu-eeprom.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/nvmem/qnap-mcu-eeprom.c b/drivers/nvmem/qnap-mcu-eeprom.c
index 0b919895b3b2..07bdaa2a33fa 100644
--- a/drivers/nvmem/qnap-mcu-eeprom.c
+++ b/drivers/nvmem/qnap-mcu-eeprom.c
@@ -86,10 +86,10 @@ static int qnap_mcu_eeprom_probe(struct platform_device *pdev)
nvcfg.read_only = true;
nvcfg.root_only = false;
nvcfg.reg_read = qnap_mcu_eeprom_read;
- nvcfg.size = QNAP_MCU_EEPROM_SIZE,
- nvcfg.word_size = 1,
- nvcfg.stride = 1,
- nvcfg.priv = mcu,
+ nvcfg.size = QNAP_MCU_EEPROM_SIZE;
+ nvcfg.word_size = 1;
+ nvcfg.stride = 1;
+ nvcfg.priv = mcu;
ndev = devm_nvmem_register(&pdev->dev, &nvcfg);
if (IS_ERR(ndev))
--
2.47.3
next prev parent reply other threads:[~2026-03-27 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 13:17 [PATCH 0/9] nvmem: patches (set 1) for 7.1 srini
2026-03-27 13:17 ` [PATCH 1/9] dt-bindings: nvmem: qfprom: Add Kaanapali compatible srini
2026-03-27 13:17 ` srini [this message]
2026-03-27 13:17 ` [PATCH 3/9] dt-bindings: nvmem: sl28cpld: Drop sa67mcu compatible srini
2026-03-27 13:17 ` [PATCH 4/9] dt-bindings: nvmem: rockchip,otp: Add support for RK3562 and RK3568 srini
2026-03-27 13:17 ` [PATCH 5/9] dt-bindings: nvmem: rockchip,otp: Add compatible for RK3528 srini
2026-03-27 13:17 ` [PATCH 6/9] nvmem: rockchip-otp: Handle internal word_size in main reg_read op srini
2026-03-27 13:17 ` [PATCH 7/9] nvmem: rockchip-otp: Add support for RK3568 srini
2026-03-27 13:17 ` [PATCH 8/9] nvmem: rockchip-otp: Add support for RK3562 srini
2026-03-27 13:17 ` [PATCH 9/9] nvmem: rockchip-otp: Add support for RK3528 srini
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=20260327131751.3026030-3-srini@kernel.org \
--to=srini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ustc.gu@gmail.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