From: <Tudor.Ambarus@microchip.com>
To: <zhuohao@chromium.org>, <linux-mtd@lists.infradead.org>
Cc: drinkcat@chromium.org, bbrezillon@kernel.org, richard@nod.at,
briannorris@chromium.org, marek.vasut@gmail.com,
boris.brezillon@collabora.com, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH v8 2/2] mtd: spi-nor: enable the debugfs for the partname and partid
Date: Thu, 29 Aug 2019 10:47:52 +0000 [thread overview]
Message-ID: <3b209c11-e5db-5006-5dd3-574c9bc42bfe@microchip.com> (raw)
In-Reply-To: <20190630160711.178679-2-zhuohao@chromium.org>
On 06/30/2019 07:07 PM, Zhuohao Lee wrote:
> External E-Mail
>
>
> This patch adds spi_nor_debugfs_init() for the debugfs initialization.
> With this patch, we can read the partname and partid through the
> debugfs.
>
> The output of new debugfs nodes on my device are:
> cat /sys/kernel/debug/mtd/mtd0/partid
> spi-nor:ef6017
> cat /sys/kernel/debug/mtd/mtd0/partname
> w25q64dw
>
> Signed-off-by: Zhuohao Lee <zhuohao@chromium.org>
> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
Rebased, fixed checkpatch warnings and checks, moved the call to
spi_nor_debugfs_init() immediately after spi_nor_get_flash_info() and
applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git,
spi-nor/next branch.
Thanks,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-29 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 16:07 [PATCH v8 1/2] mtd: mtdcore: add debugfs nodes for querying the flash name and id Zhuohao Lee
2019-06-30 16:07 ` [PATCH v8 2/2] mtd: spi-nor: enable the debugfs for the partname and partid Zhuohao Lee
2019-08-29 10:47 ` Tudor.Ambarus [this message]
2019-08-29 10:45 ` [PATCH v8 1/2] mtd: mtdcore: add debugfs nodes for querying the flash name and id 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=3b209c11-e5db-5006-5dd3-574c9bc42bfe@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=drinkcat@chromium.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=zhuohao@chromium.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).