From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199407] Radeon night light/redshift flickers
Date: Mon, 16 Apr 2018 15:09:03 +0000 [thread overview]
Message-ID: <bug-199407-2300-VAGQgRZgk1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199407-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199407
--- Comment #2 from Dan (daniel@consultd.de) ---
Thx a million...
appreciate your support very much!!!!
as a newbie, sorry for the question: How can I know what the next kernel
version with this amended will be?
4.16.2 still has this problem for me?
Thx a million
Dan
On 4/16/2018 3:47 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=199407
>
> Alex Deucher (alexdeucher@gmail.com) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |alexdeucher@gmail.com
>
> --- Comment #1 from Alex Deucher (alexdeucher@gmail.com) ---
> Should be fixed with:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1cb19e8267a57c5174da09e0d52d1477baceccca
>
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-16 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 5:35 [Bug 199407] New: Radeon night light/redshift flickers bugzilla-daemon
2018-04-16 13:47 ` [Bug 199407] " bugzilla-daemon
2018-04-16 15:09 ` bugzilla-daemon [this message]
2018-04-16 15:19 ` bugzilla-daemon
2018-04-16 15:26 ` bugzilla-daemon
2018-04-27 13:59 ` bugzilla-daemon
2018-04-27 14:19 ` bugzilla-daemon
2018-06-06 18:35 ` bugzilla-daemon
2018-06-09 18:35 ` 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-199407-2300-VAGQgRZgk1@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.