linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Andrew Zabolotny <zap@homelink.ru>
Subject: Re: [Bugme-new] [Bug 4047] New: kerenl failt to kompile
Date: Tue, 18 Jan 2005 05:04:04 +0800	[thread overview]
Message-ID: <200501180504.07500.adaplas@hotpop.com> (raw)
In-Reply-To: <20050117004141.2dcb1e0f.zap@homelink.ru>

On Monday 17 January 2005 05:41, Andrew Zabolotny wrote:
> Hello!
>
> > Date: Sun, 16 Jan 2005 03:14:57 -0800
> > From: bugme-daemon@osdl.org
> > To: bugme-new@lists.osdl.org
> > Subject: [Bugme-new] [Bug 4047] New: kerenl failt to kompile
> >
> > http://bugme.osdl.org/show_bug.cgi?id=4047
> >
> >           Summary: kerenl failt to kompile
> >    Kernel Version: 2.6.11-rc1-mm1
> >            Status: NEW
> >          Severity: blocking
> >             Owner: jsimmons@infradead.org
> >         Submitter: bug-track@fisher-privat.net
> >
> >
> > Distribution:Debian Sarge
> >
> > Problem Description:
> > LD      init/built-in.o
> >  LD      .tmp_vmlinux1
> >
> > drivers/built-in.o(.text+0x9bfa): In function `lcd_device_register':
> > : undefined reference to `fb_register_client'
>
> Here's an obvious fix plus a minor enhancement.

Would it be better if backlight/lcd support is not fully dependent on the
framebuffer? 

It's your call, so I'm still submitting this patch to akpm.

Tony 




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-17 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:41 [Bugme-new] [Bug 4047] New: kerenl failt to kompile Andrew Zabolotny
2005-01-17 21:04 ` Antonino A. Daplas [this message]
2005-01-18 19:17   ` Andrew Zabolotny

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=200501180504.07500.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=zap@homelink.ru \
    /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).