From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [RFC] add class/video to fb drivers - Take 2
Date: Wed, 20 Aug 2003 14:26:26 -0700 [thread overview]
Message-ID: <20030820212626.GA4854@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308202044280.9662-100000@phoenix.infradead.org>
On Wed, Aug 20, 2003 at 10:16:13PM +0100, James Simmons wrote:
>
> > Ok, here's a smaller version of the patch, that doesn't break any fb
> > drivers. Only those that have a struct device associated with them
> > should be changed (and that's just a 1 line addition). I think it's
> > much better because of this.
>
> Nice :-) Will apply tonight. Do you have any issues still with this
> approach. You talked about the issue of dynamically creating the data. Is
> this probnlem still present in this patch.
Well, it's not "ideal" but it will do for 2.6 to use this patch. If you
look at the tty core, it's the same way that currently works.
Ideally in 2.7 I'd like to convert to have all fb drivers create the
fb_info structure dynamically, but that's much to big of a change to do
this late in the 2.6 development cycle.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-20 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 0:27 [RFC] add class/video to fb drivers Greg KH
2003-08-20 19:10 ` [RFC] add class/video to fb drivers - Take 2 Greg KH
2003-08-20 21:16 ` James Simmons
2003-08-20 21:26 ` Greg KH [this message]
2003-08-20 21:28 ` James Simmons
2003-08-20 21:33 ` 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=20030820212626.GA4854@kroah.com \
--to=greg@kroah.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).