public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Hanno Böck" <hanno@gmx.de>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	pavel@ucw.cz, arjanv@redhat.com, marcelo@conectiva.com.br,
	linux-kernel@vger.kernel.org, acpi-devel@sourceforge.net
Subject: Re: [ACPI] RE: [BK PATCH] ACPI updates
Date: Fri, 6 Dec 2002 07:29:32 -0500	[thread overview]
Message-ID: <20021206072932.B16173@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021206125943.2199892e.hanno@gmx.de>; from hanno@gmx.de on Fri, Dec 06, 2002 at 12:59:43PM +0100

On Fri, Dec 06, 2002 at 12:59:43PM +0100, Hanno Böck wrote:
> > Well after communicating with Marcelo it sounds like he'd like to hold off
> > taking it in 2.4.21 because IDE changes take priority, and two big changes
> > at once is too many for a stable kernel revision.
> 

> I think this is a very bad news. In my opinion, the ACPI-patch
> is the most-needed kernel-patch at the moment. For many laptop-users
> that don't know about this patch, Linux is nearly
> unuseable. 

the 2.4 patch doesnt' actually offer suspend/resume capabilities; what
else did you have in mind as required ?

  reply	other threads:[~2002-12-06 12:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  1:36 [BK PATCH] ACPI updates Grover, Andrew
2002-12-06 11:59 ` [ACPI] " Hanno Böck
2002-12-06 12:29   ` Arjan van de Ven [this message]
2002-12-06 13:17     ` Matthew Wilcox
2002-12-06 15:06       ` Alan Cox
2002-12-09 16:09       ` Marcelo Tosatti
2002-12-09 19:12         ` Matthew Wilcox
2002-12-09 19:17           ` Arjan van de Ven
2002-12-09 19:45             ` Bjorn Helgaas
2002-12-09 19:17           ` Jeff Garzik
2002-12-06 16:50 ` Pavel Machek

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=20021206072932.B16173@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=acpi-devel@sourceforge.net \
    --cc=andrew.grover@intel.com \
    --cc=hanno@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=pavel@ucw.cz \
    /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