From: Shuah Khan <shuahkhan@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: shuahkhan@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: linux-next: Tree for Jun 27 (eliminated_printk)
Date: Thu, 28 Jun 2012 15:03:50 -0600 [thread overview]
Message-ID: <1340917430.3821.2.camel@lorien2> (raw)
In-Reply-To: <20120628201601.GB12471@srcf.ucam.org>
On Thu, 2012-06-28 at 21:16 +0100, Matthew Garrett wrote:
> On Thu, Jun 28, 2012 at 02:14:19PM -0600, Shuah Khan wrote:
>
> > Has this bean fixed in June 28th tree??
>
> I dropped the patches from my -next branch. I'll wait to hear that the
> pre-requisites have gone in - alternatively, Joe, feel free to add my
> SoB and have them pushed through whichever tree takes the first in the
> series.
>
ok Worked around for now by enabling CONFIG_THINKPAD_ACPI_DEBUG and
CONFIG_FUJITSU_LAPTOP_DEBUG. Just in case others need a work around.
-- Shuah
prev parent reply other threads:[~2012-06-28 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 3:22 linux-next: Tree for Jun 27 Stephen Rothwell
2012-06-27 16:09 ` linux-next: Tree for Jun 27 (vfio) Randy Dunlap
2012-06-27 19:20 ` Alex Williamson
2012-06-27 16:13 ` linux-next: Tree for Jun 27 (dm-thin.c) Randy Dunlap
2012-06-27 16:18 ` Alasdair G Kergon
2012-06-27 16:25 ` linux-next: Tree for Jun 27 (eliminated_printk) Randy Dunlap
2012-06-27 16:29 ` Joe Perches
2012-06-27 22:52 ` Stephen Rothwell
2012-06-28 20:14 ` Shuah Khan
2012-06-28 20:16 ` Matthew Garrett
2012-06-28 21:03 ` Shuah Khan [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=1340917430.3821.2.camel@lorien2 \
--to=shuahkhan@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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.