Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190816133132.6b37d7fa@canb.auug.org.au> <20190816044846.GA27781@ravnborg.org>
In-Reply-To: <20190816044846.GA27781@ravnborg.org>
From:   Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri, 16 Aug 2019 08:23:54 +0200
Message-ID: <CAKMK7uFy2vtOpSNrJyPDp0mvPTEvTD3zw7_gTuWe6gRqj18FFg@mail.gmail.com>
Subject: Re: linux-next: build warning after merge of the drm-misc tree
To:     Sam Ravnborg <sam@ravnborg.org>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Intel Graphics <intel-gfx@lists.freedesktop.org>,
        DRI <dri-devel@lists.freedesktop.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Aug 16, 2019 at 6:48 AM Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Stephen.
>
> On Fri, Aug 16, 2019 at 01:31:32PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the drm-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > warning: same module names found:
> >   drivers/video/fbdev/omap2/omapfb/displays/panel-nec-nl8048hl11.ko
> >   drivers/gpu/drm/panel/panel-nec-nl8048hl11.ko
> > warning: same module names found:
> >   drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.ko
> >   drivers/gpu/drm/panel/panel-sharp-ls037v7dw01.ko
> > warning: same module names found:
> >   drivers/video/fbdev/omap2/omapfb/displays/panel-sony-acx565akm.ko
> >   drivers/gpu/drm/panel/panel-sony-acx565akm.ko
> > warning: same module names found:
> >   drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.ko
> >   drivers/gpu/drm/panel/panel-tpo-td028ttec1.ko
> > warning: same module names found:
> >   drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td043mtea1.ko
> >   drivers/gpu/drm/panel/panel-tpo-td043mtea1.ko
> >
> > Introduced by commits
> >
> >   df439abe6501 ("drm/panel: Add driver for the NEC NL8048HL11 panel")
> >   c9cf4c2a3bd3 ("drm/panel: Add driver for the Sharp LS037V7DW01 panel")
> >   1c8fc3f0c5d2 ("drm/panel: Add driver for the Sony ACX565AKM panel")
> >   415b8dd08711 ("drm/panel: Add driver for the Toppoly TD028TTEC1 panel")
> >   dc2e1e5b2799 ("drm/panel: Add driver for the Toppoly TD043MTEA1 panel")
>
> Ups, had not seen this one coming.
> We are in the process of removing the drivers in drivers/video/fbdev/omap2/omapfb/
> and decided to introduce the new drivers early to get them out of a
> longer patch series.

Should we have a config dependency to not allow the old fbdev omap
when the drm omap driver is enabled? I think that would take care of
all this.

Or too annoying for development?

Also note that fbdev is in drm-misc now, so we should be able to fix
this all without cross-tree conflicts.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch