From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Newest fbdev patch to go mainline.
Date: Tue, 10 Feb 2004 09:57:39 -0800 [thread overview]
Message-ID: <20040210175739.GF28111@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402101750150.6600-100000@phoenix.infradead.org>
On Tue, Feb 10, 2004 at 05:51:26PM +0000, James Simmons wrote:
>
> One more thing. What should I use for devices like vesafb? Should I use
> the platform_bus_type like sa1100fb.c?
That sounds reasonable, if there is no other place the vesafb device
lives off of in the driver model.
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Newest fbdev patch to go mainline.
Date: Tue, 10 Feb 2004 09:57:39 -0800 [thread overview]
Message-ID: <20040210175739.GF28111@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402101750150.6600-100000@phoenix.infradead.org>
On Tue, Feb 10, 2004 at 05:51:26PM +0000, James Simmons wrote:
>
> One more thing. What should I use for devices like vesafb? Should I use
> the platform_bus_type like sa1100fb.c?
That sounds reasonable, if there is no other place the vesafb device
lives off of in the driver model.
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-10 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 6:36 Newest fbdev patch to go mainline James Simmons
2004-02-10 17:35 ` Greg KH
2004-02-10 17:35 ` Greg KH
2004-02-10 17:49 ` James Simmons
2004-02-10 17:49 ` James Simmons
2004-02-10 17:51 ` James Simmons
2004-02-10 17:51 ` James Simmons
2004-02-10 17:57 ` Greg KH [this message]
2004-02-10 17:57 ` Greg KH
2004-02-10 17:58 ` Greg KH
2004-02-10 17:58 ` Greg KH
2004-02-10 19:04 ` Christoph Hellwig
2004-02-10 19:04 ` Christoph Hellwig
2004-02-11 15:53 ` James Simmons
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=20040210175739.GF28111@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 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.