From: Andrew Morton <akpm@linux-foundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb backlight fix
Date: Mon, 22 Feb 2010 12:23:54 -0800 [thread overview]
Message-ID: <20100222122354.50a85575.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1002161817570.23940@casper.infradead.org>
On Tue, 16 Feb 2010 18:19:21 +0000 (GMT) James Simmons <jsimmons@infradead.org> wrote:
>
> A simple patch to allow radeonfb to compile if the backlight option is
> set.
>
> diff --git a/drivers/video/aty/radeon_base.c b/drivers/video/aty/radeon_base.c
> index 6c37e8e..2c01726 100644
> --- a/drivers/video/aty/radeon_base.c
> +++ b/drivers/video/aty/radeon_base.c
> @@ -276,7 +276,7 @@ static int nomtrr = 0;
> #endif
> static int force_sleep;
> static int ignore_devlist;
> -#ifdef CONFIG_PMAC_BACKLIGHT
> +#ifdef CONFIG_FB_RADEON_BACKLIGHT
> static int backlight = 1;
> #else
> static int backlight = 0;
Changelog is very poor. It doesn't tell us what the error was, nor how
the patch fixes it.
I attempted to reverse-engineer the patch but gave up.
radeonfb_bl_init() is omitted from the link if
CONFIG_FB_RADEON_BACKLIGHT=n. And this code:
if (backlight)
radeonfb_bl_init(rinfo);
will emit a call to radeonfb_bl_init() regardless of the value of
`backlight', so as far as I can tell, there will be a linkage error
with CONFIG_FB_RADEON_BACKLIGHT=n both before and after your patch.
So. Please resend, with a proper description. And a Signed-off-by: line.
prev parent reply other threads:[~2010-02-22 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 18:19 James Simmons
2010-02-22 20:23 ` Andrew Morton [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=20100222122354.50a85575.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®