Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp870306ybl; Fri, 16 Aug 2019 05:26:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwaryCWGdCpy+FdnKLmwb5z0xlZuLgU5FO5YP8Gjxd+xqGzXrKY+Bqg/pIiKa26hS8557pF X-Received: by 2002:a17:902:4ac2:: with SMTP id q2mr6680447plh.81.1565958399548; Fri, 16 Aug 2019 05:26:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565958399; cv=none; d=google.com; s=arc-20160816; b=iWlp+LVXeXplUPILQ/4iCtGyEHl+ezFEgIWd3qB/LQr5+/6lR0mMNXWjnXsRqx7l/s gE14Hfk3UcFgV3ssJstowCjhRWUCuO6e58tARMk+VqwilQNWvOwf02yyt24XGFXUERfm ghb1HMdT1Rv1mM8iQr81Ax4sXCEoYJ0GjAmAYYt0txR/o78ogHA/mG8yloqM7V5lqe22 PKyuhK5dksa8iF3LtXQnNpP6qi2meIQfinKRHEEpJfThmTs+xFbN2V6FVOUfD+wMnIve GIXmL09De2qn2teTAInIm6lD9onNP/U0Mqa4966DgsOV/GifIOYjrMt2sPA+ldUCkZEY oyNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=NVjxI9wQsgo7bIQV1WIOD/umfMs9jNvHwICNpI3e4Ik=; b=bzWpTELq9zvmh0K1A2hnUkQh1YkkEJ0pCDsne4QSz1VwgmezwwnCAmN+pQyZN3kT3q fNQu42KXEeGijl09JcrPkkLhBfCrQT+hhaMxJLblVfELeZS8NC2/sHgcrEhcsL/7E8lG 9aX3CbJjEjsEn68oJ6J28SvuqP9/UK80J+IiqXZAVRf/SbChAxbu7XszFS14+uw6WK+n DKY/FWpN8/c4sni2FtvYaJVWlQv6mcgrPQm/XTpUdeaGJJltixc4bqxzo92OwhRUK9X4 k5fy6z9ABGXpy1HGLM8/9uozY/nNLSiuIfbh200IE4YC4ClrhWdpmMF3aZwH9tvgeWw9 j7qw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=NkbxcG36; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q15si3745056pgt.150.2019.08.16.05.26.21; Fri, 16 Aug 2019 05:26:39 -0700 (PDT) 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; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=NkbxcG36; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727169AbfHPMYS (ORCPT + 99 others); Fri, 16 Aug 2019 08:24:18 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:38462 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727007AbfHPMYS (ORCPT ); Fri, 16 Aug 2019 08:24:18 -0400 Received: from pendragon.ideasonboard.com (dfj612yhrgyx302h3jwwy-3.rev.dnainternet.fi [IPv6:2001:14ba:21f5:5b00:ce28:277f:58d7:3ca4]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 5AE142AF; Fri, 16 Aug 2019 14:24:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1565958255; bh=Xvsx+Qa2ZOQg4OjurY0P2Q8XnZceB+vL/gqEMZuluQI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NkbxcG36hw0krUs5uFpSKH+UI86xtGWx65rlhdgnABM+nCetNG9shKvQ/aL5H1Nwd BNd0gNUFcLwQQpiyPh2gxFhTsgU72SsW1sXqGj2nf6OeQryHfllS2GMWrqcSZk+DeF R/TqDRz1zxwY0FxfVdgKS67Ogv92j+mF0Fnh+Q7A= Date: Fri, 16 Aug 2019 15:24:11 +0300 From: Laurent Pinchart To: Daniel Vetter Cc: Sam Ravnborg , Stephen Rothwell , Intel Graphics , DRI , Linux Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build warning after merge of the drm-misc tree Message-ID: <20190816122411.GE5020@pendragon.ideasonboard.com> References: <20190816133132.6b37d7fa@canb.auug.org.au> <20190816044846.GA27781@ravnborg.org> <20190816094715.GB5020@pendragon.ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190816094715.GB5020@pendragon.ideasonboard.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 16, 2019 at 12:47:15PM +0300, Laurent Pinchart wrote: > On Fri, Aug 16, 2019 at 08:23:54AM +0200, Daniel Vetter wrote: > > On Fri, Aug 16, 2019 at 6:48 AM Sam Ravnborg 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. > > Oops :-( > > The new drivers were initially part of a patch series that removed the > duplicated drivers. The new drivers then got fast-tracked, and I didn't > notice this issue. > > > 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. > > Note that drivers/video/fbdev/omap2/omapfb/ will stay, it's > drivers/gpu/drm/omapdrm/displays/ that is being removed. FB_OMAP2 > already depends on DRM_OMAP = n, I propose doing something similar at > the level of the individual display drivers. I've just posted "[PATCH 0/2] Fix module name clash with omapdrm and DRM panel modules" that should solve this issue. -- Regards, Laurent Pinchart