From: Dave Dillow <dave@thedillows.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] sis7019: support the SiS 7019 Audio Accelerator
Date: Wed, 28 Nov 2007 08:22:25 -0500 [thread overview]
Message-ID: <1196256145.7017.60.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <s5h3auqim2i.wl%tiwai@suse.de>
On Wed, 2007-11-28 at 13:36 +0100, Takashi Iwai wrote:
> OK, then it's fine. But add a proper comment. Otherwise no one else
> would understand the difference.
I presume the comment /* Must hold the voice_lock on entry */
present in all of the __ functions is insufficient, or we wouldn't be
having this coversation? :)
next prev parent reply other threads:[~2007-11-28 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 7:19 [PATCH 1/2] sis7019: support the SiS 7019 Audio Accelerator Dave Dillow
2007-11-28 9:56 ` Takashi Iwai
2007-11-28 13:03 ` Dave Dillow
2007-11-28 12:36 ` Takashi Iwai
2007-11-28 13:22 ` Dave Dillow [this message]
2007-11-28 12:50 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2007-12-08 23:54 Dave Dillow
2007-12-09 18:04 ` Dave Dillow
2007-12-13 15:54 ` Takashi Iwai
2007-12-13 17:47 ` Dave Dillow
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=1196256145.7017.60.camel@obelisk.thedillows.org \
--to=dave@thedillows.org \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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