From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Michal Marek <michal.lkml@markovi.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: make module name conflict fatal error
Date: Tue, 9 Jun 2020 08:20:12 +0200 [thread overview]
Message-ID: <20200609062012.GA499862@kroah.com> (raw)
In-Reply-To: <20200608020256.GA256950@roeck-us.net>
On Sun, Jun 07, 2020 at 07:02:56PM -0700, Guenter Roeck wrote:
> Hi,
>
> On Mon, May 11, 2020 at 01:21:49PM +0900, Masahiro Yamada wrote:
> > I think all the warnings have been fixed by now. Make it a fatal error.
> >
>
> Not entirely. With this patch in the tree, I get:
>
> Building sparc64:allmodconfig ... failed
> --------------
> Error log:
> error: the following would cause module name conflict:
> drivers/char/adi.ko
> drivers/input/joystick/adi.ko
> make[1]: *** [modules_check] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [__sub-make] Error 2
>
> Reverting this patch fixes the problem.
As it doesn't look like either of these drivers can be "auto-loaded"
based on hardware detection, I don't know what to suggest as for
renaming either of them.
Any ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2020-06-09 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 4:21 [PATCH] kbuild: make module name conflict fatal error Masahiro Yamada
2020-06-08 2:02 ` Guenter Roeck
2020-06-09 6:20 ` Greg Kroah-Hartman [this message]
2020-06-09 7:51 ` Arnd Bergmann
2020-06-09 7:58 ` Greg Kroah-Hartman
2020-06-09 8:42 ` Masahiro Yamada
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=20200609062012.GA499862@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lucas.demarchi@intel.com \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=sfr@canb.auug.org.au \
/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.