From: Wei Liu <wei.liu@kernel.org>
To: cgel.zte@gmail.com
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
ran jianping <ran.jianping@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] x86/hyperv: remove duplicate include in ivm.c
Date: Thu, 28 Oct 2021 11:38:21 +0000 [thread overview]
Message-ID: <20211028113821.4uormm52hfr5hlnd@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20211027090544.2383-1-ran.jianping@zte.com.cn>
On Wed, Oct 27, 2021 at 09:05:44AM +0000, cgel.zte@gmail.com wrote:
> From: ran jianping <ran.jianping@zte.com.cn>
>
> 'linux/types.h' included in 'arch/x86/hyperv/ivm.c'
> is duplicated.It is also included on the 12 line.
> 'linux/bitfield.h'included in 'arch/x86/hyperv/ivm.c'
> is duplicated.It is also included on the 13 line.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ran jianping <ran.jianping@zte.com.cn>
This is already dealt with. Thanks.
> ---
> arch/x86/hyperv/ivm.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/x86/hyperv/ivm.c b/arch/x86/hyperv/ivm.c
> index 4d012fd9d95d..479201ceae8e 100644
> --- a/arch/x86/hyperv/ivm.c
> +++ b/arch/x86/hyperv/ivm.c
> @@ -9,8 +9,6 @@
> #include <linux/types.h>
> #include <linux/bitfield.h>
> #include <linux/hyperv.h>
> -#include <linux/types.h>
> -#include <linux/bitfield.h>
> #include <linux/slab.h>
> #include <asm/svm.h>
> #include <asm/sev.h>
> --
> 2.25.1
>
prev parent reply other threads:[~2021-10-28 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 9:05 cgel.zte
2021-10-28 11:38 ` Wei Liu [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=20211028113821.4uormm52hfr5hlnd@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bp@alien8.de \
--cc=cgel.zte@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ran.jianping@zte.com.cn \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zealci@zte.com.cn \
/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®