From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] MIPS: Remove duplicated include in local.h
Date: Sun, 9 Jan 2022 22:43:23 +0100 [thread overview]
Message-ID: <20220109214323.GB2174@alpha.franken.de> (raw)
In-Reply-To: <20220107003128.81300-1-yang.lee@linux.alibaba.com>
On Fri, Jan 07, 2022 at 08:31:28AM +0800, Yang Li wrote:
> Fix following includecheck warning:
> ./arch/mips/include/asm/local.h: asm/asm.h is included more than once.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> arch/mips/include/asm/local.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/mips/include/asm/local.h b/arch/mips/include/asm/local.h
> index d4d47c846bb2..08366b1fd273 100644
> --- a/arch/mips/include/asm/local.h
> +++ b/arch/mips/include/asm/local.h
> @@ -8,7 +8,6 @@
> #include <asm/asm.h>
> #include <asm/cmpxchg.h>
> #include <asm/compiler.h>
> -#include <asm/asm.h>
>
> typedef struct
> {
> --
> 2.20.1.7.g153144c
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-01-09 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 0:31 [PATCH -next] MIPS: Remove duplicated include in local.h Yang Li
2022-01-09 21:43 ` Thomas Bogendoerfer [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=20220109214323.GB2174@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=abaci@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=yang.lee@linux.alibaba.com \
/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).