From: Marcus Meissner <Marcus.Meissner@caldera.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/sound/nm256_audio.c
Date: Thu, 19 Apr 2001 18:08:42 +0200 [thread overview]
Message-ID: <20010419180842.A16881@caldera.de> (raw)
In-Reply-To: <20010419173502.A13934@caldera.de> <3ADF0A91.F803266F@mandrakesoft.com>
In-Reply-To: <3ADF0A91.F803266F@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Apr 19, 2001 at 11:56:01AM -0400
On Thu, Apr 19, 2001 at 11:56:01AM -0400, Jeff Garzik wrote:
> Marcus Meissner wrote:
> >
> > Hi,
> >
> > This updates the nm256_audio driver to the 2.4 PCI API.
> >
> > Patch is against 2.4.3-ac9, verified on Sony VAIO Laptop.
>
> "verified" is the really important part with this driver, since its
> really finicky. I have a patch I would love to bounce to you in
> private, that I have been searching for a tester for -months- because I
> had no test hardware of my own.
Feel free to send (I have a NM256AV card in that VAIO).
> Your patch looks ok to me and I would say apply it. But I also think it
> is incomplete.
>
> * there is no need for a linked list of cards, since
> pci_{get,set}_drvdata is used. This eliminates the list walk in
> nm256_remove
The problem is with device opens, which just pass numbers, most other
sound drivers still use linked lists.
Hmm, but via8xxxx_audio.c doesn't, I will take this as example.
> * the new PCI API has suspend/resume hooks, and those should be used in
> preference to register_pm_...
Ok, will have another look at the other issues.
And I hope my colleague brings his VAIO to work tomorrow ;)
Ciao, Marcus
prev parent reply other threads:[~2001-04-19 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 15:35 Marcus Meissner
2001-04-19 15:56 ` Jeff Garzik
2001-04-19 16:08 ` Marcus Meissner [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=20010419180842.A16881@caldera.de \
--to=marcus.meissner@caldera.de \
--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
all inboxes | Powered by JetHome®