linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Patrick Mochel <mochel@transmeta.com>
Cc: Jeff Golds <jgolds@resilience.com>, Keith Owens <kaos@ocs.com.au>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.6-pre3
Date: Thu, 14 Jun 2001 09:51:52 +0100	[thread overview]
Message-ID: <20010614095152.Y13678@redhat.com> (raw)
In-Reply-To: <3B27DE0E.84025F41@resilience.com> <Pine.LNX.4.10.10106132305450.1433-100000@nobelium.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10106132305450.1433-100000@nobelium.transmeta.com>; from mochel@transmeta.com on Wed, Jun 13, 2001 at 11:39:49PM -0700

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

On Wed, Jun 13, 2001 at 11:39:49PM -0700, Patrick Mochel wrote:

> First off, the patch went into a pre-release of the kernel. Never would I
> trust a pre-release to be stable.

The issue is that of interface stability, as I'm sure you know.

> Second of all, if you look at the big picture, you may see the benefit in
> the change that was made. There is an effort to make Linux support power
> management, both at the system-wide level and at the driver level, in a
> much better way than it ever has. These changes are a manifestation of
> that effort. 

I've no doubt that new and better functions were necessary: but
couldn't it have been done in a source-compatible way?  New functions
rather than changed ones?

> Thirdly, these functions are rarely used.

Not every single driver is in Linus' tree.

I didn't see a feature-test macro either: did I miss it?

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-06-14  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  1:42 Linux-2.4.6-pre3 Linus Torvalds
2001-06-13  2:40 ` Linux-2.4.6-pre3 Keith Owens
2001-06-13  2:48   ` Linux-2.4.6-pre3 Jeff Garzik
2001-06-13  9:05     ` Linux-2.4.6-pre3 Tim Waugh
2001-06-13  2:49   ` Linux-2.4.6-pre3 Patrick Mochel
2001-06-13 21:41     ` Linux-2.4.6-pre3 Jeff Golds
2001-06-14  6:39       ` Linux-2.4.6-pre3 Patrick Mochel
2001-06-14  8:51         ` Tim Waugh [this message]
2001-06-14 12:47         ` Linux-2.4.6-pre3 Jeff Garzik
2001-06-14 18:02   ` Linux-2.4.6-pre3 Alan Cox
2001-06-14 21:39     ` Linux-2.4.6-pre3 Linus Torvalds
2001-06-13 21:11 ` Linux-2.4.6-pre3 José Luis Domingo López

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=20010614095152.Y13678@redhat.com \
    --to=twaugh@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=jgolds@resilience.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@transmeta.com \
    /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).