From: Michael Walle <michael@walle.cc>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Jaime Liao <jaimeliao.tw@gmail.com>,
linux-mtd@lists.infradead.org, tudor.ambarus@linaro.org,
pratyush@kernel.org, leoyu@mxic.com.tw, jaimeliao@mxic.com.tw
Subject: Re: [PATCH v1 0/2] Hide flash name if it is not set
Date: Mon, 27 Nov 2023 12:58:27 +0100 [thread overview]
Message-ID: <70b6b105435d891e937a36657fa5debc@walle.cc> (raw)
In-Reply-To: <20231127124948.163224cc@xps-13>
Hi,
>> hide flash name if it is not set
>
> Is this really needed? I'm fine exposing en empty (or "(null)") name. I
> guess it shows to people that the name might be missing somewhere and
> might push people to fix the name instead.
>
> What's your use case?
An empty string is not a bug. I'm trying to push the part names out of
the kernel and just expose the jedec id.
That being said, the description is really missing the point. See my
previous suggestion:
The attribute is optional. User space shouldn't rely on it to
be present or even correct. Instead, user space should read the
jedec_id attribute.
-michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-11-27 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 10:07 [PATCH v1 0/2] Hide flash name if it is not set Jaime Liao
2023-11-27 10:07 ` [PATCH v1 1/2] mtd: spi-nor:sysfs: hide " Jaime Liao
2023-11-27 10:07 ` [PATCH v1 2/2] mtd: spi-nor: hide flash name when the flash name does not exist Jaime Liao
2023-11-27 12:21 ` Michael Walle
2023-11-27 14:47 ` Miquel Raynal
2023-11-27 14:56 ` Michael Walle
2023-11-27 15:21 ` Tudor Ambarus
2023-11-27 15:28 ` Michael Walle
2023-11-27 17:06 ` Tudor Ambarus
2023-11-27 11:49 ` [PATCH v1 0/2] Hide flash name if it is not set Miquel Raynal
2023-11-27 11:58 ` Michael Walle [this message]
2023-11-27 12:03 ` Tudor Ambarus
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=70b6b105435d891e937a36657fa5debc@walle.cc \
--to=michael@walle.cc \
--cc=jaimeliao.tw@gmail.com \
--cc=jaimeliao@mxic.com.tw \
--cc=leoyu@mxic.com.tw \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=tudor.ambarus@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