From: Michal Simek <monstr@monstr.eu>
To: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH v2] microblaze: fix kbuild redundant file warning
Date: Tue, 1 Sep 2020 11:45:48 +0200 [thread overview]
Message-ID: <be904b19-a7af-3e05-e7af-4977b0ef241d@monstr.eu> (raw)
In-Reply-To: <4d992aee-8a69-1769-e622-8d6d6e316346@infradead.org>
On 31. 08. 20 18:38, Randy Dunlap 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: 630f289b7114 ("asm-generic: make more kernel-space headers mandatory")
> 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>
> ---
> v2: fix the Fixes: commit ID/description
>
> arch/microblaze/include/asm/Kbuild | 1 -
> 1 file changed, 1 deletion(-)
>
> --- linux-next-20200828.orig/arch/microblaze/include/asm/Kbuild
> +++ linux-next-20200828/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
>
Applied.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
prev parent reply other threads:[~2020-09-01 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 16:38 Randy Dunlap
2020-09-01 9:45 ` Michal Simek [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=be904b19-a7af-3e05-e7af-4977b0ef241d@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.simek@xilinx.com \
--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
all inboxes | Powered by JetHome®