linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	James Simmons <jsimmons@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] fbdev and power management
Date: Sat, 5 Jan 2002 12:13:40 +0100	[thread overview]
Message-ID: <20020105111340.GA2254@zaurus.ucw.cz> (raw)
In-Reply-To: <20030709151032.A22612@flint.arm.linux.org.uk>

Hi!

> I'm slightly concerned by this.  There are a growing amount of drivers
> in 2.5 which are being made to work with the existing power management
> system.  This "new" system seems to have been hanging around for about
> 4 months now with no visible further work, presumably so that a paper
> can be presented before its release.

I believe it is bad idea to change driver
model again in 2.6.x-pre. I believe current
solution is pretty much okay.
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...


  reply	other threads:[~2003-07-14 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030704042052.GL4359@himi.org>
2003-07-08 23:25 ` fbdev and power management James Simmons
2003-07-09 11:35   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-07-09 14:10     ` Russell King
2002-01-05 11:13       ` Pavel Machek [this message]
2003-07-14 16:34         ` Benjamin Herrenschmidt
2003-07-14 20:11           ` Pavel Machek
2003-07-09 17:45       ` James Simmons
2003-07-09 17:49         ` Benjamin Herrenschmidt

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=20020105111340.GA2254@zaurus.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=benh@kernel.crashing.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).