All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
	Nathan Chancellor <nathan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kbuild: change DTC_FLAGS_<basetarget>.o to take the path relative to $(obj)
Date: Wed, 21 Feb 2024 16:12:00 +0100	[thread overview]
Message-ID: <ZdYSwGUlOpGdAFVU@bergen.fjasle.eu> (raw)
In-Reply-To: <20240217055504.2059803-2-masahiroy@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

On Sat 17 Feb 2024 14:55:04 GMT, Masahiro Yamada wrote:
> For the same rationale as commit 54b8ae66ae1a ("kbuild: change
> *FLAGS_<basetarget>.o to take the path relative to $(obj)").
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
>  scripts/Makefile.lib | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> index 328c0d77ed48..56f7fe2b476d 100644
> --- a/scripts/Makefile.lib
> +++ b/scripts/Makefile.lib
> @@ -368,7 +368,7 @@ DTC_FLAGS += -Wnode_name_chars_strict \
>  	-Wunique_unit_address
>  endif
>  
> -DTC_FLAGS += $(DTC_FLAGS_$(basetarget))
> +DTC_FLAGS += $(DTC_FLAGS_$(target-stem))
>  
>  # Set -@ if the target is a base DTB that overlay is applied onto
>  DTC_FLAGS += $(if $(filter $(patsubst $(obj)/%,%,$@), $(base-dtb-y)), -@)
> -- 
> 2.40.1
> 
> 

Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-21 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17  5:55 [PATCH 1/2] kbuild: change tool coverage variables to take the path relative to $(obj) Masahiro Yamada
2024-02-17  5:55 ` [PATCH 2/2] kbuild: change DTC_FLAGS_<basetarget>.o " Masahiro Yamada
2024-02-21 15:12   ` Nicolas Schier [this message]
2024-02-21 15:11 ` [PATCH 1/2] kbuild: change tool coverage variables " Nicolas Schier
2024-02-21 15:24 ` Sean Christopherson

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=ZdYSwGUlOpGdAFVU@bergen.fjasle.eu \
    --to=nicolas@fjasle.eu \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@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 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.