From: Tony Lindgren <tony@atomide.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: linux-omap@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm_kms_helper cycle detected build error in next
Date: Mon, 16 Oct 2017 07:35:24 -0700 [thread overview]
Message-ID: <20171016143523.GW4394@atomide.com> (raw)
In-Reply-To: <20171016091649.zm5mlsa64qmf6n7k@phenom.ffwll.local>
* Daniel Vetter <daniel@ffwll.ch> [171016 02:18]:
> On Mon, Oct 16, 2017 at 05:15:50PM +1000, Dave Airlie wrote:
> > On 16 October 2017 at 16:53, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > >
> > > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> > >
> > > On 13/10/17 18:09, Tony Lindgren wrote:
> > >
> > >>> Looks like today's next build fails if omapdrm is enabled as modules
> > >>> with:
> > >>>
> > >>> depmod: ERROR: Cycle detected: drm_kms_helper -> drm -> drm_kms_helper
> > >>> depmod: ERROR: Found 2 modules in dependency cycles!
> > >>> make: *** [Makefile:1261: _modinst_post] Error 1
> > >>
> > >> Making CONFIG_DRM=y and CONFIG_DRM_KMS_HELPER=y instead of
> > >> lodable modules makes it build.
> > >
> > > The same happens even after disabling omapdrm, so it's somewhere in the
> > > common code.
> > >
> > > Interestingly, my depmod crashes when encountering this.
> >
> > There is a fix for this in drm-misc, I should probably pull it over.
> >
> > If I haven't been sent a pull tomorrow, I'll grab it.
>
> You're too much ahead for a pull request on your Monday, but you'll get it
> asap :-)
Meanwhile, can you guys provide few more clues which patch to pick
for the rest of us?
Something like patch subject line, commit id in drm-misc or something
along those lines would be nice..
Regards,
Tony
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-16 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171013145818.GG4394@atomide.com>
2017-10-13 15:09 ` drm_kms_helper cycle detected build error in next Tony Lindgren
2017-10-16 6:53 ` Tomi Valkeinen
2017-10-16 7:15 ` Dave Airlie
2017-10-16 9:16 ` Daniel Vetter
2017-10-16 14:35 ` Tony Lindgren [this message]
2017-10-17 12:07 ` Daniel Vetter
2017-10-17 14:22 ` Tony Lindgren
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=20171016143523.GW4394@atomide.com \
--to=tony@atomide.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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.