From: Mike Lothian <mike@fireburn.co.uk>
To: "Michel Dänzer" <michel@daenzer.net>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] [RFC] drm: Nerf DRM_CONTROL nodes
Date: Tue, 06 Dec 2016 01:55:21 +0000 [thread overview]
Message-ID: <CAHbf0-HR1j8zg0CQrYPq9ehM2yXW8yAQLTG65mZz7dcVJAXM4w@mail.gmail.com> (raw)
In-Reply-To: <9782ad88-a0ef-1a6c-02d4-80dfd8fbc8c2@daenzer.net>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
Thank you!
On Tue, 6 Dec 2016 at 01:47 Michel Dänzer <michel@daenzer.net> wrote:
> On 06/12/16 10:42 AM, Mike Lothian wrote:
> > Hi
> >
> > This patch (in drm-next and drm-intel-nightly) stops my system from
> > booting, I don't see any errors, just a black screen and a reboot after
> > the kernel has been selected
> >
> > I have confirmed that reverting this patch gets those two branches
> > working again
> >
> > Sorry to be the bearer of bad news - I'm guessing this is PRIME related
>
> It's not. You can choose between
>
> https://patchwork.freedesktop.org/patch/125754/
>
> or
>
> https://patchwork.freedesktop.org/patch/125644/
>
> for the fix. :)
>
>
> --
> Earthling Michel Dänzer | http://www.amd.com
> Libre software enthusiast | Mesa and X developer
>
[-- Attachment #1.2: Type: text/html, Size: 1998 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-06 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 8:10 [PATCH] [RFC] drm: Nerf DRM_CONTROL nodes Daniel Vetter
2016-11-17 7:42 ` Daniel Vetter
2016-12-06 1:42 ` Mike Lothian
2016-12-06 1:47 ` Michel Dänzer
2016-12-06 1:55 ` Mike Lothian [this message]
2017-02-19 14:54 ` Thomas Hellstrom
2017-02-19 15:21 ` Thomas Hellstrom
2017-02-20 22:22 ` Daniel Vetter
2017-02-21 5:32 ` DRM_CONTROL node breakage (Re: [PATCH] [RFC] drm: Nerf DRM_CONTROL nodes) Thomas Hellstrom
2017-02-21 5:34 ` David Airlie
2017-02-21 10:52 ` Thomas Hellstrom
2017-02-21 11:11 ` [PATCH] [RFC] drm: Nerf DRM_CONTROL nodes Thomas Hellstrom
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=CAHbf0-HR1j8zg0CQrYPq9ehM2yXW8yAQLTG65mZz7dcVJAXM4w@mail.gmail.com \
--to=mike@fireburn.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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;
as well as URLs for NNTP newsgroup(s).