public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jerone.young@canonical.com>
To: Len Brown <lenb@kernel.org>
Cc: Andrew Lutomirski <luto@mit.edu>,
	linux-thinkpad@linux-thinkpad.org,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] Set osi=Linux for the ThinkPad X200s
Date: Wed, 25 Nov 2009 13:56:45 -0600	[thread overview]
Message-ID: <1259179005.2471.4.camel@laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.0911251317480.3950@localhost.localdomain>

On Wed, 2009-11-25 at 13:24 -0500, Len Brown wrote:
> On Wed, 25 Nov 2009, Jerone Young wrote:
> 
> > I had a set of patches for the different thinkpad lines could test.
> > Couldn't verify though with Thinkpads like the T400s needed this.
> > 
> > Here are direct links from the archive:
> > 
> > https://lists.ubuntu.com/archives/kernel-team/2009-August/007065.html
> > https://lists.ubuntu.com/archives/kernel-team/2009-August/007068.html
> > https://lists.ubuntu.com/archives/kernel-team/2009-August/007064.html
> > https://lists.ubuntu.com/archives/kernel-team/2009-August/007066.html
> > https://lists.ubuntu.com/archives/kernel-team/2009-August/007067.html
> 
> 
> Have these been verified as necessary to make sound work on
> the specified models, or are these speculative patches?

Yes they have all been verified for the mute key to work. Actually I
missed the 0 patch that expalins everythig here:

https://lists.ubuntu.com/archives/kernel-team/2009-August/007080.html

Can find some of the verification in this LP bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/281732


> 
> I'd rather apply only patches that are verified as necessary upstream.
> 
> Also, I don't know how to apply html without editing -- so if
> you can extract the patches from your tree and e-mail them
> as plain text, that would be less tedious.

hmm .. don't have a tree anymore. Though they where in the ubuntu kernel
tree at one point. Best to just copy and past the diffs from the links.

> 
> thanks,
> -Len Brown, Intel Open Source Technology Center



  reply	other threads:[~2009-11-25 19:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 16:47 [PATCH] Set osi=Linux for the ThinkPad X200s Andrew Lutomirski
2009-11-09 16:54 ` Matthew Garrett
2009-11-09 17:49   ` Andrew Lutomirski
2009-11-09 17:54     ` Matthew Garrett
2009-11-10  9:24       ` [ltp] " Henrique de Moraes Holschuh
2009-11-10 12:42         ` Matthew Garrett
2009-11-10 13:32         ` Andrew Lutomirski
2009-11-10 14:14           ` Matthew Garrett
2009-11-10 17:49           ` Henrique de Moraes Holschuh
2009-11-10  9:19 ` [ltp] " Henrique de Moraes Holschuh
2009-11-25  4:50 ` Len Brown
2009-11-25 17:30   ` Jerone Young
2009-11-25 18:24     ` Len Brown
2009-11-25 19:56       ` Jerone Young [this message]
2009-11-26  5:07       ` Matthew Garrett
2009-11-26  6:00         ` Andrew Lutomirski
2009-11-26 17:02           ` Stefan Monnier
2009-11-26 13:43         ` Jerone Young
2009-11-25 19:01   ` Andrew Lutomirski
2009-11-30  5:47   ` Jerone Young

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=1259179005.2471.4.camel@laptop \
    --to=jerone.young@canonical.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-thinkpad@linux-thinkpad.org \
    --cc=luto@mit.edu \
    /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