From: Arjan van de Ven <arjanv@redhat.com>
To: Stelian Pop <stelian@popies.net>
Cc: Daniel Drake <dsd@gentoo.org>,
video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use msleep in meye driver
Date: Thu, 03 Jun 2004 10:47:18 +0200 [thread overview]
Message-ID: <1086252437.2709.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040603083848.GA3621@crusoe.alcove-fr>
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
> >From what I see in kernel/timer.c, msleep() cannot be called in
> interrupt context, so the in_interrupt() test must stay.
mdelay in irq context is *EVIL* though, and will get all the low latency
and audio folks very upset...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-03 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 15:57 [PATCH] Use msleep in meye driver Daniel Drake
2004-06-03 8:38 ` Stelian Pop
2004-06-03 8:47 ` Arjan van de Ven [this message]
2004-06-03 9:00 ` Stelian Pop
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=1086252437.2709.0.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stelian@popies.net \
--cc=video4linux-list@redhat.com \
/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