From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mach-cpuimx27: fix USB_ULPI build warnings
Date: Mon, 21 Jun 2010 08:51:58 +0200 [thread overview]
Message-ID: <20100621065158.GD12115@pengutronix.de> (raw)
In-Reply-To: <1276870795-21594-2-git-send-email-eric@eukrea.com>
On Fri, Jun 18, 2010 at 04:19:55PM +0200, Eric B?nard wrote:
> when CONFIG_USB_ULPI is not defined we actually get :
> warning: 'otg_pdata' defined but not used
> warning: 'usbh2_pdata' defined but not used
Ok, applied.
>
> Signed-off-by: Eric B?nard <eric@eukrea.com>
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: s.hauer at pengutronix.de
> ---
> arch/arm/mach-mx2/mach-cpuimx27.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-mx2/mach-cpuimx27.c b/arch/arm/mach-mx2/mach-cpuimx27.c
> index dc2dca3..5529178 100644
> --- a/arch/arm/mach-mx2/mach-cpuimx27.c
> +++ b/arch/arm/mach-mx2/mach-cpuimx27.c
> @@ -219,6 +219,7 @@ static struct platform_device serial_device = {
> };
> #endif
>
> +#if defined(CONFIG_USB_ULPI)
> static struct mxc_usbh_platform_data otg_pdata = {
> .portsc = MXC_EHCI_MODE_ULPI,
> .flags = MXC_EHCI_INTERFACE_DIFF_UNI,
> @@ -228,6 +229,7 @@ static struct mxc_usbh_platform_data usbh2_pdata = {
> .portsc = MXC_EHCI_MODE_ULPI,
> .flags = MXC_EHCI_INTERFACE_DIFF_UNI,
> };
> +#endif
>
> static struct fsl_usb2_platform_data otg_device_pdata = {
> .operating_mode = FSL_USB2_DR_DEVICE,
> --
> 1.6.3.3
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2010-06-21 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 14:19 [PATCH 1/2] net/fec: clean suspend/resume Eric Bénard
2010-06-18 14:19 ` [PATCH 2/2] mach-cpuimx27: fix USB_ULPI build warnings Eric Bénard
2010-06-21 6:51 ` Sascha Hauer [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=20100621065158.GD12115@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).