linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Enrico Jorns <ejo@pengutronix.de>
Cc: linux-mmc@vger.kernel.org, Avri Altman <avri.altman@wdc.com>
Subject: Re: [PATCH 3/3] mmc-utils: do not hide CID manufacturer information
Date: Wed, 24 May 2023 17:15:51 +0200	[thread overview]
Message-ID: <CAPDyKFoKYO867PDW+DmFaZZs2ecdx4zYJXa_CGvoRKWvcsMsew@mail.gmail.com> (raw)
In-Reply-To: <20230522214818.2038252-3-ejo@pengutronix.de>

On Mon, 22 May 2023 at 23:49, Enrico Jorns <ejo@pengutronix.de> wrote:
>
> Reading the MID just to convert it to 'Unlisted' is quite unhelpful for
> an info command.
> Due to the (constantly increasing) amount of valid MIDs it is quite
> unlikely to we have it in the database already anyway.
>
> Thus simply always print the manufacturer ID as 0xNN and understand the
> manufacturer name as an additional information held in parenthesis.
>
> Signed-off-by: Enrico Jorns <ejo@pengutronix.de>

Applied to git.kernel.org/pub/scm/utils/mmc/mmc-utils.git master, thanks!

Kind regards
Uffe


> ---
>  lsmmc.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lsmmc.c b/lsmmc.c
> index cea43af..54c3167 100644
> --- a/lsmmc.c
> +++ b/lsmmc.c
> @@ -636,10 +636,10 @@ void print_mmc_cid(struct config *config, char *cid)
>                 printf("\tCRC: 0x%02x\n", crc);
>         } else {
>                 if (config->mmc_ids[mid])
> -                       printf("manufacturer: '%s' 0x%01x\n",
> -                              config->mmc_ids[mid], oid);
> +                       printf("manufacturer: 0x%02x (%s) oid: 0x%01x\n",
> +                              mid, config->mmc_ids[mid], oid);
>                 else
> -                       printf("manufacturer: 'Unlisted' 0x%01x\n", oid);
> +                       printf("manufacturer: 0x%02x (Unlisted) oid: 0x%01x\n", mid, oid);
>
>                 printf("product: '%s' %u.%u\n", pnm, prv_major, prv_minor);
>                 printf("serial: 0x%08x\n", psn);
> --
> 2.39.2
>

  parent reply	other threads:[~2023-05-24 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 21:48 [PATCH 1/3] mmc-utils: add SanDisk to manufacturer database Enrico Jorns
2023-05-22 21:48 ` [PATCH 2/3] mmc-utils: fix printing OID for mmc in non-verbose mode Enrico Jorns
2023-05-24  6:45   ` Avri Altman
2023-05-24 15:15   ` Ulf Hansson
2023-05-22 21:48 ` [PATCH 3/3] mmc-utils: do not hide CID manufacturer information Enrico Jorns
2023-05-24  6:48   ` Avri Altman
2023-05-24 15:15   ` Ulf Hansson [this message]
2023-05-24  6:41 ` [PATCH 1/3] mmc-utils: add SanDisk to manufacturer database Avri Altman
2023-05-24 15:15 ` 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=CAPDyKFoKYO867PDW+DmFaZZs2ecdx4zYJXa_CGvoRKWvcsMsew@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=avri.altman@wdc.com \
    --cc=ejo@pengutronix.de \
    --cc=linux-mmc@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;
as well as URLs for NNTP newsgroup(s).