public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: S <nil-DDRJgj0kmXRGcL5Ds9yaJ6VXKuFTiq87@public.gmane.org>
Cc: "Hanno Böck" <hanno-Mmb7MZpHnFY@public.gmane.org>,
	acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Kernel 2.4.22?
Date: Fri, 4 Apr 2003 11:31:24 +0200	[thread overview]
Message-ID: <20030404093123.GA311@elf.ucw.cz> (raw)
In-Reply-To: <1049378019.1769.24.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>

Hi!

> This has already been discussed, and for "Marcelo team " is a to big
> patch to be included in kernel tree. I had thought about an solution, I
> think that Andrew Grover has reason.
> What we need to do, is prove that the code that not is under
> drivers/acpi, does not have any effect to others functionality in
> kernel, and put acpi has experimental.  

IDE changes got priority, but I guess we should have good chance
getting into 2.4.22.
							Pavel

-- 
When do you have heart between your knees?


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

      parent reply	other threads:[~2003-04-04  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 12:07 Kernel 2.4.22? Hanno Böck
     [not found] ` <20030403140709.75be5865.hanno-Mmb7MZpHnFY@public.gmane.org>
2003-04-03 13:53   ` Sérgio Monteiro Basto
     [not found]     ` <1049378019.1769.24.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-04-04  9:31       ` Pavel Machek [this message]

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=20030404093123.GA311@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=hanno-Mmb7MZpHnFY@public.gmane.org \
    --cc=nil-DDRJgj0kmXRGcL5Ds9yaJ6VXKuFTiq87@public.gmane.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