From: Greg KH <greg@kroah.com>
To: Kronos <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs class patches - take 2 [0/5]
Date: Wed, 24 Dec 2003 08:45:15 -0800 [thread overview]
Message-ID: <20031224164514.GB29365@kroah.com> (raw)
In-Reply-To: <20031224142717.GA3133@dreamland.darkstar.lan>
On Wed, Dec 24, 2003 at 03:27:17PM +0100, Kronos wrote:
> Greg KH <greg@kroah.com> ha scritto:
> > > On Tue, Dec 23, 2003 at 04:57:56PM -0500, Jeff Garzik wrote:
> > > Interesting... I bet that will be useful to the iPAQ folks (I've been
> > > wading through their patches lately), as they have created a couple
> > > ultra-simple classes for SoC devices and such.
> >
> > I bet it will. I've ported my old frame buffer patch to use it, and
> > it saved a lot of code.
> >
> > Hm, I wonder if the frame buffer people ever intregrated that patch...
>
> I had a patch that add class_device to struct fb_info. This was 3-4
> months ago.
So all of the frame buffer drivers have to be changed to dynamically
allocate the fb_info structure? That's the "proper" way to do this, but
I felt it was a bit too late in the 2.6 development cycle to try to
intregrate such a large change in...
Oh well,
greg k-h
prev parent reply other threads:[~2003-12-24 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 21:24 Greg KH
2003-12-23 21:26 ` [PATCH] add "simple" class device support [1/5] Greg KH
2003-12-23 21:27 ` [PATCH] remove tty class device logic [2/5] Greg KH
2003-12-23 21:29 ` [PATCH] add sysfs mem class [3/5] Greg KH
2003-12-23 21:30 ` [PATCH] add sysfs misc class [4/5] Greg KH
2003-12-23 21:31 ` [PATCH] add sysfs vc class [5/5] Greg KH
2003-12-23 21:57 ` [PATCH] sysfs class patches - take 2 [0/5] Jeff Garzik
2003-12-23 22:07 ` Greg KH
2003-12-23 23:01 ` [PATCH] add video sysfs class [6/5] Greg KH
2003-12-24 14:27 ` [PATCH] sysfs class patches - take 2 [0/5] Kronos
2003-12-24 16:45 ` Greg KH [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=20031224164514.GB29365@kroah.com \
--to=greg@kroah.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.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®