linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jon Mason <jdmason@kudzu.us>,
	NTB Mailing List <linux-ntb@googlegroups.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the ntb tree
Date: Tue, 16 Jul 2019 15:02:30 +0900	[thread overview]
Message-ID: <CAK7LNASTDPG6bDeXj9GfWQVB559D6GEsZiUaiqCfzcPpteZxZw@mail.gmail.com> (raw)
In-Reply-To: <20190716130341.03b02792@canb.auug.org.au>

On Tue, Jul 16, 2019 at 12:03 PM Stephen Rothwell <sfr@canb.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@socionext.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

  parent reply	other threads:[~2019-07-16  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16  3:03 linux-next: build warning after merge of the ntb tree Stephen Rothwell
2019-07-16  3:46 ` Logan Gunthorpe
2019-07-16  4:54   ` Stephen Rothwell
2019-07-16  6:02 ` Masahiro Yamada [this message]
2022-06-21 10:02 Stephen Rothwell

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=CAK7LNASTDPG6bDeXj9GfWQVB559D6GEsZiUaiqCfzcPpteZxZw@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-ntb@googlegroups.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).