From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mario_Limonciello@dell.com
Cc: matthew.garrett@coreos.com, linux@dominikbrodowski.net,
linux-acpi@vger.kernel.org, broonie@kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/4] acpi: allow for an override to set _REV
Date: Sat, 23 May 2015 00:15:54 +0200 [thread overview]
Message-ID: <23116293.JAxziy2cCE@vostro.rjw.lan> (raw)
In-Reply-To: <DB6E482E89290547898851B8CC9D8110016A5EBC17@AUSX7MCPS302.AMER.DELL.COM>
On Friday, May 22, 2015 04:19:05 PM Mario_Limonciello@Dell.com wrote:
> > OK, so do we have any proof that anything in addition to the sound thing is broken by returning 2 from _REV?
> >
> > If not, then we're probably spending too much time discussing this.
>
> From a Dell perspective I'm not aware of anything else breaking, but I'll be sure to raise its attention and any associated details if I become privy to them. I'm working with architecture to ensure that future products are not relying on _REV values as well.
> I know Matthew had mentioned that another OEM's product was using this as well, but I don't know what for.
OK, here's a deal.
I'll wait for the next few days for someone to tell me if there's any
known system in addition to the XPS 13 (2015) which breaks as a result
of the change to return 2 from _REV. If none are reported before the
next Friday, I'll just apply the patch I posted some time ago. If any
reports come in later, we'll still be able to rearrange things during
the 4.2 cycle or even later.
If *something* is reported next week, I'll reconsider the approach depending
on what that thing is.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-05-22 21:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 13:31 [PATCH 0/4] ACPI: provide an override for _REV Dominik Brodowski
2015-05-14 13:31 ` [PATCH 1/4] acpi: use same type for acpi_predefined_names values as in definition Dominik Brodowski
2015-05-14 13:31 ` [PATCH 2/4] acpi: allow for an override to set _REV Dominik Brodowski
2015-05-14 14:18 ` Dominik Brodowski
2015-05-14 20:36 ` Rafael J. Wysocki
2015-05-14 21:55 ` Rafael J. Wysocki
2015-05-17 17:41 ` Dominik Brodowski
2015-05-18 1:01 ` Rafael J. Wysocki
2015-05-18 4:47 ` Dominik Brodowski
2015-05-21 1:24 ` Rafael J. Wysocki
2015-05-21 10:24 ` Dominik Brodowski
2015-05-22 1:11 ` Rafael J. Wysocki
2015-05-21 18:10 ` Matthew Garrett
2015-05-21 18:18 ` Mario Limonciello
2015-05-22 1:13 ` Rafael J. Wysocki
2015-05-22 21:19 ` Mario_Limonciello
2015-05-22 22:15 ` Rafael J. Wysocki [this message]
2015-06-30 20:11 ` Rafael J. Wysocki
2015-05-22 1:02 ` Rafael J. Wysocki
2015-05-14 13:31 ` [PATCH 3/4] acpi: add _REV quirk for Dell XPS 13 (2015) Dominik Brodowski
2015-05-14 13:31 ` [PATCH 4/4] acpi: fix kernel-parameters ordering in Documentation Dominik Brodowski
2015-05-14 20:31 ` [PATCH 0/4] ACPI: provide an override for _REV Rafael J. Wysocki
2015-05-14 23:56 ` Rafael J. Wysocki
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=23116293.JAxziy2cCE@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Mario_Limonciello@dell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=matthew.garrett@coreos.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