public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: tharbaugh@lnxi.com
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: 13 Jul 2004 10:00:51 -0600	[thread overview]
Message-ID: <m3y8lndhho.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <1089732108.8696.127.camel@tubarao>

Thayne Harbaugh <tharbaugh@lnxi.com> writes:

> On Tue, 2004-07-13 at 09:04 -0600, Eric W. Biederman wrote:
> > Thayne Harbaugh <tharbaugh@lnxi.com> writes:
> 
> > > There's a short list of things that have been removed or changed
> > > significantly (although this is from memory and may not match the
> > > current code):
> > > 
> > > * read-back check of written data
> > 
> > I have a patch  for that already.  Since we are not checking any other
> > status bits.  At least verifying the data is correct is useful.  
> 
> Wonderful.
> 
> > > * retry of failed writes
> > 
> > This one is more interesting.  I don't know if it should be generic or we
> should
> 
> > just override do_write_one_word...
> > 
> > One way or another we will get this one back in there.
> 
> Good.

Looking at where we are Dave has just reworked the code for handling multiple
word sizes for reads and writes, and things are just starting to settle out.
And since he is going to be gone he will be sending these changes to Linus
later this week.

Since refactoring does not work well if I don't have a working code base
to start with. I will push for the appropriate fixes to the MTD command sets
so I know I am starting with a working base.  And then I will start refactoring
the command sets.

Eric

  parent reply	other threads:[~2004-07-13 16:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  3:13 [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe Eric W. Biederman
2004-07-13  6:25 ` David Woodhouse
2004-07-13  7:05   ` Eric W. Biederman
2004-07-13  8:02     ` David Woodhouse
2004-07-13 14:23       ` Eric W. Biederman
2004-07-13 14:45         ` Thayne Harbaugh
2004-07-13 15:04           ` Eric W. Biederman
2004-07-13 15:21             ` Thayne Harbaugh
2004-07-13 15:40               ` Eric W. Biederman
2004-07-13 16:00               ` Eric W. Biederman [this message]
2004-07-14  5:44                 ` Eric W. Biederman
2004-08-12  7:39                   ` Eric W. Biederman
2004-07-13 15:25   ` Eric W. Biederman
2004-07-13 16:17     ` Josh Boyer
2004-08-12  7:13       ` Eric W. Biederman
2004-08-16 14:13         ` Josh Boyer
2004-07-13 16:36 ` Dan Post
2004-07-13 16:52   ` Nicolas Pitre
2004-07-13 17:33     ` Dan Post
2004-07-13 18:17       ` Nicolas Pitre

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=m3y8lndhho.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tharbaugh@lnxi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox