From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] emu10k1: fix P16V breakage for non Audigy2 cards
Date: Thu, 17 Mar 2005 17:41:55 +0100 [thread overview]
Message-ID: <s5hbr9i1ay4.wl@alsa2.suse.de> (raw)
In-Reply-To: <1111076459.23171.16.camel@mindpipe>
At Thu, 17 Mar 2005 11:20:59 -0500,
Lee Revell wrote:
>
> On Thu, 2005-03-17 at 16:58 +0100, Takashi Iwai wrote:
> > Already applied the older one except but the change to printk.
> > (Is that identical with the new one, right?)
>
> Are you sure you committed it? I still haven't seen the CVS commit
> message. And there does not seem to be a list delay since I got the
> commit message for the "misc oopses" patch immediately.
Don't worry. The CVS-commit message order is sometimes screwed.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-17 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 5:21 [PATCH] emu10k1: fix P16V breakage for non Audigy2 cards Lee Revell
2005-03-16 5:27 ` Lee Revell
2005-03-16 21:28 ` James Courtier-Dutton
2005-03-17 15:53 ` Lee Revell
2005-03-17 15:58 ` Takashi Iwai
2005-03-17 16:00 ` Lee Revell
2005-03-17 16:20 ` Lee Revell
2005-03-17 16:41 ` Takashi Iwai [this message]
2005-03-17 16:48 ` Lee Revell
2005-03-18 19:52 ` James Courtier-Dutton
2005-03-18 19:54 ` Lee Revell
2005-03-18 19:56 ` Lee Revell
2005-03-17 14:11 ` [PATCH] emu10k1: fix misc oopses Thierry Vignaud
2005-03-17 15:02 ` Lee Revell
2005-03-17 16:01 ` 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=s5hbr9i1ay4.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.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