From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: zhangjiao2 <zhangjiao2@cmss.chinamobile.com>,
lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: iio: rm .*.cmd when make clean
Date: Wed, 4 Sep 2024 01:43:45 +0300 [thread overview]
Message-ID: <ZteRIY3H0o4wYy1G@surfacebook.localdomain> (raw)
In-Reply-To: <20240903200923.21c4c1ff@jic23-huawei>
Tue, Sep 03, 2024 at 08:09:23PM +0100, Jonathan Cameron kirjoitti:
> On Mon, 2 Sep 2024 11:54:12 +0800
> zhangjiao2 <zhangjiao2@cmss.chinamobile.com> wrote:
> > On Sat, 31 Aug 2024 11:59:31, Jonathan Cameron wrote:
> > >> On Thu, 29 Aug 2024 13:33:09 +0800
> > >> zhangjiao2 <zhangjiao2@cmss.chinamobile.com> wrote:
...
> > >> rm .*.cmd when make clean
> > > Where do those come from?
> > Those come from tools/build/Build.include.
> > These .*.cmd files ware created when make.
> > So clean them when make clean.
> Hmm. I'm still a little curious about the path to those getting created as
> I don't see them. when testing.
At least this is documented here
https://elixir.bootlin.com/linux/v6.11-rc6/source/tools/build/Documentation/Build.txt#L149
Here is where they are being created
https://elixir.bootlin.com/linux/v6.11-rc6/source/tools/build/Build.include#L58
And it seems it is only created when there are actual dependencies.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-09-03 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 5:33 zhangjiao2
2024-08-31 10:59 ` Jonathan Cameron
2024-09-02 3:54 ` zhangjiao2
2024-09-03 19:09 ` Jonathan Cameron
2024-09-03 22:43 ` Andy Shevchenko [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=ZteRIY3H0o4wYy1G@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangjiao2@cmss.chinamobile.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
all inboxes | Powered by JetHome®