From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Ulf Hansson <ulf.hansson@linaro.org>, <linux-mmc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mmc: core: Normalize the error handling branch in sd_read_ext_regs()
Date: Wed, 30 Nov 2022 21:53:30 +0800 [thread overview]
Message-ID: <a111e3ab-c5ef-4cfb-5fae-99619c0840d9@huawei.com> (raw)
In-Reply-To: <20221130134920.2109-1-thunder.leizhen@huawei.com>
On 2022/11/30 21:49, Zhen Lei wrote:
> 1. Use pr_err() to output the error message.
> 2. Add the description of why success 0 is returned in case
> "non-supported SD ext reg layout".
>
> Fixes: c784f92769ae ("mmc: core: Read the SD function extension registers for power management")
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> drivers/mmc/core/sd.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
Sorry, I forgot to add the version difference description.
v1 --> v2:
Add a description instead of returning an error code.
v1:
https://lkml.org/lkml/2022/11/30/240
>
> diff --git a/drivers/mmc/core/sd.c b/drivers/mmc/core/sd.c
> index 3662bf5320ce56d..93ee53f74427c38 100644
> --- a/drivers/mmc/core/sd.c
> +++ b/drivers/mmc/core/sd.c
> @@ -1259,7 +1259,7 @@ static int sd_read_ext_regs(struct mmc_card *card)
> */
> err = sd_read_ext_reg(card, 0, 0, 0, 512, gen_info_buf);
> if (err) {
> - pr_warn("%s: error %d reading general info of SD ext reg\n",
> + pr_err("%s: error %d reading general info of SD ext reg\n",
> mmc_hostname(card->host), err);
> goto out;
> }
> @@ -1273,7 +1273,12 @@ static int sd_read_ext_regs(struct mmc_card *card)
> /* Number of extensions to be find. */
> num_ext = gen_info_buf[4];
>
> - /* We support revision 0, but limit it to 512 bytes for simplicity. */
> + /*
> + * We only support revision 0, and limit it to 512 bytes for simplicity.
> + * In other cases, success 0 is returned, because the card remains
> + * functional and all but the new features from the SD function
> + * extensions registers can still be used.
> + */
> if (rev != 0 || len > 512) {
> pr_warn("%s: non-supported SD ext reg layout\n",
> mmc_hostname(card->host));
> @@ -1288,7 +1293,7 @@ static int sd_read_ext_regs(struct mmc_card *card)
> for (i = 0; i < num_ext; i++) {
> err = sd_parse_ext_reg(card, gen_info_buf, &next_ext_addr);
> if (err) {
> - pr_warn("%s: error %d parsing SD ext reg\n",
> + pr_err("%s: error %d parsing SD ext reg\n",
> mmc_hostname(card->host), err);
> goto out;
> }
>
--
Regards,
Zhen Lei
next prev parent reply other threads:[~2022-11-30 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 13:49 Zhen Lei
2022-11-30 13:53 ` Leizhen (ThunderTown) [this message]
2022-11-30 14:43 ` Ulf Hansson
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=a111e3ab-c5ef-4cfb-5fae-99619c0840d9@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®