From: Christoph Hellwig <hch@lst.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: SUBDIRS= replacement
Date: Thu, 17 Jan 2019 15:55:31 +0100 [thread overview]
Message-ID: <20190117145531.GA21429@lst.de> (raw)
Hi Masahiro, hi Michal,
I just got this beatiful warning:
hch@carbon:~/work/xfs$ make -j4 SUBDIRS=fs/xfs
Makefile:189: ================= WARNING ================
Makefile:190: 'SUBDIRS' will be removed after Linux 5.3
Makefile:191: Please use 'M=' or 'KBUILD_EXTMOD' instead
Makefile:192: ==========================================
Both the replacement seem to be geared towards building externals
modules. But what is the replacement for just building a directory
of the normal kernel tree?
E.g. what hit this is that I rebased an XFS series, and wanted to
compile test just the xfs code for each step using
make -j4 SUBDIRS=fs/xfs
next reply other threads:[~2019-01-17 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:55 Christoph Hellwig [this message]
2019-01-17 16:29 ` SUBDIRS= replacement Sam Ravnborg
2019-01-17 17:09 ` Christoph Hellwig
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=20190117145531.GA21429@lst.de \
--to=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--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