From: David Woodhouse <dwmw2@infradead.org>
To: mtd@infradead.org
Subject: Updates.
Date: Thu, 30 Mar 2000 10:10:32 +0100 [thread overview]
Message-ID: <6334.954407432@devel2.axiom.internal> (raw)
I've updated the documentation now. I thought I'd said that the notify
functions which are called to notify 'user' modules of addition and removal of
MTD devices may not sleep.
That was a silly decision, and so I've changed it - these routines obviously
need to call the mtd->read() routines et al to see if there's anything of
interest on the newly-added device, which means they have to be able to sleep.
I was going to protect the MTD driver list with a spinlock but it'll have to
be a semaphore.
I've committed an updated ftl.c to CVS, based on the latest one from David
Hinds' PCMCIA code. It appears to be hanging in INIT_REQUEST, which is
confusing me. Anyone want to take a look?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-03-30 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 9:10 David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-24 10:42 Updates Ywe Cærlyn
2006-05-16 23:55 Updates Tom McCabe
2006-05-17 2:24 ` Updates Jody
2006-05-17 2:32 ` Updates Vikas Kumar
2006-05-17 2:42 ` Updates Jody
2006-05-17 8:02 ` Updates Frank Gevaerts
2006-05-18 7:16 ` Updates Vojtěch Sázel
[not found] <0032HA5071DKFICB@vger.kernel.org>
2004-08-25 9:01 ` updates xpix
[not found] <B79G2E886I28GA55@vger.kernel.org>
2004-08-25 8:16 ` updates jonm
[not found] <9JJD23BK81GJGH37@vger.kernel.org>
2004-08-25 7:51 ` updates jgamble
[not found] <04GJIEG1D6AFF9G6@vger.kernel.org>
2004-08-22 21:39 ` updates gward
[not found] <AEEKHKH43246513J@vger.kernel.org>
2004-08-20 19:10 ` updates udpelleg
1998-05-05 9:57 updates Lencses Gabor
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=6334.954407432@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.