From: Masahiro Yamada <masahiroy@kernel.org>
To: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] kbuild: remove trailing slash from devicetree/binding/ for descending
Date: Tue, 3 Mar 2020 22:47:39 +0900 [thread overview]
Message-ID: <CAK7LNARVX6bJPO0yPo7k_ateDNmk_bXGfoR8nmkEUbkCVtJTLw@mail.gmail.com> (raw)
In-Reply-To: <20200226175325.8787-1-masahiroy@kernel.org>
On Thu, Feb 27, 2020 at 2:53 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> obj-* needs a trailing slash for a directory, but subdir-* does not
> because it already implies a directory.
>
> Also, change subdir-y to subdir- to ensure this is effective only
> for cleaning targets.
>
> This makes the cleaning log consistent. (no trailing slash)
>
> Before:
>
> $ make clean
> CLEAN Documentation/devicetree/bindings/
>
> After:
>
> $ make clean
> CLEAN Documentation/devicetree/bindings
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
Applied to linux-kbuild.
>
> Documentation/Makefile | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index d77bb607aea4..39569a2e1953 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -2,7 +2,8 @@
> # Makefile for Sphinx documentation
> #
>
> -subdir-y := devicetree/bindings/
> +# for cleaning
> +subdir- := devicetree/bindings
>
> # Check for broken documentation file references
> ifeq ($(CONFIG_WARN_MISSING_DOCUMENTS),y)
> --
> 2.17.1
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2020-03-03 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 17:53 [PATCH] kbuild: remove trailing slash from devicetree/binding/ for descending Masahiro Yamada
2020-03-03 13:47 ` Masahiro Yamada [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=CAK7LNARVX6bJPO0yPo7k_ateDNmk_bXGfoR8nmkEUbkCVtJTLw@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).