From: Takashi Iwai <tiwai@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: perex@suse.cz, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: ALSA update
Date: Wed, 16 Oct 2002 18:20:25 +0200 [thread overview]
Message-ID: <s5hhefm5p9y.wl@alsa2.suse.de> (raw)
In-Reply-To: <20021015.124540.39818748.davem@redhat.com>
At Tue, 15 Oct 2002 12:45:40 -0700 (PDT),
David S. Miller <davem@redhat.com> wrote:
>
> From: Jaroslav Kysela <perex@suse.cz>
> Date: Tue, 15 Oct 2002 21:45:56 +0200 (CEST)
>
> On Tue, 15 Oct 2002, David S. Miller wrote:
>
> > It fails again soon after that, none of the ioctl32.c/pcm32.c
> > changes were even _compile_ tested.
>
> Thanks. Applied to linux-sound repository.
>
> And what are you going to do in the future to make sure
> the sound/ioctl32/ changes you submit in the future even
> compile?
I'll test before submitting.
this time I had no chance, though...
--
Takashi Iwai <tiwai@suse.de> SuSE Linux AG - www.suse.de
ALSA Developer ALSA Project - www.alsa-project.org
next prev parent reply other threads:[~2002-10-16 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 19:45 ALSA update Jaroslav Kysela
2002-10-14 19:58 ` David S. Miller
2002-10-14 22:43 ` Jaroslav Kysela
2002-10-15 17:08 ` David S. Miller
2002-10-15 19:45 ` Jaroslav Kysela
2002-10-15 19:45 ` David S. Miller
2002-10-16 16:20 ` Takashi Iwai [this message]
[not found] <Pine.NEB.4.44.0210151048240.20607-100000@mimas.fachschaften.tu-muenchen.de>
2002-10-15 9:55 ` Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2002-11-10 20:44 Jaroslav Kysela
[not found] <200212181807.gBII7Wn28845@hera.kernel.org>
2002-12-18 18:21 ` Greg KH
2002-12-18 19:17 ` Jaroslav Kysela
2002-12-18 19:27 ` Greg KH
2002-12-19 12:17 ` Takashi Iwai
2002-12-18 19:51 ` Ruslan U. Zakirov
2002-12-19 12:07 ` Takashi Iwai
2002-12-19 12:18 ` Jaroslav Kysela
2002-12-20 0:27 ` Greg KH
2002-12-19 23:04 ` Bill Davidsen
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=s5hhefm5p9y.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=torvalds@transmeta.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 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.