linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Aaron Lu <aaron.lwe@gmail.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <lenb@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [REGRESSION/PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A
Date: Thu, 1 Aug 2013 13:11:31 -0500	[thread overview]
Message-ID: <CAMP44s2OOX8=tumzwiK3_PRJCxfLfDECrz3dPbzNPiUOuYT8TA@mail.gmail.com> (raw)
In-Reply-To: <20130801180144.GA20520@srcf.ucam.org>

On Thu, Aug 1, 2013 at 1:01 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Thu, Aug 01, 2013 at 12:50:18PM -0500, Felipe Contreras wrote:
>> On Thu, Aug 1, 2013 at 12:42 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>> > An interface that describes reality is better than one that doesn't. But
>> > hey, feel free to disagree and post a patch for the ABI docs.
>>
>> An interface that is useful to the user is better than one that is not.
>
> The interface is useful.

Not 100% useful.

If you are going to claim that 99% true is not true, then useful but
inconsistent is not useful.

I think it is useful, and I think it can be consistent if we want it to.

> There are plenty of machines out there that
> disable the backlight at minimum brightness setting (see every Apple,
> for example), and assuming otherwise has always been incorrect. But,
> like I said, send the patch.

The key word in "every Apple" is *every*; what level 0 does in every
apple is consistent. If 0 should turn off the screen, it should do so
on all Linux machines.

I will investigate and prepare an update to the documentation and the
quirks to do so.

-- 
Felipe Contreras

  reply	other threads:[~2013-08-01 18:11 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 19:20 [REGRESSION/PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A Felipe Contreras
2013-07-29 20:17 ` Rafael J. Wysocki
2013-07-29 20:22   ` Felipe Contreras
2013-07-29 20:47     ` Rafael J. Wysocki
2013-07-29 21:04       ` Felipe Contreras
2013-07-30  3:11 ` Aaron Lu
2013-07-30  3:44   ` Felipe Contreras
2013-07-30  5:51     ` Aaron Lu
2013-07-30  5:57       ` Aaron Lu
2013-07-30 13:42         ` Rafael J. Wysocki
2013-07-30 20:59           ` Felipe Contreras
2013-07-30 23:13             ` Rafael J. Wysocki
2013-07-31  0:11               ` Felipe Contreras
2013-07-31  1:36                 ` Aaron Lu
2013-07-31  2:07                   ` Felipe Contreras
2013-07-31  2:22                     ` Aaron Lu
2013-08-01 18:50                       ` Felipe Contreras
2013-07-31  5:14                 ` Matthew Garrett
2013-07-31 11:32                   ` Felipe Contreras
2013-07-31 14:00                     ` Matthew Garrett
2013-07-31 17:46                       ` Felipe Contreras
2013-07-31 17:52                         ` Matthew Garrett
2013-07-31 18:07                           ` Felipe Contreras
2013-07-31 18:47                             ` Matthew Garrett
2013-08-01 17:37                               ` Felipe Contreras
2013-08-01 17:42                                 ` Matthew Garrett
2013-08-01 17:50                                   ` Felipe Contreras
2013-08-01 18:01                                     ` Matthew Garrett
2013-08-01 18:11                                       ` Felipe Contreras [this message]
2013-08-01 23:40                 ` Felipe Contreras
2013-07-31  1:59             ` Aaron Lu
2013-07-31  2:09               ` Felipe Contreras
  -- strict thread matches above, loose matches on Subject: below --
2013-10-20 22:16 Vincent Blut
2013-10-21  1:53 ` Aaron Lu
2013-10-21 21:21   ` Vincent Blut
2013-10-22  2:16     ` Aaron Lu
2013-10-22  2:12 ` Felipe Contreras
2013-10-23 15:31   ` Matthew Garrett
2013-10-23 19:39     ` Felipe Contreras
2013-10-24  0:53       ` 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='CAMP44s2OOX8=tumzwiK3_PRJCxfLfDECrz3dPbzNPiUOuYT8TA@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=aaron.lwe@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).