All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: "legolas558@users.sourceforge.net" <legolas558@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	mnowak@redhat.com, shaohua.li@intel.com
Subject: Re: Laptop keyboard unusable when ACPI is active
Date: Fri, 23 Nov 2007 23:21:43 -0500	[thread overview]
Message-ID: <200711232321.44048.lenb@kernel.org> (raw)
In-Reply-To: <47452EAC.5060801@users.sourceforge.net>

On Thursday 22 November 2007 02:24, legolas558@users.sourceforge.net wrote:

> It is also important to note that this bug always comes with bug 8740 
> http://bugzilla.kernel.org/show_bug.cgi?id=8740 (also confirmed and also 
> an ACPI issue).

No, 8740 is not an ACPI issue.
http://bugzilla.kernel.org/show_bug.cgi?id=8740#c2

-Len

  reply	other threads:[~2007-11-24  4:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 21:42 [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c legolas558
2007-10-11  8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
2007-10-12 11:52   ` Laptop keyboard unusable when ACPI is active legolas558
2007-11-22  7:24     ` legolas558
2007-11-24  4:21       ` Len Brown [this message]
2007-11-24 19:08         ` legolas558
2007-10-18 19:52   ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
2007-10-20 11:47     ` legolas558
2007-10-20 18:33       ` Pavel Machek
2007-10-21  9:43         ` legolas558
2007-11-24  4:27           ` Len Brown
2007-11-24 19:14             ` legolas558
2007-10-21 11:07     ` legolas558
  -- strict thread matches above, loose matches on Subject: below --
2007-11-23  7:44 Laptop keyboard unusable when ACPI is active Mats Johannesson
2007-11-23  7:44 ` Mats Johannesson
2007-11-24  4:04 ` Len Brown

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=200711232321.44048.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=legolas558@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnowak@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=shaohua.li@intel.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.