From: Masahiro Yamada <masahiroy@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Michal Simek <monstr@monstr.eu>,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] microblaze: fix kbuild redundant file warning
Date: Sat, 29 Aug 2020 15:28:21 +0900 [thread overview]
Message-ID: <CAK7LNATA5vpEaPHXEgnzR3PDpPZbXYXNtr2ZOgyL2QqVxcmE_g@mail.gmail.com> (raw)
In-Reply-To: <21eddfa7-2b7c-00c4-ad5b-40878036f987@infradead.org>
On Sat, Aug 29, 2020 at 3:35 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix build warning since this file is already listed in
> include/asm-generic/Kbuild.
>
> ../scripts/Makefile.asm-generic:25: redundant generic-y found in arch/microblaze/include/asm/Kbuild: hw_irq.h
>
> Fixes: 7e8f54cd4e26 ("microblaze: Remove empty headers")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Michal Simek <monstr@monstr.eu>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> arch/microblaze/include/asm/Kbuild | 1 -
> 1 file changed, 1 deletion(-)
>
> --- linux-next-20200825.orig/arch/microblaze/include/asm/Kbuild
> +++ linux-next-20200825/arch/microblaze/include/asm/Kbuild
> @@ -1,7 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0
> generated-y += syscall_table.h
> generic-y += extable.h
> -generic-y += hw_irq.h
> generic-y += kvm_para.h
> generic-y += local64.h
> generic-y += mcs_spinlock.h
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2020-08-29 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 18:35 [PATCH] microblaze: fix kbuild redundant file warning Randy Dunlap
2020-08-29 6:28 ` Masahiro Yamada [this message]
2020-08-31 14:01 ` Michal Simek
2020-08-31 16:22 ` Masahiro Yamada
2020-08-31 16:33 ` Randy Dunlap
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=CAK7LNATA5vpEaPHXEgnzR3PDpPZbXYXNtr2ZOgyL2QqVxcmE_g@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--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 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).