From: Christoph Hellwig <hch@infradead.org>
To: John Kim <john@larvalstage.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.65] pnp api changes to sound/isa/sb/es968.c
Date: Wed, 19 Mar 2003 12:11:21 +0000 [thread overview]
Message-ID: <20030319121121.A21042@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0303190650530.28260@quinn.larvalstage.com>; from john@larvalstage.com on Wed, Mar 19, 2003 at 07:03:57AM -0500
On Wed, Mar 19, 2003 at 07:03:57AM -0500, John Kim wrote:
> struct snd_card_es968 {
> -#ifdef __ISAPNP__
> - struct isapnp_dev *dev;
> -#endif /* __ISAPNP__ */
> + struct pnp_dev *dev;
> };
What about completly removing struct snd_card_es968 and using pnp_dev
directtly instead? sound/* is full of this overdesign and it's time
to get it follow kernel style a bit more..
> static int __init alsa_card_es968_init(void)
> {
> int cards = 0;
>
> -#ifdef __ISAPNP__
> - cards += isapnp_probe_cards(snd_es968_pnpids, snd_es968_isapnp_detect);
> -#else
> - snd_printk("you have to enable ISA PnP support.\n");
> -#endif
> + cards += pnp_register_card_driver(&es968_pnpc_driver);
> #ifdef MODULE
> if (!cards)
> - snd_printk("no ES968 based soundcards found\n");
> + printk(KERN_ERR "no ES968 based soundcards found\n");
> #endif
> return cards ? 0 : -ENODEV;
> }
That printk is useless, you get a useful message from modprobe on
an ENODEV return anyway.
next prev parent reply other threads:[~2003-03-19 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 12:03 John Kim
2003-03-19 12:11 ` Christoph Hellwig [this message]
2003-03-19 14:33 ` John Kim
2003-03-19 14:36 ` [PATCH 2.5.65] pnp api changes to sound/isa/sb/es968.c [rev2] John Kim
2003-03-19 14:38 ` [PATCH 2.5.65] pnp api changes to sound/isa/sb/es968.c Ruslan U. Zakirov
2003-03-19 15:09 ` Ruslan U. Zakirov
2003-03-19 16:22 ` John Kim
2003-03-19 22:15 ` Adam Belay
2003-03-19 22:08 ` Adam Belay
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=20030319121121.A21042@infradead.org \
--to=hch@infradead.org \
--cc=john@larvalstage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®