linux-mtd.lists.infradead.org archive mirror
 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: [PATCH v2] mtd-utils: integck: add support for volume specific power-cut test
Date: Wed, 28 May 2014 12:30:53 +0300	[thread overview]
Message-ID: <1401269453.2118.5.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B4094CF@post.tritech.se>

On Wed, 2014-05-28 at 08:40 +0000, Mats Kärrman wrote:
> On Tuesday, May 27, 2014 4:55 PM, Artem Bityutskiy wrote:
> > How about this compromise solution which should be simple enough to
> > implement, but I am not sure it is good enough to you.
> > 
> > Change -p so that it takes an _argument_. The argument should be a path
> > to the debugfs file which controls the power cuts emulation. This can be
> > either global or the per-FS switch.
> > 
> > All the test will do is writing '1' to this file as soon as it starts,
> > and as soon as it mounts or re-mounts the FS.
> > 
> > Now, it is your choice which file path to give - the global or the
> > per-FS.
> 
> I guess you mean something in the line of
> http://comments.gmane.org/gmane.linux.drivers.mtd/47872

Yes, but without introducing a new option, but just changing the old one
and add the path argument there.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2014-05-28  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  8:21 [PATCH v2] mtd-utils: integck: add support for volume specific power-cut test Mats Kärrman
2014-05-27 12:37 ` Artem Bityutskiy
2014-05-27 14:15   ` Mats Kärrman
2014-05-27 14:55     ` Artem Bityutskiy
2014-05-28  8:40       ` Mats Kärrman
2014-05-28  9:30         ` Artem Bityutskiy [this message]
2014-05-28 10:52           ` Mats Kärrman
2014-05-28 11:04             ` Artem Bityutskiy

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=1401269453.2118.5.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;
as well as URLs for NNTP newsgroup(s).