public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: ebiederman@lnxi.com (Eric W. Biederman)
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash driver probe/commandset separation.
Date: Thu, 03 May 2001 22:40:13 +0100	[thread overview]
Message-ID: <17287.988926013@redhat.com> (raw)
In-Reply-To: <m33damuyn5.fsf@DLT.linuxnetworx.com>

ebiederman@lnxi.com said:
>  Note there is a good argument for joining the probe paths Handling
> chip interleaving, unless we can make it simple we don't want that
> duplicated many times.

True. The build_cmd et al macros prevent duplication to a certain extent. 

> I'll try to have something working for 2 & 4 by the end of today.  Any
> hints on why the cmdset drivers don't compile? 

I changed the chip driver registration stuff. They need to have a 
struct mtd_chip_driver and set mtd->fldrv to point to it. And I'd like to 
make the inter_module_xxx stuff go away completely - maybe they can 
register with the code in chipreg instead, and get cfi_probe to look them 
up that way. That can wait a little while though - I'm not sure that's the 
correct approach (because they're not actually probes).

--
dwmw2

  reply	other threads:[~2001-05-03 21:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-29 18:38 Flash driver probe/commandset separation David Woodhouse
2001-04-30 15:17 ` AW: " Florian Schirmer / TayTron
2001-04-30 15:56   ` David Woodhouse
2001-04-30 15:56 ` Eric W. Biederman
2001-05-01 14:26   ` David Woodhouse
2001-04-30 17:56 ` Alice Hennessy
2001-05-02 15:33 ` Nicolas Pitre
2001-05-02 15:39   ` David Woodhouse
2001-05-03 17:32     ` Eric W. Biederman
2001-05-03 21:40       ` David Woodhouse [this message]
2001-05-03 21:45         ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2001-05-02 16:22 Kári Davíðsson

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=17287.988926013@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ebiederman@lnxi.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