All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: E Shattow <e@freeshell.de>,  Marek Vasut <marex@nabladev.com>,
	Alexander Koch <akoch@initse.com>,
	 David Lechner <dlechner@baylibre.com>,
	 Flaviu Nistor <flaviu.nistor@gmail.com>,
	Takahiro Kuwano <takahiro.kuwano@infineon.com>,
	 Tom Rini <trini@konsulko.com>,
	 Tudor Ambarus <tudor.ambarus@linaro.org>,
	 Vignesh R <vigneshr@ti.com>,
	 u-boot@lists.u-boot-project.org
Subject: Re: [PATCH] mtd: spi-nor: Indent SF: just like other boot time messages
Date: Mon, 26 Oct 2026 09:25:51 +0100	[thread overview]
Message-ID: <87ik2oj2b4.fsf@bootlin.com> (raw)
In-Reply-To: <jwvqzhdho45.fsf-monnier+Inbox@gnu.org> (Stefan Monnier's message of "Sun, 25 Oct 2026 10:10:04 -0400")

On 25/10/2026 at 10:10:04 -04, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> E Shattow [2026-10-25 06:29:43] wrote:
>
>> On 10/24/26 11:05, Marek Vasut wrote:
>>> On 10/24/26 5:14 PM, Stefan Monnier wrote:
>>>>> to the fixed indent:
>>>>>
>>>>> "
>>>>> DRAM:  3.5 GiB
>>>>> Core:  310 devices, 34 uclasses, devicetree: separate
>>>>> SF:    Detected w25q128jw with page size 256 Bytes, erase size
>>>>> 4 KiB, total 16 MiB
>>>>>      ^^^
>>>>
>>>> I'm probably not the targeted audience, but FWIW, I find the meaning of
>>>> "SF" non-obvious, so maybe instead of adding spaces, we could use those
>>>> 3 extra characters to come up with a slightly more
>>>> self-explanatory abbreviation?
>>> SF is SPI Flash , it is used all over the code base.
>
> Yes, that's indeed how I figured what it meant, but it would be better
> if users could figure that out without having to consult the source code.
>
>> I also find the meaning of "SF" non-obvious, and nothing better comes to
>> mind to abbreviate it. You cannot get to "sf" command from "spi flash"
>> or "flash" commands. If the probe message would say "SPI [NOR|NAND]
>> Flash detected ...." or "SPI: [NOR|NAND] Flash detected ..." it would

Except sf is only about SPI NORs, not SPI NANDs. The tool has been here
for ages, it is light, but very limited (single chip, spi nor
only). People may use the mtd tool instead, which is much heavier
(requires the mtd layer which is optional) but flash/bus agnostic. All
this to say, I don't know how to make a better shortcut for it, and yes
this acronym is already sparkled all over the place.

     SPINOR:Detected

would fit, but no more space ;)


  parent reply	other threads:[~2026-10-26  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 22:45 [PATCH] mtd: spi-nor: Indent SF: just like other boot time messages Marek Vasut
2026-10-24 14:23 ` Tom Rini
2026-10-24 21:27   ` Marek Vasut
2026-10-24 15:14 ` Stefan Monnier
2026-10-24 18:05   ` Marek Vasut
2026-10-25 13:29     ` E Shattow
2026-10-25 14:10       ` Stefan Monnier
2026-10-25 14:18         ` E Shattow
2026-10-26  8:25         ` Miquel Raynal [this message]
2026-10-26 11:07           ` E Shattow

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=87ik2oj2b4.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=akoch@initse.com \
    --cc=dlechner@baylibre.com \
    --cc=e@freeshell.de \
    --cc=flaviu.nistor@gmail.com \
    --cc=marex@nabladev.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=takahiro.kuwano@infineon.com \
    --cc=trini@konsulko.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.