From: Michel Alexandre Salim <salimma@fedoraproject.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Marco Chiappero <marco@absence.it>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
platform-driver-x86 <platform-driver-x86@vger.kernel.org>,
Mattia Dongili <malattia@linux.it>
Subject: Re: Need help debugging Sony Vaio VPCY2 backlight control problem
Date: Mon, 04 Jul 2011 13:31:54 +0200 [thread overview]
Message-ID: <4E11A4AA.2090106@fedoraproject.org> (raw)
In-Reply-To: <1309769864.1896.113.camel@rui>
Hi Rui,
They apply cleanly on top of 3.0-rc5, but I'm getting a
warning-treated-as-failure. Which kernel tree am I supposed to be
applying this to -- linus' 3.0-rc5, a post-rc5 commit, drm-intel-fixes
or drm-intel-next?
Thanks -- Michel
CC [M] drivers/gpu/drm/i915/i915_drv.o
CC [M] drivers/gpu/drm/i915/i915_dma.o
CC [M] drivers/gpu/drm/i915/i915_irq.o
drivers/gpu/drm/i915/i915_irq.c: In function ‘ivybridge_irq_handler’:
drivers/gpu/drm/i915/i915_irq.c:505:3: error: implicit declaration of
function ‘intel_opregion_gse_intr’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/gpu/drm/i915/i915_irq.o] Error 1
make[3]: *** [drivers/gpu/drm/i915] Error 2
make[2]: *** [drivers/gpu/drm] Error 2
make[1]: *** [drivers/gpu] Error 2
make: *** [drivers] Error 2
On 07/04/2011 10:57 AM, Zhang Rui wrote:
> Hi, Michael,
>
> please check if the two patches attached help.
>
> thanks,
> rui
>
> On Mon, 2011-07-04 at 16:48 +0800, Michel Alexandre Salim wrote:
>> On 07/04/2011 10:46 AM, Michel Alexandre Salim wrote:
>>> Here are the ectool dumps, before setting any brightness (backlight=0),
>>> after setting it to 5, and after setting it to 3, plus the typescript
>>> log of the commands issued and the sysfs readings.
>>>
>>> I then set brightness back to 0 (ec-after3.txt) -- didn't log the
>>> keyboard interactions because it's the same (value for brightness
>>> concurs with what is set, but actual_brightness is still -1)
>>>
>>> Let me know if you need anything else. Once we can at least pinpoint the
>>> problem to the right subsystem, I'll add these attachments to the
>>> correct bug report.
>>>
>>> Thanks,
>>>
>> And here's the last dump file, forgot to attach it earlier.
>>
>> Thanks,
>>
--
Michel Alexandre Salim
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
next prev parent reply other threads:[~2011-07-04 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 19:34 Need help debugging Sony Vaio VPCY2 backlight control problem Michel Alexandre Salim
2011-07-01 22:12 ` Marco Chiappero
2011-07-04 8:46 ` Michel Alexandre Salim
2011-07-04 8:48 ` Michel Alexandre Salim
2011-07-04 8:57 ` Zhang Rui
2011-07-04 11:31 ` Michel Alexandre Salim [this message]
2011-07-04 13:34 ` Michel Alexandre Salim
2011-07-13 12:51 ` Michel Alexandre Salim
2011-07-04 10:58 ` Marco Chiappero
2011-07-04 19:00 ` Michel Alexandre Salim
2011-07-04 19:51 ` Marco Chiappero
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=4E11A4AA.2090106@fedoraproject.org \
--to=salimma@fedoraproject.org \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
--cc=marco@absence.it \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rui.zhang@intel.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