From: daniel@zonque.org (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: gadget: udc: pxa27x: fix build warning when !OF
Date: Thu, 06 Nov 2014 07:47:11 +0100 [thread overview]
Message-ID: <545B196F.2020303@zonque.org> (raw)
In-Reply-To: <1415249759-6219-1-git-send-email-balbi@ti.com>
On 11/06/2014 05:55 AM, Felipe Balbi wrote:
> in case kernel is built without CONFIG_OF there
> will be a build warning (see below) due to of_match_ptr()
> being defined to NULL.
>
> Because of_match_ptr() is pretty pointless anyway,
> let's just remove it and fix the warning.
The alternative, of course, would be to wrap the udc_pxa_dt_ids
declaration in IS_ENABLED(CONFIG_OF), but I'm not sure whether it's
worth it.
Daniel
> drivers/usb/gadget/udc/pxa27x_udc.c:2403:28: warning: ?udc_pxa_dt_ids? defined but not used [-Wunused-variable]
> static struct of_device_id udc_pxa_dt_ids[] = {
> ^
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> ---
> drivers/usb/gadget/udc/pxa27x_udc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/udc/pxa27x_udc.c b/drivers/usb/gadget/udc/pxa27x_udc.c
> index 69e7b816..d1d8a9f 100644
> --- a/drivers/usb/gadget/udc/pxa27x_udc.c
> +++ b/drivers/usb/gadget/udc/pxa27x_udc.c
> @@ -2590,7 +2590,7 @@ static struct platform_driver udc_driver = {
> .driver = {
> .name = "pxa27x-udc",
> .owner = THIS_MODULE,
> - .of_match_table = of_match_ptr(udc_pxa_dt_ids),
> + .of_match_table = udc_pxa_dt_ids,
> },
> .probe = pxa_udc_probe,
> .remove = pxa_udc_remove,
>
next prev parent reply other threads:[~2014-11-06 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 4:55 [PATCH] usb: gadget: udc: pxa27x: fix build warning when !OF Felipe Balbi
2014-11-06 6:47 ` Daniel Mack [this message]
2014-11-06 19:55 ` Robert Jarzmik
2014-11-06 22:17 ` Felipe Balbi
2014-11-06 22:25 ` Felipe Balbi
2014-11-07 7:26 ` Robert Jarzmik
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=545B196F.2020303@zonque.org \
--to=daniel@zonque.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.