Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC] mtd-utils: integck: add support for volume specific power-cut test
Date: Mon, 19 Aug 2013 18:16:34 +0300	[thread overview]
Message-ID: <1376925394.2089.491.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C4FCDC729@post.tritech.se>

On Mon, 2013-08-19 at 15:01 +0000, Mats Kärrman wrote:
> Actually this was what I first had in mind, but I stopped for the -P solution
> for two reasons:
> 1) It saved me a lot of time ;)
> 2) Integck seem to be written with the aim of being a general purpose test
> program (even if some comments in the code hint in another direction). If
> so, it would not be safe to assume there is any ubifs/ubi folder or that the
> knob file is called tst_recovery.

OK, but there is also an "fstype" field, could you use and do the trick
only for UBIFS?

>  Also it is possible to mount the debugfs
> anywhere (but i guess that could also be parsed from /proc/mounts).

I would not worry about this and I'd assume "/sys/kernel/debug" now, I
think this is more than good enough.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2013-08-19 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19  8:50 [RFC] mtd-utils: integck: add support for volume specific power-cut test Mats Kärrman
2013-08-19 13:36 ` Artem Bityutskiy
2013-08-19 14:24   ` Mats Kärrman
2013-08-19 14:50     ` Artem Bityutskiy
2013-08-19 14:55       ` Artem Bityutskiy
2013-08-19 15:01         ` Mats Kärrman
2013-08-19 15:16           ` Artem Bityutskiy [this message]
2013-08-19 15:37             ` Mats Kärrman
2013-08-20 12:23               ` Artem Bityutskiy
2013-08-20 13:10                 ` Artem Bityutskiy
2013-08-21  6:21                   ` Mats Kärrman

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=1376925394.2089.491.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=Mats.Karrman@tritech.se \
    --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