public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Larsson <alex@cendio.se>
Cc: mtd@infradead.org
Subject: Re: New release of MTD code pending.
Date: Mon, 27 Mar 2000 17:01:25 +0100	[thread overview]
Message-ID: <10326.954172885@devel2.axiom.internal> (raw)
In-Reply-To: <Pine.LNX.3.96.1000327172759.26529E-100000@biffen.cendio.se>


alex@cendio.se said:
>  All this should really be documented in mtd.h, so that one can rely
> on certain properties. The you can just fix drivers that don't
> implement stuff you depend on, instead of having to read all drivers
> to see how the api really works.

Definitely. At the moment, I don't think there even _is_ a good example to
point at. 

I started this in HTML at one point, but didn't get very far, do didn't ever 
publish it:
	http://www.linux-mtd.infradead.org/tech/API.html

> I was thinking of using alan's new kernel documentation stuff. That
> would be nice.

Yes, the DocBook stuff looks quite good.

I'd very much like to get some real documentation done, then go through the 
existing drivers and audit them sensibly against that documentation. 

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

       reply	other threads:[~2000-03-27 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1000327172759.26529E-100000@biffen.cendio.se>
2000-03-27 16:01 ` David Woodhouse [this message]
2000-03-27  9:12 New release of MTD code pending David Woodhouse
2000-03-27 14:18 ` Alexander Larsson
2000-03-27 14:24   ` David Woodhouse
2000-03-27 14:31     ` Alexander Larsson
2000-03-27 14:38       ` David Woodhouse
2000-03-27 14:55         ` Alexander Larsson
2000-03-27 15:22           ` David Woodhouse
2000-03-27 15:54     ` Trevor Woolven

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=10326.954172885@devel2.axiom.internal \
    --to=dwmw2@infradead.org \
    --cc=alex@cendio.se \
    --cc=mtd@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