From: Brian Norris <computersforpeace@gmail.com>
To: Daniel Walter <dwalter@sigma-star.at>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] Trace-events for mtd
Date: Fri, 8 Jan 2016 10:00:33 -0800 [thread overview]
Message-ID: <20160108180033.GP109450@google.com> (raw)
In-Reply-To: <20151117191448.GA5367@dw-nb.local>
On Tue, Nov 17, 2015 at 08:14:48PM +0100, Daniel Walter wrote:
> I wanted to reach out to the broader community to find
> out if I missed somethings and to get overall feedback
> if more traceevents would be useful to help us
> debugging mtd i/o a little bit better.
Regarding this point: is there a good reason not to track mtd_erase()?
How about mtd_{read,write}_oob()? (NB: The latter can be used to get
both in-band and out-of-band data.)
Brian
prev parent reply other threads:[~2016-01-08 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:14 [RFC] Trace-events for mtd Daniel Walter
2015-11-17 19:18 ` [RFC] [PATCH] mtd: add tracepoints for mtd_read and mtd_write Daniel Walter
2016-01-08 9:33 ` Richard Weinberger
2016-01-08 17:57 ` Brian Norris
2016-01-14 1:12 ` Daniel Walter
2016-01-08 18:00 ` Brian Norris [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=20160108180033.GP109450@google.com \
--to=computersforpeace@gmail.com \
--cc=dwalter@sigma-star.at \
--cc=linux-mtd@lists.infradead.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).