mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Surbhi Palande <surbhi.palande@canonical.com>
Cc: dri-devel@lists.sourceforge.net,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Eric Anholt <eric@anholt.net>,
	linux-kernel@vger.kernel.org, airlied@linux.ie,
	yakui.zhao@intel.com, zhenyuw@linux.intel.com,
	Len Brown <lenb@kernel.org>
Subject: Re: ACPI _LID failures
Date: Fri, 19 Mar 2010 12:53:20 -0700	[thread overview]
Message-ID: <20100319125320.22d8b25d@jbarnes-piketon> (raw)
In-Reply-To: <cover.1268680514.git.surbhi.palande@canonical.com>

On Mon, 15 Mar 2010 21:32:41 +0200
Surbhi Palande <surbhi.palande@canonical.com> wrote:

> The following two patches are quirks that blacklist bios which report
> incorrect lid status. These are bioses for machines with a 900 GM.
> The first one is tested by Ubuntu users and the second one isn't.
> Further testing will be appreciated.
> 
> 
> Surbhi Palande (2):
>   drm/i915: blacklist lid status: Sony VGN-BX196VP
>   drm/i915: blacklist lid status: Elite Co. G335
> 
>  drivers/gpu/drm/i915/intel_lvds.c |   14 ++++++++++++++
>  1 files changed, 14 insertions(+), 0 deletions(-)

Patches look ok to me.  Len was curious about whether some recent ACPI
EC fixes will fix some of our lid detection bugs though.

Len, is there any particular patch or version people should try?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  parent reply	other threads:[~2010-03-19 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <89k83ahv05c@azsmga001.ch.intel.com>
2010-03-15 19:32 ` [PATCH 0/2] blacklist lid status: Sony VGN-BX196VP and Elite Co Surbhi Palande
2010-03-15 19:32   ` [PATCH 1/2] drm/i915: blacklist lid status: Sony VGN-BX196VP Surbhi Palande
2010-03-15 19:33   ` [PATCH 2/2] drm/i915: blacklist lid status: Elite Co. G335 Surbhi Palande
2010-03-19 19:53   ` Jesse Barnes [this message]
2010-03-19 20:53     ` ACPI _LID failures Eric Anholt
2010-03-19 21:05       ` Jesse Barnes
2010-03-19 21:12         ` Matthew Garrett

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=20100319125320.22d8b25d@jbarnes-piketon \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=eric@anholt.net \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=surbhi.palande@canonical.com \
    --cc=yakui.zhao@intel.com \
    --cc=zhenyuw@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®