From: Greg KH <greg@kroah.com>
To: Andrew Zabolotny <zap@homelink.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Backlight and LCD module patches [1]
Date: Thu, 24 Jun 2004 14:34:52 -0700 [thread overview]
Message-ID: <20040624213452.GC2477@kroah.com> (raw)
In-Reply-To: <20040618095559.20763766.zap@homelink.ru>
On Fri, Jun 18, 2004 at 09:55:59AM +0400, Andrew Zabolotny wrote:
> On Thu, 17 Jun 2004 15:05:10 -0700
> Greg KH <greg@kroah.com> wrote:
> > Then you need to have a way to corrispond those devices together,
> > becides just a name. Use the pointer that you have provided to link
> > them together some way.
>
> There's no place to stuff that pointer into, because the load order of the
> framebuffer and lcd/backlight modules are not important (that's the reason for
> the notification chain), and at the time l/b modules are loaded there can be
> even no corresponding platform device (on my PDA for example, where platform
> device is also registered from a module).
>
> How about passing a pointer to struct dev, and a pointer to struct fbinfo to
> every l/b driver and asking them if they are for this device or not?
Ick, no.
How about just having every l/b driver containing a pointer to the
fbinfo that it is associated with? Isn't there some way you can keep
the pointer that you need around within the place that you need to use
it from eventually?
thanks,
greg k-h
next prev parent reply other threads:[~2004-06-24 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:35 Backlight and LCD module patches [1] Andrew Zabolotny
2004-06-17 19:47 ` Greg KH
2004-06-17 21:55 ` Andrew Zabolotny
2004-06-17 22:05 ` Greg KH
2004-06-18 5:55 ` Andrew Zabolotny
2004-06-24 21:34 ` Greg KH [this message]
2004-06-26 20:21 ` Andrew Zabolotny
2004-07-14 6:11 ` Greg KH
2004-07-14 19:14 ` 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=20040624213452.GC2477@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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