mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lv Zheng <lv.zheng@intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Len Brown <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ACPI/EC: Fix regressions on Samsung hardware.
Date: Wed, 29 Oct 2014 17:14:29 +0100	[thread overview]
Message-ID: <3707792.PHiIGtcpHx@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1414553399.git.lv.zheng@intel.com>

On Wednesday, October 29, 2014 11:33:33 AM Lv Zheng wrote:
> It is reported that the Samsung EC firmware behaves differently than Acer
> EC firmware. And then previous 2 commits that fix Acer issues have broken
> Samsung hardware.
> 
> This patchset fixes the regressions.
> 
> Lv Zheng (2):
>   Revert "ACPI / EC: Add support to disallow QR_EC to be issued before
>     completing previous QR_EC"
>   ACPI/EC: Fix a regression caused by conflict firmware behavior
>     between Samsung and Acer.

Both patches applied, thanks Lv!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      parent reply	other threads:[~2014-10-29 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26 12:16 ACPI regression: New Acer workarounds break Samsung NP900X Ortwin Glück
2014-10-27  3:08 ` Zheng, Lv
2014-10-29  3:33 ` [PATCH v2 0/2] ACPI/EC: Fix regressions on Samsung hardware Lv Zheng
2014-10-29  3:33   ` [PATCH v2 1/2] Revert "ACPI / EC: Add support to disallow QR_EC to be issued before completing previous QR_EC" Lv Zheng
2014-10-29  3:33   ` [PATCH v2 2/2] ACPI/EC: Fix a regression caused by conflict firmware behavior between Samsung and Acer Lv Zheng
2014-10-29 16:14   ` Rafael J. Wysocki [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=3707792.PHiIGtcpHx@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=zetalog@gmail.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®