All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Marek Skuczynski <mareksk7@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Emulated write failures cause block marking as bad
Date: Mon, 15 Feb 2010 16:10:06 +0200	[thread overview]
Message-ID: <1266243006.11659.98.camel@localhost> (raw)
In-Reply-To: <a328840c1002050123u15be6d75s1c6f27fca6452137@mail.gmail.com>

On Fri, 2010-02-05 at 10:23 +0100, Marek Skuczynski wrote:
> > Okay, maybe my case is isolated because of tested system configuration,
> > I will try manage this case myself.
> >
> I have prepared a patch, maybe someone will find it useful.

Something like this is useful, but I disapprove of adding another
configuration option. Instead, I think you should just improve the
current debugging code.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-02-15 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 17:02 Emulated write failures cause block marking as bad Marek Skuczynski
2010-02-04 17:33 ` Artem Bityutskiy
2010-02-04 19:38   ` Marek Skuczynski
2010-02-05  9:23     ` Marek Skuczynski
2010-02-15 14:10       ` Artem Bityutskiy [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=1266243006.11659.98.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mareksk7@gmail.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.