From: Alan Cox <alan@redhat.com>
To: linux-sound@vger.kernel.org
Subject: Re: sb_dsp_detect
Date: Sun, 26 Mar 2000 01:51:14 +0000 [thread overview]
Message-ID: <marc-linux-sound-95405647817569@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95405563817088@msgid-missing>
> That's the prototype of the func in subj:
>
> int sb_dsp_detect(struct address_info *hw_config, int pci, int pciio)
>
> the two pci parameter, AFAIK, are not used
> by anyone. Since i'm going to change that prototype
> to fix a bug, i can get them off while i'm there.
>
> The related pci code seems unused to me..
> should i leave it there?
Its related to some hacking on SB compatibles. Can you leave it for now. Someone
is having another crack at the yamaha shit and will need it
prev parent reply other threads:[~2000-03-26 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-25 23:41 sb_dsp_detect Alessandro Zummo
2000-03-26 1:51 ` Alan Cox [this message]
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=marc-linux-sound-95405647817569@msgid-missing \
--to=alan@redhat.com \
--cc=linux-sound@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