linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	Chris Zankel <chris@zankel.net>,
	"open list:TENSILICA XTENSA PORT (xtensa)" 
	<linux-xtensa@linux-xtensa.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xtensa: add boot subdirectories build artifacts to 'targets'
Date: Sat, 25 Jul 2020 16:10:28 +0900	[thread overview]
Message-ID: <CAK7LNASexG=PFPSRFSsVyrM1CTy-NN9aJC1TFAt_4HCJ+XU48g@mail.gmail.com> (raw)
In-Reply-To: <CAMo8BfJv38cPOAOOMGn8R7-CtBy2BCbMRkMAeXNZ=A4YbtTPbw@mail.gmail.com>

On Wed, Jul 22, 2020 at 12:57 PM Max Filippov <jcmvbkbc@gmail.com> wrote:
>
> On Tue, Jul 21, 2020 at 5:47 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
> >
> > Xtensa always rebuilds the following even if nothing in the source code
> > has been changed. Passing V=2 shows the reason.
> >
> >   AS      arch/xtensa/boot/boot-elf/bootstrap.o - due to bootstrap.o not in $(targets)
> >   LDS     arch/xtensa/boot/boot-elf/boot.lds - due to boot.lds not in $(targets)
> >
> > They are built by if_changed(_dep). Add them to 'targets' so .*.cmd files
> > are included.
> >
> > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> > ---
> >
> >  arch/xtensa/boot/boot-elf/Makefile     | 1 +
> >  arch/xtensa/boot/boot-redboot/Makefile | 1 +
> >  2 files changed, 2 insertions(+)
>
> Acked-by: Max Filippov <jcmvbkbc@gmail.com>
>
> --
> Thanks.
> -- Max


Applied to linux-kbuild.


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2020-07-25  7:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  0:47 [PATCH] xtensa: add boot subdirectories build artifacts to 'targets' Masahiro Yamada
2020-07-22  3:56 ` Max Filippov
2020-07-25  7:10   ` 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='CAK7LNASexG=PFPSRFSsVyrM1CTy-NN9aJC1TFAt_4HCJ+XU48g@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.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).