From: Michael Ellerman <mpe@ellerman.id.au>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Fix duplicate included _clear.h
Date: Tue, 08 Jun 2021 12:26:43 +1000 [thread overview]
Message-ID: <874ke9f5wc.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <1623061512-31651-1-git-send-email-jiapeng.chong@linux.alibaba.com>
Jiapeng Chong <jiapeng.chong@linux.alibaba.com> writes:
> Clean up the following includecheck warning:
>
> ./arch/powerpc/perf/req-gen/perf.h: _clear.h is included more than once.
That's by design.
See the error reported by the kbuild robot.
> No functional change.
Not true.
cheers
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> arch/powerpc/perf/req-gen/perf.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/powerpc/perf/req-gen/perf.h b/arch/powerpc/perf/req-gen/perf.h
> index fa9bc80..59fa588 100644
> --- a/arch/powerpc/perf/req-gen/perf.h
> +++ b/arch/powerpc/perf/req-gen/perf.h
> @@ -51,7 +51,6 @@ enum CAT2(NAME_LOWER, _requests) {
> * r_fields
> * };
> */
> -#include "_clear.h"
> #define STRUCT_NAME__(name_lower, r_name) name_lower ## _ ## r_name
> #define STRUCT_NAME_(name_lower, r_name) STRUCT_NAME__(name_lower, r_name)
> #define STRUCT_NAME(r_name) STRUCT_NAME_(NAME_LOWER, r_name)
> --
> 1.8.3.1
prev parent reply other threads:[~2021-06-08 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 10:25 [PATCH] powerpc: Fix duplicate included _clear.h Jiapeng Chong
2021-06-07 20:01 ` kernel test robot
2021-06-08 2:26 ` Michael Ellerman [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=874ke9f5wc.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).