From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm: mach-davinci: mark __maybe_unused struct
Date: Thu, 12 Sep 2013 16:13:29 +0530 [thread overview]
Message-ID: <52319AD1.9020305@ti.com> (raw)
In-Reply-To: <1378317646-21262-1-git-send-email-computersforpeace@gmail.com>
On Wednesday 04 September 2013 11:30 PM, Brian Norris wrote:
> If neither CONFIG_SND_DM365_AIC3X_CODEC nor CONFIG_SND_DM365_VOICE_CODEC
> are defined, we may get warnings like:
>
> arch/arm/mach-davinci/board-dm365-evm.c:179:33: warning: 'dm365_evm_snd_data' defined but not used [-Wunused-variable]
>
> To fix this, just mark the struct as __maybe_unused.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail•com>
> Cc: Sekhar Nori <nsekhar@ti•com>
> Cc: Kevin Hilman <khilman@deeprootsystems•com>
> Cc: Russell King <linux@arm•linux.org.uk>
Thanks, will queue this for -rc cycle. For future, please note that
subject line of DaVinci patches need to be prefixed "ARM: davinci: ".
Also, the subject should highlight the answer to "Why?" rather than
"How?". So, while committing I changed the headline to:
ARM: davinci: dm365 evm: fix unused variable warning
Thanks,
Sekhar
prev parent reply other threads:[~2013-09-12 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 18:00 [PATCH] arm: mach-davinci: mark __maybe_unused struct Brian Norris
2013-09-12 10:43 ` Sekhar Nori [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=52319AD1.9020305@ti.com \
--to=nsekhar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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