From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: mach-omap2: remove NULL board_mux from board files
Date: Thu, 2 Dec 2010 13:36:42 +0200 [thread overview]
Message-ID: <20101202113642.GR5429@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1012021303240.27201@esdhcp041196.research.nokia.com>
On Thu, Dec 02, 2010 at 01:04:57PM +0200, Aaro Koskinen wrote:
>Hi,
>
>On Thu, 2 Dec 2010, Felipe Balbi wrote:
>>On Thu, Dec 02, 2010 at 11:53:42AM +0200, Aaro Koskinen wrote:
>>>diff --git a/arch/arm/mach-omap2/mux.h b/arch/arm/mach-omap2/mux.h
>>>index 350c04f..e224ab5 100644
>>>--- a/arch/arm/mach-omap2/mux.h
>>>+++ b/arch/arm/mach-omap2/mux.h
>>>@@ -133,6 +133,8 @@ static inline int omap_mux_init_signal(char
>>>*muxname, int val)
>>> return 0;
>>>}
>>>
>>>+static struct omap_board_mux *board_mux __initdata
>>>__attribute__((unused));
>>
>>how about __unused ??
>
>I don't think we have that:
>
> CC arch/arm/mach-omap2/mux.o
>In file included from arch/arm/mach-omap2/mux.c:39:
>arch/arm/mach-omap2/mux.h:136: error: expected ',' or ';' before '__unused'
>make[1]: *** [arch/arm/mach-omap2/mux.o] Error 1
>make: *** [arch/arm/mach-omap2] Error 2
sorry, it's __maybe_unused :-)
#define __maybe_unused __attribute__((unused))
--
balbi
prev parent reply other threads:[~2010-12-02 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 9:53 [PATCH v2] arm: mach-omap2: remove NULL board_mux from board files Aaro Koskinen
2010-12-02 10:37 ` Felipe Balbi
2010-12-02 11:04 ` Aaro Koskinen
2010-12-02 11:36 ` Felipe Balbi [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=20101202113642.GR5429@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--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).