From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: compile error when building multiple EHCI host controllers as modules
Date: Tue, 28 Mar 2006 19:51:55 +0200 [thread overview]
Message-ID: <pan.2006.03.28.17.51.53.450352@free.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0603241429220.19557-100000@gate.crashing.org
Hi,
Le Fri, 24 Mar 2006 14:32:57 -0600, Kumar Gala a écrit :
> +
> +static int __init ehci_hcd_init(void)
> +{
> + int retval = 0;
> +
> + pr_debug("%s: block sizes: qh %Zd qtd %Zd itd %Zd sitd %Zd\n",
> + hcd_name,
> + sizeof(struct ehci_qh), sizeof(struct ehci_qtd),
> + sizeof(struct ehci_itd), sizeof(struct ehci_sitd));
> +
> +#ifdef CONFIG_PPC_83xx
> + retval = platform_driver_register(&ehci_fsl_dr_driver);
> + if (retval < 0)
> + return retval;
This is wrong as the first driver could failed but the following one could
be correct : imagine generic kernel were multiple config options are
enabled.
On some board we could have only one controller, on other both.
> + retval = platform_driver_register(&ehci_fsl_dr_driver);
> + if (retval < 0)
> + return retval;
> +#endif
We should unregister all the previous drivers if we fail.
Matthieu
next prev parent reply other threads:[~2006-03-28 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 22:26 compile error when building multiple EHCI host controllers as modules Kumar Gala
2006-03-24 6:33 ` [linux-usb-devel] " David Brownell
2006-03-24 16:59 ` Kumar Gala
2006-03-24 20:32 ` Kumar Gala
2006-03-28 16:18 ` Kumar Gala
2006-03-28 17:51 ` Matthieu CASTET [this message]
2006-04-04 2:48 ` David Brownell
2006-04-04 4:23 ` Kumar Gala
2006-04-05 17:32 ` Kumar Gala
2006-04-10 19:11 ` David Brownell
2006-04-10 19:16 ` Kumar Gala
2006-04-11 15:07 ` [PATCH] usb: allow multiple types of EHCI controllers to be built " Kumar Gala
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=pan.2006.03.28.17.51.53.450352@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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