From: Ingo Oeser <ioe-lkml@rameria.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Greg KH <gregkh@suse.de>
Subject: Re: [ALSA STABLE 3/3] a few more -- unregister platform device again if probe was unsuccessful
Date: Thu, 13 Apr 2006 11:26:34 +0200 [thread overview]
Message-ID: <200604131126.35841.ioe-lkml@rameria.de> (raw)
In-Reply-To: <443DAD5C.8080007@keyaccess.nl>
Hi Rene,
On Thursday, 13. April 2006 03:46, you wrote:
> And finally, unregister on probe failure for sound/drivers,
> sound/arm/sa11xx-uda1341.c and sound/ppc/powermac.c.
>
> sound/arm/sa11xx-uda1341.c | 14 +++++++++-----
> sound/drivers/dummy.c | 4 ++++
> sound/drivers/mpu401/mpu401.c | 4 ++++
> sound/drivers/mtpav.c | 14 +++++++++-----
> sound/drivers/serial-u16550.c | 4 ++++
> sound/drivers/virmidi.c | 4 ++++
> sound/ppc/powermac.c | 14 +++++++++-----
> 7 files changed, 43 insertions(+), 15 deletions(-)
This is inserting lots of duplicate and control heavy code.
It looks like the same pattern and is using just platform_xxx funxtions.
Any counter-examples with a different pattern, which you converted in
a different manner?
Wouldn't it be more useful to do these checks in
platform_register_simple() and return the proper error value there?
Or just create a small helper, if this have to be done seperate.
Greg, what do you think here?
Regards
Ingo Oeser
next prev parent reply other threads:[~2006-04-13 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 1:46 Rene Herman
2006-04-13 9:26 ` Ingo Oeser [this message]
2006-04-13 9:31 ` Russell King
2006-04-13 14:05 ` Rene Herman
2006-04-13 14:57 ` Russell King
2006-04-13 16:17 ` Rene Herman
2006-04-13 17:05 ` Russell King
2006-04-13 18:47 ` Rene Herman
2006-04-13 22:02 ` Greg KH
2006-04-13 23:12 ` Rene Herman
2006-04-15 13:16 ` Takashi Iwai
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=200604131126.35841.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--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
all inboxes | Powered by JetHome®