From: Johannes Berg <johannes@sipsolutions.net>
To: christoph.paasch@uclouvain.be
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
chunkeey@googlemail.com
Subject: Re: [PATCH] p54: fix compiler-warning when no P54_LEDS are configured
Date: Wed, 29 Dec 2010 19:13:10 +0100 [thread overview]
Message-ID: <1293646390.3546.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201012291816.27302.christoph.paasch@uclouvain.be>
On Wed, 2010-12-29 at 18:16 +0100, Christoph Paasch wrote:
> +#if defined(CONFIG_DEBUG_MUTEXES) || defined(CONFIG_P54_LEDS)
> struct p54_common *priv = dev->priv;
> +#endif
It seems a lot simpler to just add __maybe_unused...
johannes
prev parent reply other threads:[~2010-12-29 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 15:14 [PATCH] p54: fix compiler-warning when no P54_LEDS are configured Christoph Paasch
2010-12-29 16:19 ` Larry Finger
2010-12-29 16:46 ` Larry Finger
2010-12-29 17:16 ` Christoph Paasch
2010-12-29 17:32 ` Larry Finger
2010-12-29 18:13 ` Johannes Berg [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=1293646390.3546.17.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=christoph.paasch@uclouvain.be \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).