From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 92765] Linux 4.1.12+, 4.2.5+ -> drm:radeon_pm_late_init [radeon]] *ERROR* + WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() +
Date: Mon, 2 Nov 2015 10:09:11 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.11.02.10.09.11@googlemail.com> (raw)
In-Reply-To: bug-92765-502-gxulWXJ539@http.bugs.freedesktop.org/
On Mon, 02 Nov 2015 05:39:20 +0000, bugzilla-daemon wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=92765
>
> Alex Deucher <alexdeucher@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Component|Drivers/Gallium/radeonsi |DRM/Radeon
> Version|11.0 |unspecified
> Resolution|--- |FIXED
> Product|Mesa |DRI
> QA Contact|dri-devel@lists.freedesktop |
> |.org |
>
> --- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
> Fixed in:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=49abb26651167c892393cd9f2ad23df429645ed9
Alex, I don't know why there are two different bugzillas for this, but
please take a look at https://bugzilla.kernel.org/show_bug.cgi?id=106851
because the issue does not seem to be fixed by that patch at all.
-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-02 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 16:37 [Bug 92765] Linux 4.1.12+, 4.2.5+ -> drm:radeon_pm_late_init [radeon]] *ERROR* + WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() + bugzilla-daemon
2015-11-02 5:39 ` bugzilla-daemon
2015-11-02 10:09 ` Holger Hoffstätte [this message]
2015-11-02 15:11 ` Alex Deucher
2015-11-02 15:28 ` Holger Hoffstätte
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=pan.2015.11.02.10.09.11@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--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.