[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210111105654.17e3aa76@canb.auug.org.au>
Date: Mon, 11 Jan 2021 10:56:54 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Vetter <daniel.vetter@...ll.ch>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>
Cc: Dave Airlie <airlied@...ux.ie>,
DRI <dri-devel@...ts.freedesktop.org>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the drm tree
Hi all,
On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > error: the following would cause module name conflict:
> > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko
> > drivers/gpu/drm/panel/panel-dsi-cm.ko
> >
> > Maybe caused by commit
> >
> > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver")
> >
> > I have used the drm tree from next-20210107 for today.
>
> This has affected the drm-misc tree as well (since it merged in the drm
> tree).
>
> I have used the drm-misc tree from next-20210107 for today.
And now the drm-intel tree.
I have used the drm-intel tree from next-20210108 for today.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists