public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: Josh Boyer <jdub@us.ibm.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: 12 Aug 2004 01:13:46 -0600	[thread overview]
Message-ID: <m31xic6d79.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <1089735455.29112.14.camel@weaponx.rchland.ibm.com>

Josh Boyer <jdub@us.ibm.com> writes:

> On Tue, 2004-07-13 at 10:25, Eric W. Biederman wrote:
> > Ok recording what the reason for this that I got on irc.
> > 
> > cfi_cmdset_0020 is just a variant on cfi_cmdset_0001 that shares most of
> > the code.
> 
> Thinking about this more, I wouldn't worry too much about
> cfi_cmdset_0020.c.  It's old, fairly unmaintained, and only has a single
> user as far as I know.
> 
> If your changes break it, then it'll give someone and excuse to update
> the code.  Eventually it should be merged with cfi_cmdset_0001.c anyway,
> since M58LW128A reports command set 01, but really needs the
> functionality of command set 20.  The exception list you talked about in
> IRC might help with that.
> 
> But don't let me stop you from making it work if you want to :).

So far I have been busy with other things so I have been taking the slow route
to refactoring.  I have just reported the cfi_fixup function from cfi_util
and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
under control.  

It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
merged.

For the deeper pieces of command set common code moving their helper functions
into cfi_util is probably a good place to start.

I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...

Eric

  reply	other threads:[~2004-08-12  7:13 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
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 [this message]
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=m31xic6d79.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=jdub@us.ibm.com \
    --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