All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	Patrick Mochel <mochel@osdl.org>
Subject: Re: Fix up power managment in 2.6
Date: Mon, 1 Sep 2003 11:33:45 +0200	[thread overview]
Message-ID: <20030901093344.GC155@elf.ucw.cz> (raw)
In-Reply-To: <20030901092646.B15370@flint.arm.linux.org.uk>

Hi!

> > Its the only way to have power managment working by 2.6.1.
> 
> Rubbish.  PM is now working here on ARM again - within a week of Pat's
> change.

As you said, you are not using kernel/power.

> > Lots of
> > work went into pm during 2.5 series, and Patrick invalidated all that
> > with one, 140KB, untested and broken patch (and he managed to break
> > about all rules about patch submission).
> 
> I agree that it needed public review _before_ hitting Linus' tree - a
> change of that magnitude with only half the subsystems fixed up should
> not go directly into Linus' tree without review.

Good. [I believe it was big enough to require testing on separate tree
(-mm? -ac?) before going mainline].

> > It is not possible to fix damage he done within week.
> 
> It is my understanding that the old PM in 2.5 was not suitable for
> the PPC architecture and the new PM model is.  As far as the drivers
> are concerned, the interface presented is a definite improvement on
> what there was before (there are a few things which I'd like to see
> further improvement on, but that's not a subject for discussion in
> this thread.)

I only see dm getting more and more complicated :-(.

> I don't particularly care about kernel/power/* because its not useful
> for me - whereas you obviously do.  Maybe that's where your axe is
> grinding.  But whatever, don't throw the baby (driver model changes)
> out with the bath water.

kernel/power/* changes are worst, because that's subsystem I should be
maintainer of. Driver model changes are quite bad, too, because they
mean we should go over all drivers and fix them. And driver failures
are often pretty subtle.

> And finally, there's longer than a week to fix it. 8)

I'm not looking forward to another half-a-year before kernel gets into
state where it was in -test3.

I still want that crap killed, at least because of the way *how* it
was merged. Altrough killing kernel/power/* would be good start, and
maybe it would lead us to a state where dm changes can be debugged. 

								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-09-01 20:38 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 23:28 Fix up power managment in 2.6 Pavel Machek
2003-09-01  6:57 ` Russell King
2003-09-01  8:11   ` Pavel Machek
2003-09-01  8:26     ` Russell King
2003-09-01  9:33       ` Pavel Machek [this message]
2003-09-01 16:28 ` Linus Torvalds
2003-09-01 21:12   ` Pavel Machek
2003-09-01 21:52     ` Russell King
2003-09-01 22:19       ` Pavel Machek
2003-09-01 22:30         ` Russell King
2003-09-01 22:40           ` Pavel Machek
2003-09-01 22:48             ` Russell King
2003-09-02 17:17             ` Greg KH
2003-09-03 15:13               ` Pavel Machek
2003-09-02 10:21           ` Benjamin Herrenschmidt
2003-09-03 13:02             ` Alan Cox
2003-09-03 13:31               ` Benjamin Herrenschmidt
2003-09-03 17:08               ` Pavel Machek
2003-09-05 20:42             ` Pavel Machek
2003-09-01 22:55     ` Patrick Mochel
2003-09-01 23:38       ` Pavel Machek
2003-09-02  0:52         ` Patrick Mochel
2003-09-02  9:02           ` Pavel Machek
2003-09-02  9:47           ` Pavel Machek
2003-09-02 16:11             ` Patrick Mochel
2003-09-03 16:21               ` Pavel Machek
2003-09-03 23:17                 ` Patrick Mochel
2003-09-03 17:49               ` Pavel Machek
2003-09-03 17:59                 ` bill davidsen
2003-09-03 23:20                 ` Patrick Mochel
2003-09-05  9:33                   ` Pavel Machek
2003-09-03 20:03               ` Bill Davidsen
2003-09-03 22:14                 ` Pavel Machek
2003-09-04  4:06                   ` Bill Davidsen
2003-09-04 14:52                     ` Patrick Mochel
2003-09-02 10:29       ` Jan Rychter
2003-09-05  5:58       ` Rob Landley
2003-09-05 10:26         ` Pavel Machek
2003-09-05 10:56           ` Michael Frank
2003-09-05 11:08             ` Pavel Machek
2003-09-05 11:51               ` Michael Frank
2003-09-05 12:01                 ` Pavel Machek
2003-09-05 17:47         ` Patrick Mochel
2003-09-05 18:02           ` Jeff Garzik
2003-09-05 18:13             ` Patrick Mochel
2003-09-05 21:46               ` Jeff Garzik
2003-09-05 18:57             ` Rob Landley
2003-09-05 19:06               ` Pavel Machek
2003-09-05 20:09                 ` Keyboard stuff (was Re: Fix up power managment in 2.6) Rob Landley
2003-09-05 20:31                   ` Pavel Machek
2003-09-05 20:01             ` Fix up power managment in 2.6 Richard A Nelson
2003-09-05 21:45               ` Jeff Garzik
2003-09-05 18:49           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:13 Nicolas Mailhot

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=20030901093344.GC155@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=torvalds@osdl.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.