From: Greg KH <gregkh@linuxfoundation.org>
To: Tian <27392025k@gmail.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH] misc: cardreader: fix overwritten return value in RTS5260 driver
Date: Mon, 28 Jul 2025 06:21:59 +0200 [thread overview]
Message-ID: <2025072844-stingray-eskimo-9422@gregkh> (raw)
In-Reply-To: <20250727234134.26540-1-27392025k@gmail.com>
On Sun, Jul 27, 2025 at 04:41:34PM -0700, Tian wrote:
> In both rts5260.c and rtsx_pcr.c, a return value is set and then
> overwritten by a later function call, which makes the original value
> unused. This patch ensures the return value is handled properly
> to avoid ignoring possible error conditions.
>
> Signed-off-by: Tian <27392025k@gmail.com>
Please use your ful name as per the kernel documentation.
> ---
> drivers/misc/cardreader/rts5260.c | 2 +-
> drivers/misc/cardreader/rtsx_pcr.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/cardreader/rts5260.c b/drivers/misc/cardreader/rts5260.c
> index d2d3a6ccb8f7..ed8adaab54a8 100644
> --- a/drivers/misc/cardreader/rts5260.c
> +++ b/drivers/misc/cardreader/rts5260.c
> @@ -269,7 +269,7 @@ static int rts5260_card_power_off(struct rtsx_pcr *pcr, int card)
> rts5260_card_before_power_off(pcr);
> err = rtsx_pci_write_register(pcr, LDO_VCC_CFG1,
> LDO_POW_SDVDD1_MASK, LDO_POW_SDVDD1_OFF);
> - err = rtsx_pci_write_register(pcr, LDO_CONFIG2,
> + err |= rtsx_pci_write_register(pcr, LDO_CONFIG2,
> DV331812_POWERON, DV331812_POWEROFF);
How was this tested?
And why do the second write if the first one failed?
> if (pcr->option.ocp_en)
> rtsx_pci_disable_ocp(pcr);
Why do this if the write failed?
> diff --git a/drivers/misc/cardreader/rtsx_pcr.c b/drivers/misc/cardreader/rtsx_pcr.c
> index a7b066c48740..9fb22f2cedbd 100644
> --- a/drivers/misc/cardreader/rtsx_pcr.c
> +++ b/drivers/misc/cardreader/rtsx_pcr.c
> @@ -1196,7 +1196,7 @@ static int rtsx_pci_init_hw(struct rtsx_pcr *pcr)
> /* Gating real mcu clock */
> err = rtsx_pci_write_register(pcr, RTS5261_FW_CFG1,
> RTS5261_MCU_CLOCK_GATING, 0);
> - err = rtsx_pci_write_register(pcr, RTS5261_REG_FPDCTL,
> + err |= rtsx_pci_write_register(pcr, RTS5261_REG_FPDCTL,
> SSC_POWER_DOWN, 0);
Is this even going to ever happen? Same for above, how was this tested?
thanks,
greg k-h
prev parent reply other threads:[~2025-07-28 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 23:41 [PATCH] misc: cardreader: fix overwritten return value in RTS5260 driver Tian
2025-07-28 4:21 ` Greg KH [this message]
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=2025072844-stingray-eskimo-9422@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=27392025k@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
/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