From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] 4.10-rc2 oops in DRM connector code
Date: Wed, 11 Jan 2017 16:39:35 +0100 [thread overview]
Message-ID: <CAKMK7uGg7ZqyY8qDkTa9zCeBmOM42+_J71kxAT_KZjyLCdHNKQ@mail.gmail.com> (raw)
In-Reply-To: <c14a88a1-ecc1-5727-5e74-6e9bf4fdc3ca@intel.com>
On Wed, Jan 11, 2017 at 4:24 PM, Dave Hansen <dave.hansen@intel.com> wrote:
> On 01/10/2017 11:43 PM, Daniel Vetter wrote:
>> On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote:
>>> On 01/10/2017 02:31 AM, Daniel Vetter wrote:
>>>> commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e
>>>> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
>>>> Date: Sun Dec 18 14:35:45 2016 +0100
>>>>
>>>> drm: prevent double-(un)registration for connectors
>>>>
>>>> Lack of that would perfectly explain that oops ... Otherwise still no idea
>>>> what's going wrong.
>>> No... That's not in mainline as far as I can see. Should I test with
>>> it applied?
>> Hm, I guess failed to cc: stable that one properly, iirc we decided the
>> race fix is too academic and can't be hit in reality ;-)
>>
>> Testing would be great. Probably conflicts because we extracted
>> drm_connector.c only recently, but running s/drm_connector\.c/drm_crtc.c/
>> over the diff and then applying with some fudge should take care of that.
>
> It doesn't apply to mainline, with or without the substitution you suggest.
>
> Do you want that commit itself tested from -next?
Hm, just cherry-picked it on top of Linus' latest 4.10 git, applies
cleanly there. The substituation was for 4.9. I can send you the patch
here, but seems all fine from what I can tell ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2017-01-11 15:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:03 4.10-rc2 oops in DRM connector code Dave Hansen
2017-01-09 10:15 ` [Intel-gfx] " Daniel Vetter
2017-01-09 12:59 ` Dave Hansen
2017-01-09 13:40 ` Dave Hansen
2017-01-09 13:46 ` Dave Hansen
2017-01-09 16:41 ` Daniel Vetter
2017-01-09 16:50 ` Dave Hansen
2017-01-09 16:59 ` Daniel Vetter
2017-01-09 17:22 ` Dave Hansen
2017-01-09 19:34 ` Alex Deucher
2017-01-09 17:42 ` Dave Hansen
2017-01-10 10:31 ` Daniel Vetter
2017-01-10 16:52 ` Dave Hansen
2017-01-11 7:43 ` Daniel Vetter
2017-01-11 15:24 ` Dave Hansen
2017-01-11 15:39 ` Daniel Vetter [this message]
2017-01-11 16:16 ` Dave Hansen
2017-01-11 22:25 ` Daniel Vetter
2017-01-11 15:40 ` Chris Wilson
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=CAKMK7uGg7ZqyY8qDkTa9zCeBmOM42+_J71kxAT_KZjyLCdHNKQ@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dave.hansen@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.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 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).