From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Add Sequoia RAM-booting target
Date: Thu, 07 May 2009 14:22:45 -0500 [thread overview]
Message-ID: <4A033505.90909@freescale.com> (raw)
In-Reply-To: <20090507190628.0231F83420E8@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Stefan,
>
> in message <200905071739.56301.sr@denx.de> you wrote:
>>>> Linux kernel btw. Here the macro "__maybe_unsed" is defined to
>>>> "__attribute__((unused))".
>>> In many cases? a rgrep on a recent kernel counts 84 incantations, which
>>> is not much for the Linux kernel, I believe.
>> Perhaps it's quite new to the Linux kernel. I just spotted it the first time a
>> few weeks ago and thought: "What a nice way to remove some of the ugly
>> #ifdef's in U-Boot!". :)
>
> My understanding was that this is (only?) intended for function
> declarations to silence warnings about unused function arguments
> (which may be necessary anyway for compatible call interface with
> other functions that actually need this arg).
Unusued function argument warnings are not normally enabled in the first
place (it's a separate warning class from unused variables).
-Scott
next prev parent reply other threads:[~2009-05-07 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 15:01 [U-Boot] [PATCH] ppc4xx: Add Sequoia RAM-booting target Stefan Roese
2009-05-07 12:25 ` Detlev Zundel
2009-05-07 13:30 ` Stefan Roese
2009-05-07 15:06 ` Detlev Zundel
2009-05-07 15:39 ` Stefan Roese
2009-05-07 19:06 ` Wolfgang Denk
2009-05-07 19:22 ` Scott Wood [this message]
2009-05-08 4:30 ` Stefan Roese
2009-05-08 12:34 ` Detlev Zundel
2009-05-07 18:42 ` Wolfgang Denk
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=4A033505.90909@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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