From: Keith Packard <keithp@keithp.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: 2.6.39-rc2 regression: X201s fails to resume b77dcf8460ae57d4eb9fd3633eb4f97b8fb20716
Date: Fri, 08 Apr 2011 16:13:28 -0700 [thread overview]
Message-ID: <yunaag0tjzb.fsf@aiko.keithp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104082340020.2724@localhost6.localdomain6>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Fri, 8 Apr 2011 23:44:51 +0200 (CEST), Thomas Gleixner <tglx@linutronix.de> wrote:
> Can the bluetooth folks please have a look at that ASAP? The obvious
> fast fix for Linus tree is to revert the second hunk for now, but this
> needs to be fixed proper.
Who will submit this patch? I'd rather have your name on it so that
people come complain at you...
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-04-08 23:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 7:44 2.6.39-rc2 regression: X201s fails to resume b77dcf8460ae57d4eb9fd3633eb4f97b8fb20716 Keith Packard
2011-04-06 22:31 ` Thomas Gleixner
2011-04-08 21:44 ` Thomas Gleixner
2011-04-08 23:13 ` Keith Packard [this message]
2011-04-09 0:08 ` Vinicius Costa Gomes
2011-04-09 2:03 ` Keith Packard
2011-04-11 15:58 ` Gustavo F. Padovan
2011-04-11 16:13 ` Thomas Gleixner
2011-04-11 16:12 ` Thomas Gleixner
2011-04-11 21:40 ` Marcel Holtmann
2011-04-11 22:16 ` Thomas Gleixner
2011-04-11 22:19 ` Thomas Gleixner
2011-04-11 22:25 ` Gustavo F. Padovan
2011-04-12 18:09 ` Gustavo F. Padovan
2011-04-12 18:09 ` Gustavo F. Padovan
2011-04-12 18:28 ` Thomas Gleixner
2011-04-11 16:34 ` Alan Cox
2011-04-11 16:59 ` Vinicius Gomes
2011-04-21 21:50 ` Keith Packard
2011-04-21 22:59 ` Gustavo F. Padovan
2011-04-22 0:04 ` Keith Packard
2011-04-23 16:37 ` Gustavo F. Padovan
2011-05-03 7:27 ` Stefan Seyfried
2011-05-03 14:48 ` Keith Packard
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=yunaag0tjzb.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.