From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make radeon_reinitialize_M10() absent if its reference is #ifdef'd out
Date: Wed, 15 Apr 2009 18:40:27 +0200 [thread overview]
Message-ID: <1239813627.7443.18.camel@pasglop> (raw)
In-Reply-To: <20090414155651.27671.36394.stgit@warthog.procyon.org.uk>
On Tue, 2009-04-14 at 16:56 +0100, David Howells wrote:
> Make radeon_reinitialize_M10() absent if its reference is #ifdef'd out
> (if
> CONFIG_PM=n or CONFIG_PPC_PMAC=n. Otherwise a warning is given:
>
> CC drivers/video/aty/radeon_pm.o
> drivers/video/aty/radeon_pm.c:1720: warning: 'radeon_reinitialize_M10'
> defined but not used
>
> Signed-off-by: David Howells <dhowells@redhat.com>
Nah. You ifdef it with CONFIG_PPC_PMAC, but it can be used on x86
too (see the "BUGFIX" entries).
Cheers,
Ben.
> ---
>
> drivers/video/aty/radeon_pm.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
>
> diff --git a/drivers/video/aty/radeon_pm.c
> b/drivers/video/aty/radeon_pm.c
> index 97a1f09..8655bbd 100644
> --- a/drivers/video/aty/radeon_pm.c
> +++ b/drivers/video/aty/radeon_pm.c
> @@ -1716,6 +1716,7 @@ static void radeon_pm_m10_reconfigure_mc(struct radeonfb_info *rinfo)
> OUTREG(MC_IND_INDEX, 0);
> }
>
> +#if defined(CONFIG_PM) && defined(CONFIG_PPC_PMAC)
> static void radeon_reinitialize_M10(struct radeonfb_info *rinfo)
> {
> u32 tmp, i;
> @@ -1940,6 +1941,7 @@ static void radeon_reinitialize_M10(struct radeonfb_info *rinfo)
> */
> radeon_pm_m10_enable_lvds_spread_spectrum(rinfo);
> }
> +#endif /* CONFIG_PM && CONFIG_PPC_PMAC */
>
> #ifdef CONFIG_PPC_OF
>
next prev parent reply other threads:[~2009-04-15 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 15:56 [PATCH] Make radeon_reinitialize_M10() absent if its reference is #ifdef'd out David Howells
2009-04-15 16:40 ` Benjamin Herrenschmidt [this message]
2009-04-15 17:03 ` David Howells
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=1239813627.7443.18.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.