From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
LKML <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
Marcin Juszkiewicz <openembedded@hrw.one.pl>
Subject: Re: Git backlight subsystem tree
Date: Thu, 8 Feb 2007 13:23:14 -0800 [thread overview]
Message-ID: <20070208212314.GA21165@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702081830520.7686@pentafluge.infradead.org>
On Thu, Feb 08, 2007 at 06:32:02PM +0000, James Simmons wrote:
> On Thu, 8 Feb 2007, Richard Purdie wrote:
>
> > On Thu, 2007-02-08 at 15:28 +0000, James Simmons wrote:
> > > I have some patches that move the backlight away from using the class
> > > stuff. The only problem is the patch requires all backlight devices
> > > to be linked to a real struct device. Right now the acpi backligths are
> > > not.
> >
> > Why would you want to do that?
> >
> > The whole point of having this is so that backlights appear as a
> > standard interface under /sys/class/backlight.
> >
> > An example of why standardised interfaces are good would be someone
> > writing an applet for a handheld to control the backlight brightness.
> > With the class in place, the applet can easily work with any backlight.
> > Without it, it has to be written for each backlight.
> >
> > So this is a very strong NAK but I'm curious why you'd want to do it...
>
> I CC Greg to explain. The backlight class didn't go away. The way it is
> handled is different.
Have a pointer to the patch so I can help explain better?
As a short summary, 'struct class_device' is going away. Using a
'struct device' in its place is what the conversion should have just
done, no functionality change otherwise.
thanks,
greg k-h
next prev parent reply other threads:[~2007-02-08 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 2:30 Git backlight subsystem tree Richard Purdie
2007-02-08 3:01 ` Andrew Morton
2007-02-08 15:28 ` James Simmons
2007-02-08 17:59 ` Richard Purdie
2007-02-08 18:32 ` James Simmons
2007-02-08 19:37 ` Richard Purdie
2007-02-08 21:23 ` Greg KH [this message]
2007-02-08 21:54 ` James Simmons
2007-02-08 23:41 ` Greg KH
2007-02-08 23:50 ` Richard Purdie
2007-02-09 0:23 ` Greg KH
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=20070208212314.GA21165@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openembedded@hrw.one.pl \
--cc=rpurdie@rpsys.net \
/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.