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;
From:   "Namjae Jeon" <namjae.jeon@samsung.com>
To:     =?iso-8859-1?Q?'Pali_Roh=E1r'?= <pali@kernel.org>,
        "'Stephen Rothwell'" <sfr@canb.auug.org.au>,
        "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc:     "'Al Viro'" <viro@ZenIV.linux.org.uk>,
        "'Linux Next Mailing List'" <linux-next@vger.kernel.org>,
        "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
        "'Sungjong Seo'" <sj1557.seo@samsung.com>,
        "'Christoph Hellwig'" <hch@lst.de>
In-Reply-To: <20200309231739.2w45cleifsmwbfd6@pali>
Subject: RE: linux-next: build warning after merge of the vfs tree
Date:   Tue, 10 Mar 2020 08:36:04 +0900
Message-ID: <003501d5f66b$7fe3b260$7fab1720$@samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Language: ko
Thread-Index: AQLhnT+ZUEFtORUKwX4A79zpVs4A5gKBNZQWAseM+v6l/1Lw8A==
CMS-TYPE: 101P
DLP-Filter: Pass
References: <20200310095918.3ea6432f@canb.auug.org.au>
        <CGME20200309231744epcas1p3c0c6f455449fbcbb67df2fdcbe7ba351@epcas1p3.samsung.com>
        <20200309231739.2w45cleifsmwbfd6@pali>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

> On Tuesday 10 March 2020 09:59:18 Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the vfs tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > warning: same module names found:
> >   fs/exfat/exfat.ko
> >   drivers/staging/exfat/exfat.ko
> >
> > Introduced by commit
> >
> >   b9d1e2e6265f ("exfat: add Kconfig and Makefile")
> >
> > and not fixed by commit
> >
> >   1a3c0509ce83 ("staging: exfat: make staging/exfat and fs/exfat
> > mutually exclusive")
> 
> Hello Stephen!
> 
> exfat.ko from fs/exfat subdirectory is a rewrite/cleanup of staging exfat
> driver. It means that fs/exfat replaces staging/exfat and so after
> fs/exfat is merged, the old staging/exfat code is not needed anymore.
> 
> Therefore I think that instead of hacking Kconfig/Makefile files to define
> mutually exclusivity, it is better to remove staging/exfat code.
> 
> Removal of old staging code should be easy and should fix this problem.
Agree.
Greg, You told me to let me know when fs/exfat gets accepted. Now it's time
to drop staging/exfat.

Thanks!
> 
> Any objections? Or other ideas?