From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: expose ooblayout information via sysfs
Date: Thu, 07 Aug 2025 09:50:57 +0200 [thread overview]
Message-ID: <878qjvefj2.fsf@bootlin.com> (raw)
In-Reply-To: <25dcf103-3cd3-400a-b402-cbb5f23006c9@gmail.com> (Gabor Juhos's message of "Wed, 6 Aug 2025 20:40:21 +0200")
Hi Gabor,
>> I would prefer a debugfs entry, as this is mostly focusing on
>> development and debugging purposes. sysfs has a stable API, which makes
>> it a less relevant place in this case.
>
> Sorry, it seems that I misunderstood the ABI documentation.
>
> Since the 'sysfs-class-mtd' file is under the 'testing' directory
> within
It is indeed unclear. I'm not sure myself what that exactly means TBH,
but it's been there for a long time and can for sure be considered
stable. Sysfs in general is not for debugging.
> 'Documentation/ABI' I thought that it can be extended by attributes used for
> testing purposes. Additionally, the 'oobavail' and 'oobsize' attributes are
> exposed via sysfs, so it seemed to be a logical place for the new oob related ones.
>
> Nevertheless, I will check what can I do with the debugfs based
> approach.
Sure, thanks!
Miquèl
prev parent reply other threads:[~2025-08-07 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 12:06 Gabor Juhos
2025-08-06 6:57 ` Miquel Raynal
2025-08-06 18:40 ` Gabor Juhos
2025-08-07 7:50 ` Miquel Raynal [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=878qjvefj2.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=j4g8y7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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 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®