From: Masahiro Yamada <masahiroy@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Dinh Nguyen <dinguyen@kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] nios2: add FORCE for vmlinuz.gz
Date: Thu, 24 Nov 2022 12:55:28 +0900 [thread overview]
Message-ID: <CAK7LNARfULFwt9RGq34dXSwchCWMrwauh_PfMKPCSBAqhCOHzg@mail.gmail.com> (raw)
In-Reply-To: <20221124032053.10627-1-rdunlap@infradead.org>
On Thu, Nov 24, 2022 at 12:21 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Add FORCE to placate a warning from make:
>
> arch/nios2/boot/Makefile:24: FORCE prerequisite is missing
>
> Fixes: 2fc8483fdcde ("nios2: Build infrastructure")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Dinh Nguyen <dinguyen@kernel.org>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: linux-kbuild@vger.kernel.org
Assuming this will go to the NIOS2 tree,
Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
Please let me know if I should apply this to kbuild tree.
> ---
> arch/nios2/boot/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -- a/arch/nios2/boot/Makefile b/arch/nios2/boot/Makefile
> --- a/arch/nios2/boot/Makefile
> +++ b/arch/nios2/boot/Makefile
> @@ -20,7 +20,7 @@ $(obj)/vmlinux.bin: vmlinux FORCE
> $(obj)/vmlinux.gz: $(obj)/vmlinux.bin FORCE
> $(call if_changed,gzip)
>
> -$(obj)/vmImage: $(obj)/vmlinux.gz
> +$(obj)/vmImage: $(obj)/vmlinux.gz FORCE
> $(call if_changed,uimage)
> @$(kecho) 'Kernel: $@ is ready'
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2022-11-24 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 3:20 [PATCH] nios2: add FORCE for vmlinuz.gz Randy Dunlap
2022-11-24 3:55 ` Masahiro Yamada [this message]
2022-11-26 23:32 ` Masahiro Yamada
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=CAK7LNARfULFwt9RGq34dXSwchCWMrwauh_PfMKPCSBAqhCOHzg@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.