[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK7LNASTDPG6bDeXj9GfWQVB559D6GEsZiUaiqCfzcPpteZxZw@mail.gmail.com>
Date: Tue, 16 Jul 2019 15:02:30 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jon Mason <jdmason@...zu.us>,
NTB Mailing List <linux-ntb@...glegroups.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the ntb tree
On Tue, Jul 16, 2019 at 12:03 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the ntb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> WARNING: could not open /home/sfr/next/next/drivers/ntb/ntb.c: No such file or directory
>
> The only thing I could see that might be relevant is commit
>
> 56dce8121e97 ("kbuild: split out *.mod out of {single,multi}-used-m rules")
>
> and some others in the kbuild tree. Nothing has changed recently in the
> ntb tree ...
>
> drievrs/ntb builds a module called ntb but there is no ntb.c file.
>
> Any ideas?
commit 0539f970a8427138026d4738a7a32d869f1be300
Author: Masahiro Yamada <yamada.masahiro@...ionext.com>
Date: Thu Jul 11 14:44:31 2019 +0900
kbuild: create *.mod with full directory path and remove MODVERDIR
is the first bad commit.
drivers/ntb/core.c defines MODULE_VERSION().
When CONFIG_DEBUG_SECTION_MISMATCH=y,
scripts/mod/sum.c tries to open the non-existing old
source based on the stale *.mod file
during the directory descending.
I will kill cmd_secanalysis for tomorrow's linux-next.
Thanks for catching various bugs!
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists