From: Valdis.Kletnieks@vt.edu
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Aaron Lu <aaron.lu@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: linux-next 20160512 - ACPI issue with screen brightness
Date: Thu, 19 May 2016 23:05:00 -0400 [thread overview]
Message-ID: <7208.1463713500@turing-police.cc.vt.edu> (raw)
In-Reply-To: <6459.1463698397@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Thu, 19 May 2016 18:53:17 -0400, Valdis.Kletnieks@vt.edu said:
> > > next-20160512 sets the screen brightness to about 40%-ish or so, rather
> > > than the 100% intensity I want.
> Put this one in the "things that go bump in the night" pile - the problem
> doesn't manifest on next-20160519, even though the commit I bisected to
> is in the tree for today, and I don't see any obvious smoking guns to
> have fixed it in the past week's worth of 'git log'....
Actually, put it in "things that go bump in the night but need a stake driven
through them"- it looks like I booted the wrong kernel while testing, and in
fact next-20160519 *is* still broken. However, after:
git revert -n e4f35c1339f0cfcf38d3f63dd6fea2b070399263
git revert -n 059500940defe285222d3b189b366dfe7f299cae
Things work again.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2016-05-20 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:41 linux-next 20160512 - ACPI issue with screen brightness Valdis Kletnieks
2016-05-17 20:50 ` Rafael J. Wysocki
2016-05-19 22:53 ` Valdis.Kletnieks
2016-05-20 3:05 ` Valdis.Kletnieks [this message]
2016-05-20 5:45 ` Aaron Lu
2016-05-20 7:02 ` Valdis.Kletnieks
2016-05-20 7:17 ` Aaron Lu
2016-05-20 7:35 ` Aaron Lu
2016-05-21 0:15 ` Valdis.Kletnieks
2016-05-21 3:29 ` Aaron Lu
2016-05-21 7:55 ` [PATCH] ACPI / Thermal / video: fix max_level incorrect value Aaron Lu
2016-05-25 5:15 ` Aaron Lu
2016-05-26 1:49 ` Valdis.Kletnieks
2016-05-26 5:15 ` Aaron Lu
2016-05-27 0:42 ` Zhang, Rui
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=7208.1463713500@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=aaron.lu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.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