From: Jens Axboe <axboe@kernel.dk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Christoph Hellwig <hch@lst.de>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: building individual files in subdirectories
Date: Sun, 17 Nov 2019 19:30:42 -0700 [thread overview]
Message-ID: <a08ab4f0-d500-331b-da70-388e6244bc67@kernel.dk> (raw)
In-Reply-To: <CAK7LNAQFy=AfJtk4GT+FL=Kzcf6Ev=keKoUz_7Le7iZOQEc90g@mail.gmail.com>
On 11/17/19 5:15 PM, Masahiro Yamada wrote:
> Hi Jens,
>
>
> (related to https://lkml.org/lkml/2019/11/15/1152)
>
>
> I received questions about single builds not working properly
> some times in the past.
>
> For example, the following is a post from Christoph to kbuild ML,
> and my reply to it.
I'm not saying it isn't useful, what I'm saying is that slowing
things down by almost 100% seems excessive!
--
Jens Axboe
prev parent reply other threads:[~2019-11-18 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 12:11 building individual files in subdirectories Christoph Hellwig
2019-05-29 1:12 ` Masahiro Yamada
2019-11-18 0:15 ` Masahiro Yamada
2019-11-18 2:30 ` Jens Axboe [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=a08ab4f0-d500-331b-da70-388e6244bc67@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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