From: Roland Dreier <roland@topspincom•com>
To: Ralph Blach <rcblach@raleigh•ibm.com>
Cc: Embedded Linux list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Wait queue question
Date: 15 Feb 2001 08:39:46 -0800 [thread overview]
Message-ID: <52zofn3not.fsf@love-boat.topspincom.com> (raw)
In-Reply-To: Ralph Blach's message of "Thu, 15 Feb 2001 08:59:06 -0500"
>>>>> "Ralph" == Ralph Blach <rcblach@raleigh•ibm.com> writes:
Ralph> Roland, Ok, but were is an example of how to use a
Ralph> wait_event macro. I dont see it in any of the
Ralph> documentation.
Documentation/DocBook/kernel-hacking.tmpl does mention wait_event(),
although it's pretty short on details. But your best bet is just to
grep through some driver sources and look at how people actually use
it.
Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 15:05 Wait queue question Ralph Blach
2001-02-14 17:30 ` Roland Dreier
2001-02-15 13:59 ` Ralph Blach
2001-02-15 16:39 ` Roland Dreier [this message]
2001-02-14 18:34 ` Ron Bianco
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 18:04 Ian Abbott
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=52zofn3not.fsf@love-boat.topspincom.com \
--to=roland@topspincom$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=rcblach@raleigh$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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