From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Dave Airlie <airlied@linux.ie>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Antonino A. Daplas" <adaplas@gmail.com>
Subject: Re: [PATCH] fbdev sysfs imrovements
Date: Tue, 20 Mar 2007 17:14:26 -0700 [thread overview]
Message-ID: <20070321001426.GA29665@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703192055090.27580@pentafluge.infradead.org>
On Tue, Mar 20, 2007 at 02:25:49PM +0000, James Simmons wrote:
>
> This patch does several things to allow the underlying hardware to be
> shared amount many devices. The most important thing is the use of
> the created device via device_create instead of the hardware device. No
> longer should fbdev drivers use the xxx_set_drvdata with the parent
> bus device. The second change is having a bus independent power management
> for the framebuffer driver. The final change is using the release method
> to cleanup the device. The reason again is to make the fbdev driver
> independent of the bus parent device. Feedback is welcomed.
Looks good to me.
thanks,
greg k-h
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-21 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 14:25 [PATCH] fbdev sysfs imrovements James Simmons
2007-03-21 0:14 ` Greg KH [this message]
2007-03-27 3:58 ` Andrew Morton
2007-03-27 6:14 ` Paul Mackerras
2007-03-27 6:20 ` Andrew Morton
2007-04-01 0:56 ` James Simmons
2007-04-01 1:24 ` Andrew Morton
2007-04-05 13:46 ` 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=20070321001426.GA29665@kroah.com \
--to=greg@kroah.com \
--cc=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=geert@linux-m68k.org \
--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).