From: "Marek Behún" <marek.behun@nic.cz>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] Makefile: make clean should delete include/generated/env.in
Date: Wed, 30 Mar 2022 14:16:55 +0200 [thread overview]
Message-ID: <20220330141655.0de0521e@thinkpad> (raw)
In-Reply-To: <20220330101100.45774-1-heinrich.schuchardt@canonical.com>
On Wed, 30 Mar 2022 12:11:00 +0200
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:
> 'make sifive_unamtched_defconfig; make clean; make' fails if file
> include/generated/env.in exists. 'make clean' should remove all files that
> stop building.
>
> Add file include/generated/env.in to the clean target.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
I also noticed this :)
Reviewed-by: Marek Behún <marek.behun@nic.cz>
next prev parent reply other threads:[~2022-03-30 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:11 [PATCH 1/1] Makefile: make clean should delete include/generated/env.in Heinrich Schuchardt
2022-03-30 12:16 ` Marek Behún [this message]
2022-03-31 13:39 ` Tom Rini
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=20220330141655.0de0521e@thinkpad \
--to=marek.behun@nic.cz \
--cc=heinrich.schuchardt@canonical.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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