From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Steven King <sfking@fdwdc.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Zhang Rui <rui.zhang@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after?undocking
Date: Sun, 07 Sep 2008 15:39:11 -0700 [thread overview]
Message-ID: <48C4580F.4000804@goop.org> (raw)
In-Reply-To: <48BEA77A.5050104@dbservice.com>
Tomas Carnecky wrote:
> I don't know whether I should ROFL or be sad, but: In the 2.6.26 stable
> tree the bay driver (ACPI_BAY) is marked as EXPERIMENTAL, and now you're
> saying that it's obsolete. Do features go right from experimental to
> obsolete now?
Sure. Some experiments don't work out.
J
next prev parent reply other threads:[~2008-09-07 22:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 22:35 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 3:17 ` Zhang Rui
2008-09-01 10:50 ` Tomas Carnecky
[not found] ` <48BBC8FC.1020809-ix/z9KG6G0Jl57MIdRCFDg@public.gmane.org>
2008-09-01 11:28 ` Henrique de Moraes Holschuh
2008-09-01 11:28 ` Henrique de Moraes Holschuh
2008-09-01 12:16 ` Tomas Carnecky
2008-09-01 18:34 ` Matthew Garrett
2008-09-01 19:05 ` Steven King
[not found] ` <200809011205.05253.sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
2008-09-03 14:45 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after?undocking Holger Macht
2008-09-03 14:45 ` Holger Macht
2008-09-03 15:04 ` Tomas Carnecky
2008-09-03 15:04 ` Tomas Carnecky
2008-09-07 22:39 ` Jeremy Fitzhardinge [this message]
2008-09-03 21:28 ` Henrique de Moraes Holschuh
2008-09-03 21:28 ` Henrique de Moraes Holschuh
2008-09-05 9:00 ` Holger Macht
2008-09-08 22:17 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 11:34 ` Matthew Garrett
2008-09-01 18:21 ` Steven King
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=48C4580F.4000804@goop.org \
--to=jeremy@goop.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfking@fdwdc.com \
--cc=tom@dbservice.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 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.