From: Christoph Hellwig <hch@lst.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@lst.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: SUBDIRS= replacement
Date: Thu, 17 Jan 2019 18:09:09 +0100 [thread overview]
Message-ID: <20190117170909.GB31280@lst.de> (raw)
In-Reply-To: <20190117162921.GB31768@ravnborg.org>
On Thu, Jan 17, 2019 at 05:29:21PM +0100, Sam Ravnborg wrote:
> Try:
>
> make -j4 fs/xfs/
>
> This is the recommend way to do so.
> Let us know if you see problem with this approach.
Yes, that seems to work. I think the warning should suggest that as
well, as it probably is the more common use compare to building
external modules.
prev parent reply other threads:[~2019-01-17 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:55 SUBDIRS= replacement Christoph Hellwig
2019-01-17 16:29 ` Sam Ravnborg
2019-01-17 17:09 ` Christoph Hellwig [this message]
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=20190117170909.GB31280@lst.de \
--to=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=sam@ravnborg.org \
--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;
as well as URLs for NNTP newsgroup(s).