From: Kumar Gala <galak@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Mark prop unused in early_init_dt_scan_chosen().
Date: Wed, 9 May 2007 22:39:36 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705092238390.29512@localhost.localdomain> (raw)
In-Reply-To: <20070508171451.GA8893@ld0162-tx32.am.freescale.net>
On Tue, 8 May 2007, Scott Wood wrote:
> The prop variable is only referenced when initrd support is
> turned on.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> arch/powerpc/kernel/prom.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/prom.c b/arch/powerpc/kernel/prom.c
> index caef555..6705459 100644
> --- a/arch/powerpc/kernel/prom.c
> +++ b/arch/powerpc/kernel/prom.c
> @@ -720,7 +720,7 @@ static int __init early_init_dt_scan_chosen(unsigned long node,
> const char *uname, int depth, void *data)
> {
> unsigned long *lprop;
> - u32 *prop;
> + u32 __attribute__((unused)) *prop;
is this the desired way to remove warnings related to CONFIG_ options? I
know in the past we'd wrap it with a #ifdef CONFIG_FOO
> unsigned long l;
> char *p;
>
>
- k
next prev parent reply other threads:[~2007-05-10 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 17:14 [PATCH] Mark prop unused in early_init_dt_scan_chosen() Scott Wood
2007-05-08 23:56 ` Michael Ellerman
2007-05-09 0:41 ` David Gibson
2007-05-10 3:39 ` Kumar Gala [this message]
2007-05-10 7:39 ` Geert Uytterhoeven
2007-05-10 15:54 ` Scott Wood
2007-05-10 16:06 ` Geert Uytterhoeven
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=Pine.LNX.4.64.0705092238390.29512@localhost.localdomain \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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).