From: Takashi Iwai <tiwai@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Charbonnel <thomas@undata.org>
Subject: Re: [PATCH] Fix shared interrupt handling of SA_INTERRUPT and SA_SAMPLE_RANDOM
Date: Mon, 23 Aug 2004 19:29:23 +0200 [thread overview]
Message-ID: <s5hd61hhifg.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5heklxhjbg.wl@alsa2.suse.de>
At Mon, 23 Aug 2004 19:10:11 +0200,
I wrote:
>
> The patch below fixes these problems by adding the SA_INTERRUPT
> handler always to the head of the irq list, and by checking the return
> value of each handler.
Forgot to mention that it's to 2.6.8.1.
Takashi
next prev parent reply other threads:[~2004-08-23 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 17:10 [PATCH] Fix shared interrupt handling of SA_INTERRUPT and SA_SAMPLE_RANDOM Takashi Iwai
2004-08-23 17:29 ` Takashi Iwai [this message]
2004-08-23 18:09 ` Zwane Mwaikambo
2004-08-25 3:45 ` Andrew Morton
2004-08-25 11:17 ` Takashi Iwai
2004-08-25 20:41 ` Andrew Morton
2004-08-26 12:50 ` Takashi Iwai
2004-08-26 14:04 ` Russell King
2004-08-26 14:10 ` Takashi Iwai
2004-08-26 14:18 ` Russell King
2004-08-26 14:27 ` Takashi Iwai
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=s5hd61hhifg.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@undata.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