From: David Woodhouse <dwmw2@infradead.org>
To: mtd@infradead.org
Subject: Preliminary documentation.
Date: Tue, 28 Mar 2000 11:49:03 +0100 [thread overview]
Message-ID: <18200.954240543@devel2.axiom.internal> (raw)
I've now put written up the documentation I wrote out by hand last night.
It's at http://www.linux-mtd.infradead.org/tech/
Comments, please. I haven't yet filled in my suggested restrictions on the
read/write functions, but I have removed the retlen arguments.
As I said, I'm changing the notifier stuff to make it cleaner. I have yet to
actually change the code to fit in with my new documentation.
Also, a couple of questions on the decisions I've made:
1. Is mtd->sync() enough, or could users want more access to the erase queue?
We could add
struct erase_info *mtd->eraseq;
spin_lock_t mtd->eraseq_lock;
... and allow users to use that.
2. Is the callback in the erase_info OK or would we be better off having a
wait_queue_head_t instead (or as well)?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-03-28 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 10:49 David Woodhouse [this message]
2000-03-28 14:11 ` Preliminary documentation Alexander Larsson
2000-03-28 15:11 ` David Woodhouse
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=18200.954240543@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--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