From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: stfrench@microsoft.com, linux-cifs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: cifs: Fix tracing build error with O=
Date: Thu, 20 Jun 2019 20:56:10 +0900 [thread overview]
Message-ID: <CAK7LNATbMou4DHN9=POay4RGT6upj1RoUZPwfvaB7oZwqm5rfA@mail.gmail.com> (raw)
In-Reply-To: <20190620075838.sthw4kjpp2gt6t6j@gondor.apana.org.au>
On Thu, Jun 20, 2019 at 4:58 PM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Thu, Jun 20, 2019 at 06:54:42AM +0000, yamada.masahiro@socionext.com wrote:
> >
> > I cannot reproduce the build error on the latest Linus tree.
> >
> >
> > $ make O=build allmodconfig fs/cifs/
> >
> > perfectly works for me.
>
> I was trying to build just the fs/cifs directory with
>
> make O=build M=fs/cifs
>
> But I see now that this can't possibly work as M= only supports
> absolute paths. As M= is supposed to replace SUBDIRS=, what are
> we supposed to do to build just a directory?
Documentation/kbuild/kbuild.txt says
M= and KBUILD_EXTMOD (and older form SUBDIRS= too)
are for building external modules.
Yet, many people still wrongly use them to build
in-kernel directories just because they seem to work
(but do not really).
The similar question, and the answer is here:
https://lkml.org/lkml/2019/1/17/584
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2019-06-20 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 6:40 cifs: Fix tracing build error with O= Herbert Xu
2019-06-20 6:54 ` yamada.masahiro
2019-06-20 7:58 ` Herbert Xu
2019-06-20 11:56 ` Masahiro Yamada [this message]
2019-06-20 12:47 ` Herbert Xu
2019-06-20 12:56 ` Masahiro Yamada
2019-06-20 13:36 ` Herbert Xu
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='CAK7LNATbMou4DHN9=POay4RGT6upj1RoUZPwfvaB7oZwqm5rfA@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stfrench@microsoft.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).