From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106901] Brightness / WIFI Key does not generate any events
Date: Fri, 15 Jan 2016 13:14:45 +0000 [thread overview]
Message-ID: <bug-106901-2300-qROzVBp2uw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106901-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106901
--- Comment #27 from Roman Gruber <roman.gruber@gmx.at> ---
Linux ASUS-G75VW 4.4.0-gentoo_14-01-2016 #1 SMP Thu Jan 14 19:15:47 CET 2016
x86_64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz GenuineIntel GNU/Linux
same behaviour
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-15 13:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106901-2300@https.bugzilla.kernel.org/>
2015-11-05 6:46 ` [Bug 106901] Brightness / WIFI Key does not generate any events bugzilla-daemon
2015-11-20 11:18 ` bugzilla-daemon
2015-11-20 11:19 ` bugzilla-daemon
2015-11-20 11:20 ` bugzilla-daemon
2015-12-13 18:27 ` bugzilla-daemon
2015-12-13 18:27 ` bugzilla-daemon
2015-12-13 18:37 ` bugzilla-daemon
2015-12-13 18:55 ` bugzilla-daemon
2015-12-17 16:02 ` bugzilla-daemon
2015-12-17 16:04 ` bugzilla-daemon
2015-12-17 16:06 ` bugzilla-daemon
2015-12-17 16:07 ` bugzilla-daemon
2015-12-17 16:08 ` bugzilla-daemon
2015-12-17 16:11 ` bugzilla-daemon
2016-01-15 13:13 ` bugzilla-daemon
2016-01-15 13:14 ` bugzilla-daemon
2016-01-15 13:14 ` bugzilla-daemon [this message]
2016-01-15 13:15 ` bugzilla-daemon
2016-03-09 13:05 ` bugzilla-daemon
2016-03-09 13:05 ` bugzilla-daemon
2016-03-21 10:44 ` bugzilla-daemon
2016-03-21 10:45 ` bugzilla-daemon
2016-03-21 10:45 ` bugzilla-daemon
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=bug-106901-2300-qROzVBp2uw@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.