From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Al Stone <ahs3@redhat.com>
Cc: linux-acpi@vger.kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: Adjust the return value of _REV on x86
Date: Mon, 16 Mar 2015 21:01:40 +0000 [thread overview]
Message-ID: <20150316210140.GA4678@srcf.ucam.org> (raw)
In-Reply-To: <55073E50.3010309@redhat.com>
On Mon, Mar 16, 2015 at 02:34:24PM -0600, Al Stone wrote:
> More a philosophical question -- the patch seems fine to me, personally, and
> for arm64, we have to have >= 5 anyway -- but would it make sense to just not
> acknowledge _REV and deprecate it from the kernel and the spec? I'm already
> trying to get rid of _OSI because of such silliness and force requests to _OSC
> where they should be (granted, it will take some time...).
A bunch of systems verify that _REV returns >= 2 and change EC behaviour
based on that, so killing it in the near term is unfortunately probably
not an option.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2015-03-16 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:50 [PATCH] ACPI: Adjust the return value of _REV on x86 Matthew Garrett
2015-03-14 19:58 ` Jason Ekstrand
2015-03-16 23:21 ` Jason Ekstrand
2015-03-23 12:04 ` Matt Fleming
2015-03-24 5:50 ` Mario Limonciello
2015-03-24 9:17 ` Liam Girdwood
2015-03-24 14:41 ` Mario Limonciello
2015-03-24 15:24 ` Matt Fleming
2015-03-24 17:22 ` Mario Limonciello
2015-03-24 18:01 ` Matthew Garrett
2015-03-24 19:53 ` Mario Limonciello
2015-03-24 20:00 ` Matthew Garrett
2015-03-24 20:02 ` Rafael J. Wysocki
2015-03-24 20:21 ` Mario Limonciello
2015-03-26 2:40 ` Yuhong Bao
2015-03-16 20:34 ` Al Stone
2015-03-16 21:01 ` Matthew Garrett [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=20150316210140.GA4678@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ahs3@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.