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, 17 Jun 2004 15:05:10 -0700 [thread overview]
Message-ID: <20040617220510.GA4122@kroah.com> (raw)
In-Reply-To: <20040618015504.661a50a9.zap@homelink.ru>
On Fri, Jun 18, 2004 at 01:55:04AM +0400, Andrew Zabolotny wrote:
> On Thu, 17 Jun 2004 12:47:39 -0700
> Greg KH <greg@kroah.com> wrote:
>
> > So no, I'm not going to accept this, you need to change your lcd code to
> > pass around pointers to the proper structures, instead of trying to rely
> > on the name of a device. Because of this, I'm not going to apply your
> > second patch.
> I think you missed something. It doesn't rely on the name of the device while
> registering/unregistering, I've changed this, look:
No, I saw your change.
> extern int lcd_device_register(const char *name, void *devdata,
> struct lcd_properties *lp,
> struct lcd_device **alloc_ld);
That function should be:
struct lcd_device lcd_device_register(const char *name, void *devdata,
struct lcd_properties *lp);
instead. Then return an ERR_PTR() if you have an error.
> Now this:
>
> extern struct lcd_device *lcd_device_find(const char *name);
>
> It needs a char* argument because there's no other easy way to find the
> correspondence between framebuffer devices and lcd/backlight devices
> corresponding to that framebuffer device.
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.
thanks,
greg k-h
next prev parent reply other threads:[~2004-06-17 22:06 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 [this message]
2004-06-18 5:55 ` Andrew Zabolotny
2004-06-24 21:34 ` Greg KH
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=20040617220510.GA4122@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