From: Heiko Stuebner <heiko@sntech.de>
To: Srinivas Kandagatla <srini@kernel.org>, Felix Gu <ustc.gu@gmail.com>
Cc: linux-kernel@vger.kernel.org, Felix Gu <ustc.gu@gmail.com>
Subject: Re: [PATCH] nvmem: qnap-mcu-eeprom: Fix struct assignments using commas instead of semicolons
Date: Mon, 02 Mar 2026 12:15:23 +0100 [thread overview]
Message-ID: <10809879.nUPlyArG6x@phil> (raw)
In-Reply-To: <20260301-qnap-v1-1-8131c9b2d118@gmail.com>
Am Sonntag, 1. März 2026, 10:51:16 Mitteleuropäische Normalzeit schrieb Felix Gu:
> 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>
I wonder how I managed to make that mistake :-)
Thanks for noticing
Heiko
> ---
> 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))
>
> ---
> base-commit: 3fa5e5702a82d259897bd7e209469bc06368bf31
> change-id: 20260301-qnap-f91e2ca99aab
>
> Best regards,
>
next prev parent reply other threads:[~2026-03-02 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 9:51 [PATCH] nvmem: qnap-mcu-eeprom: Fix struct assignments using commas instead of semicolons Felix Gu
2026-03-02 11:15 ` Heiko Stuebner [this message]
2026-03-03 9:25 ` Markus Elfring
2026-03-11 11:33 ` Srinivas Kandagatla
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=10809879.nUPlyArG6x@phil \
--to=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@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