linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pxa: mark ezx structures as __maybe_unused
Date: Wed, 09 Dec 2015 21:46:30 +0100	[thread overview]
Message-ID: <8737vbl595.fsf@belgarion.home> (raw)
In-Reply-To: <7455848.ygDvrz6r6S@wuerfel> (Arnd Bergmann's message of "Wed, 09 Dec 2015 17:36:03 +0100")

Arnd Bergmann <arnd@arndb.de> writes:

> The ezx platform contains multiple machine descriptors, but not all
> of them use all of the data structures, and it's possible to disable
> all of the machines, which produces some harmless warnings:
>
> mach-pxa/ezx.c:53:26: warning: 'ezx_pwm_lookup' defined but not used [-Wunused-variable]
> mach-pxa/ezx.c:86:31: warning: 'ezx_fb_info_1' defined but not used [-Wunused-variable]
> mach-pxa/ezx.c:107:31: warning: 'ezx_fb_info_2' defined but not used [-Wunused-variable]
> mach-pxa/ezx.c:113:32: warning: 'ezx_devices' defined but not used [-Wunused-variable]
> mach-pxa/ezx.c:117:22: warning: 'ezx_pin_config' defined but not used [-Wunused-variable]
>
> This marks all those structures as __maybe_unused to avoid the warnings.
> Obviously a configuration that contains the ezx platform but no specific
> model is a bit silly, but it should not cause compile-time warnings.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>

I think you'll take that through your tree, as I'm passing the v4.5 pull. If you
want me to take them, just tell me, but I think v4.5 is already prepared on your
side as I've seen a mail from Boris talking about pxa patches going through mtd
tree for v4.5.

Cheers.

--
Robert

  reply	other threads:[~2015-12-09 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 16:36 [PATCH] ARM: pxa: mark ezx structures as __maybe_unused Arnd Bergmann
2015-12-09 20:46 ` Robert Jarzmik [this message]
2015-12-09 21:27   ` Arnd Bergmann

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=8737vbl595.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --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).