From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: PATCH : remove warning in documentation for via_audio
Date: Wed, 5 Sep 2001 19:47:46 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0109051945030.20371-100000@pppg_penguin.linux.bogus> (raw)
Following patch removes a warning when the documentation is built. Applies
cleanly to 2.4.10-pre4, and with a 4-line offset to 2.4.9-ac6.
diff -urN linux-2.4.7/drivers/sound/via82cxxx_audio.c altered-2.4.7/drivers/sound/via82cxxx_audio.c
--- linux-2.4.7/drivers/sound/via82cxxx_audio.c Sat Jul 21 22:47:35 2001
+++ altered-2.4.7/drivers/sound/via82cxxx_audio.c Thu Aug 23 20:14:57 2001
@@ -862,6 +862,7 @@
/**
* via_chan_clear - Stop DMA channel operation, and reset pointers
+ * @card: the chip to accessed
* @chan: Channel to be cleared
*
* Call via_chan_stop to halt DMA operations, and then resets
Ken
--
If a six turned out to be nine, I don't mind.
Home page : http://www.kenmoffat.uklinux.net
reply other threads:[~2001-09-05 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.21.0109051945030.20371-100000@pppg_penguin.linux.bogus \
--to=ken@kenmoffat.uklinux.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).