From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts/Makefile.clean: clean also $(extra-m) and $(extra-)
Date: Thu, 12 Jun 2014 10:24:52 +0200 [thread overview]
Message-ID: <539963D4.3040409@suse.cz> (raw)
In-Reply-To: <1402019035-2190-1-git-send-email-yamada.m@jp.panasonic.com>
Dne 6.6.2014 03:43, Masahiro Yamada napsal(a):
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> ---
> scripts/Makefile.clean | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/Makefile.clean b/scripts/Makefile.clean
> index 686cb0d..a651cee 100644
> --- a/scripts/Makefile.clean
> +++ b/scripts/Makefile.clean
> @@ -40,8 +40,8 @@ subdir-ymn := $(addprefix $(obj)/,$(subdir-ymn))
> # build a list of files to remove, usually relative to the current
> # directory
>
> -__clean-files := $(extra-y) $(always) \
> - $(targets) $(clean-files) \
> +__clean-files := $(extra-y) $(extra-m) $(extra-) \
> + $(always) $(targets) $(clean-files) \
Do you have an example where generated files are left in the tree after
make clean? This should go into the changelog.
Dne 12.6.2014 07:46, Masahiro Yamada napsal(a):> Hi Michal,
> If possible, please consider to include this patch in GIT-PULL.
Sorry, I need to do a cut off at some point :). I'll merge it right
after the merge window. If you provide a reproducer in the changelog,
I'll send it to Linus for the next -rc.
Michal
next prev parent reply other threads:[~2014-06-12 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:43 [PATCH] scripts/Makefile.clean: clean also $(extra-m) and $(extra-) Masahiro Yamada
2014-06-06 13:30 ` Sam Ravnborg
2014-06-12 5:46 ` Masahiro Yamada
2014-06-12 8:24 ` Michal Marek [this message]
2014-06-12 8:40 ` Masahiro Yamada
2014-06-12 8:41 ` Michal Marek
2014-06-18 19:53 ` Michal Marek
2014-06-20 12:22 ` Masahiro Yamada
2014-06-20 13:23 ` Michal Marek
2014-07-03 20:55 ` Michal Marek
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=539963D4.3040409@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.m@jp.panasonic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.