Linux-Next discussions
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
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: Mon, 15 Jul 2019 21:46:42 -0600	[thread overview]
Message-ID: <7ec45bb7-4e72-2415-21f7-44dadaa0fada@deltatee.com> (raw)
In-Reply-To: <20190716130341.03b02792@canb.auug.org.au>



On 2019-07-15 9:03 p.m., Stephen Rothwell 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?

I renamed the ntb.c file to core.c so we could add more files to build
ntb.ko. See [1].

Thanks,

Logan


[1]
https://lore.kernel.org/linux-iommu/20190422210528.15289-6-logang@deltatee.com/

  reply	other threads:[~2019-07-16  3:46 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 [this message]
2019-07-16  4:54   ` Stephen Rothwell
2019-07-16  6:02 ` Masahiro Yamada
  -- strict thread matches above, loose matches on Subject: below --
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=7ec45bb7-4e72-2415-21f7-44dadaa0fada@deltatee.com \
    --to=logang@deltatee.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 \
    --cc=yamada.masahiro@socionext.com \
    /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