From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
Xi Wang <wangxi11@huawei.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: add more hints about SUBDIRS replacement
Date: Wed, 26 Jun 2019 16:30:46 +0200 [thread overview]
Message-ID: <20190626143046.GA12510@ravnborg.org> (raw)
In-Reply-To: <20190625085127.9446-1-yamada.masahiro@socionext.com>
On Tue, Jun 25, 2019 at 05:51:27PM +0900, Masahiro Yamada wrote:
> Commit 0126be38d988 ("kbuild: announce removal of SUBDIRS if used")
> added a hint about the 'SUBDIRS' replacement, but it was not clear
> enough.
>
> Multiple people sent me similar questions, patches.
>
> https://lkml.org/lkml/2019/1/17/456
>
> I did not mean to suggest M= for building a subdirectory in the kernel
> tree.
>
> >From the commit 669efc76b317 ("net: hns3: fix compile error"), people
> already (ab)use M=... to do that because it seems to work to some extent.
>
> Documentation/kbuild/kbuild.txt says M= and KBUILD_EXTMOD are used for
> building external modules.
>
> In fact, Kbuild supports the single target '%/' for this purpose, but
> this may not be noticed much.
>
> Kindly add more hints.
>
> Makefile:213: ================= WARNING ================
> Makefile:214: 'SUBDIRS' will be removed after Linux 5.3
> Makefile:215:
> Makefile:216: If you are building an individual subdirectory
> Makefile:217: in the kernel tree, you can do like this:
> Makefile:218: $ make path/to/dir/you/want/to/build/
> Makefile:219: (Do not forget the trailing slash)
> Makefile:220:
> Makefile:221: If you are building an external module,
> Makefile:222: Please use 'M=' or 'KBUILD_EXTMOD' instead
> Makefile:223: ==========================================
>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Nice!
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Sam
next prev parent reply other threads:[~2019-06-26 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 8:51 Masahiro Yamada
2019-06-26 14:30 ` Sam Ravnborg [this message]
2019-07-06 14:30 ` 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=20190626143046.GA12510@ravnborg.org \
--to=sam@ravnborg.org \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=wangxi11@huawei.com \
--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
Powered by JetHome