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: Wed, 06 Aug 2025 08:57:11 +0200 [thread overview]
Message-ID: <87tt2ley48.fsf@bootlin.com> (raw)
In-Reply-To: <20250719-mtd-ooblayout-sysfs-v1-1-e0d68d872e17@gmail.com> (Gabor Juhos's message of "Sat, 19 Jul 2025 14:06:48 +0200")
Hello Gabor,
On 19/07/2025 at 14:06:48 +02, Gabor Juhos <j4g8y7@gmail.com> wrote:
> Add two new sysfs device attributes which allows to determine the OOB
> layout used by a given MTD device. This can be useful to verify the
> current layout during driver development without adding extra debug
> code. The exposed information also makes it easier to analyze NAND
> dumps without the need of cravling out the layout from the driver
> code.
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.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
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: Wed, 06 Aug 2025 08:57:11 +0200 [thread overview]
Message-ID: <87tt2ley48.fsf@bootlin.com> (raw)
In-Reply-To: <20250719-mtd-ooblayout-sysfs-v1-1-e0d68d872e17@gmail.com> (Gabor Juhos's message of "Sat, 19 Jul 2025 14:06:48 +0200")
Hello Gabor,
On 19/07/2025 at 14:06:48 +02, Gabor Juhos <j4g8y7@gmail.com> wrote:
> Add two new sysfs device attributes which allows to determine the OOB
> layout used by a given MTD device. This can be useful to verify the
> current layout during driver development without adding extra debug
> code. The exposed information also makes it easier to analyze NAND
> dumps without the need of cravling out the layout from the driver
> code.
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.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-08-06 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 12:06 [PATCH] mtd: expose ooblayout information via sysfs Gabor Juhos
2025-07-19 12:06 ` Gabor Juhos
2025-08-06 6:57 ` Miquel Raynal [this message]
2025-08-06 6:57 ` Miquel Raynal
2025-08-06 18:40 ` Gabor Juhos
2025-08-06 18:40 ` Gabor Juhos
2025-08-07 7:50 ` Miquel Raynal
2025-08-07 7:50 ` Miquel Raynal
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=87tt2ley48.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 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.