Linux ACPI
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Len Brown <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi: Don't send KEY_UNKNOWN for random video notifications
Date: Fri, 02 Apr 2010 09:05:40 +0800	[thread overview]
Message-ID: <1270170340.24064.4503.camel@rzhang1-desktop> (raw)
In-Reply-To: <20100401123227.GA4312@srcf.ucam.org>

On Thu, 2010-04-01 at 20:32 +0800, Matthew Garrett wrote:
> On Thu, Apr 01, 2010 at 02:57:53PM +0800, Zhang Rui wrote:
> 
> > can you attach the acpidump of your laptop please?
> 
> Afraid not - it's prototype hardware.
> 
that's okay. The patch looks good.
I just want to see why notification 0xD1 is sent out.

Acked-by: Zhang Rui <rui.zhang@intel.com>

thanks,
rui



      reply	other threads:[~2010-04-02  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 22:40 [PATCH] acpi: Don't send KEY_UNKNOWN for random video notifications Matthew Garrett
2010-04-01  0:57 ` Len Brown
2010-04-01  6:57   ` Zhang Rui
2010-04-01 12:32     ` Matthew Garrett
2010-04-02  1:05       ` Zhang Rui [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=1270170340.24064.4503.camel@rzhang1-desktop \
    --to=rui.zhang@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    /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