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: Tue, 17 Oct 2017 07:22:03 -0700 [thread overview]
Message-ID: <20171017142203.GZ4394@atomide.com> (raw)
In-Reply-To: <20171017120753.is5attwq3p7mfsst@phenom.ffwll.local>
* Daniel Vetter <daniel@ffwll.ch> [171017 05:09]:
> On Mon, Oct 16, 2017 at 07:35:24AM -0700, Tony Lindgren wrote:
> >
> > 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..
>
> I guess linux-next still not yet back to the daily update schedule, that's
> why you need this? It's been in trees since last week, and now also in
> drm-next ... Usually no one ever cares about the commit if we fix it right
> away.
>
> Anyway
>
> commit 512721a14a2a94b48ca0863d48f9829922a816b8
> Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Date: Fri Oct 13 16:08:53 2017 +0200
>
> drm/drm_of: Move drm_of_panel_bridge_remove_function into header.
OK thanks looks like Linux next is building for me again now.
Regards,
Tony
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-10-17 14:22 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
2017-10-17 12:07 ` Daniel Vetter
2017-10-17 14:22 ` Tony Lindgren [this message]
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=20171017142203.GZ4394@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.