From: Nigel Cunningham <ncunningham@linuxmail.org>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Re: Devices don't get linked to their class.
Date: Tue, 07 Sep 2004 07:56:51 +1000 [thread overview]
Message-ID: <1094507810.2304.43.camel@laptop.cunninghams> (raw)
In-Reply-To: <32016.10.250.10.1.1094456212.squirrel@sq04.pol.net>
Hi.
On Mon, 2004-09-06 at 17:36, Antonino A. Daplas wrote:
> I'll modify the patch a little bit so struct fb_info has a struct device
> *device. This way, we need not add a new parameter to
> register_framebuffer(), and we don't need to modify all drivers, only
> those where we can set the device field.
Sounds great. I knew there was more than one way of skinning this cat,
and just went for the simplest :>
Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
Many today claim to be tolerant. True tolerance, however, can cope with others
being intolerant.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-06 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 5:02 Devices don't get linked to their class Nigel Cunningham
2004-09-04 12:41 ` Antonino A. Daplas
2004-09-05 6:21 ` Nigel Cunningham
2004-09-05 10:40 ` Antonino A. Daplas
2004-09-05 21:45 ` Nigel Cunningham
2004-09-06 3:38 ` [PATCH] " Nigel Cunningham
[not found] ` <32016.10.250.10.1.1094456212.squirrel@sq04.pol.net>
2004-09-06 21:56 ` Nigel Cunningham [this message]
2004-09-07 19:50 ` Kronos
2004-09-08 0:55 ` Antonino A. Daplas
2004-09-08 3:21 ` Nigel Cunningham
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=1094507810.2304.43.camel@laptop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.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 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).