From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] ACPI and power management fixes for v3.11-rc4
Date: Sat, 3 Aug 2013 15:20:22 -0500 [thread overview]
Message-ID: <CAMP44s2dbNBbKwLd9hGaYVPL_Z6-v_S0xZpmz8cwicg1wgMr+Q@mail.gmail.com> (raw)
In-Reply-To: <1963015.Y2AObmEn2f@vostro.rjw.lan>
On Sat, Aug 3, 2013 at 6:54 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Friday, August 02, 2013 08:48:09 PM Felipe Contreras wrote:
>> Yes, that's fine, either the revert, or the patch I mentioned, or
>> something else, but something has to be done, and it was better to do
>> it in v3.11-rc4 than in v3.11-rc5, because that change itself can
>> cause further problems.
>
> A revert can be done in -rc5 just fine. If we don't have a working fix this
> week, I'll do the revert.
I think you are waiting for miracles. But whatever.
>> Let's do a though experiment, let's say you are right, and they can
>> survive the 6 months it would take you to find the "perfect" solution,
>> say in v3.13. What's wrong with having a partial solution in v3.12? If
>> the blacklisting doesn't work properly (there's absolutely no evidence
>> for that), then you revert it on v3.12.1.
>>
>> What's wrong with that approach?
>
> If the blacklisting leads to problems, they may not be reported in the 3.12
> time frame, but much later. For example because people won't realize that
> the problems are caused by the blacklisting until much much later. And then
> we'll be in a spot where whatever we do will break things for someone.
The key word is *may*, you don't *know*. Why do you insist in
committing this reification fallacy?
This threat is not real, it's theoretical.
But let's suppose you are right, and there are issues, and those don't
get reported in v3.12. That is actually GOOD, if people don't report
issues, it means the issues are not that big, or not even *there*.
And no, we won't be in a spot where whatever we do will break things,
because if the intel backlight driver works correctly, that solution
would work for everyone. And if it doesn't, we should stay with what
works best.
> And we had situations like that in the past, which is the source of my concern.
> You obviously don't have that experience, or you won't be so eager to inflict
> the blacklisting on everyone.
>
> Anyway, as you know, but conveniently don't mention, I asked some experienced
> people for opinions about that. If they agree with you, we will add the
> blacklist. If they don't, we won't add it.
Again, screw the users. We are stuck with broken backlight for several
more months to come. Great.
--
Felipe Contreras
next prev parent reply other threads:[~2013-08-03 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 14:29 [GIT PULL] ACPI and power management fixes for v3.11-rc4 Rafael J. Wysocki
2013-08-02 19:12 ` Felipe Contreras
2013-08-02 21:21 ` Rafael J. Wysocki
2013-08-02 21:31 ` Felipe Contreras
2013-08-02 22:21 ` Rafael J. Wysocki
2013-08-03 1:48 ` Felipe Contreras
2013-08-03 11:54 ` Rafael J. Wysocki
2013-08-03 16:08 ` Igor Gnatenko
2013-08-03 20:21 ` Felipe Contreras
2013-08-03 23:27 ` Igor Gnatenko
2013-08-04 0:27 ` Felipe Contreras
2013-08-03 20:20 ` Felipe Contreras [this message]
2013-08-03 21:59 ` Rafael J. Wysocki
2013-08-03 22:06 ` Felipe Contreras
2013-08-03 22:21 ` Rafael J. Wysocki
2013-08-03 22:33 ` Felipe Contreras
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=CAMP44s2dbNBbKwLd9hGaYVPL_Z6-v_S0xZpmz8cwicg1wgMr+Q@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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).