public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Yi Wang <wang.yi59@zte.com.cn>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, x86@kernel.org, suravee.suthikulpanit@amd.com,
	puwen@hygon.cn, davidwang@zhaoxin.com,
	linux-kernel@vger.kernel.org, dwmw@amazon.co.uk,
	gregkh@linuxfoundation.org, thomas.lendacky@amd.com,
	fenghua.yu@intel.com, pbonzini@redhat.com,
	konrad.wilk@oracle.com, zhong.weidong@zte.com.cn
Subject: Re: [PATCH 0/3] x86/cpu: fix some prototype warning
Date: Wed, 7 Nov 2018 10:46:13 +0100	[thread overview]
Message-ID: <20181107094613.GA69469@gmail.com> (raw)
In-Reply-To: <1541580877-45723-1-git-send-email-wang.yi59@zte.com.cn>


* Yi Wang <wang.yi59@zte.com.cn> wrote:

> This series of patch fix some prototype warning because
> of missing include file.
> 
> Yi Wang (3):
>   x86/cpu: fix prototype warning in cacheinfo.c
>   x86/cpu: fix prototype warning in scattered.c
>   x86/cpu: fix prototype warning in topology.c
> 
>  arch/x86/kernel/cpu/cacheinfo.c | 1 +
>  arch/x86/kernel/cpu/scattered.c | 2 ++
>  arch/x86/kernel/cpu/topology.c  | 2 ++
>  3 files changed, 5 insertions(+)

Could you please submit this as a single patch?

Thanks,

	Ingo

      parent reply	other threads:[~2018-11-07  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  8:54 [PATCH 0/3] x86/cpu: fix some prototype warning Yi Wang
2018-11-07  8:54 ` [PATCH 1/3] x86/cpu: fix prototype warning in cacheinfo.c Yi Wang
2018-11-07  8:54 ` [PATCH 2/3] x86/cpu: fix prototype warning in scattered.c Yi Wang
2018-11-07  8:54 ` [PATCH 3/3] x86/cpu: fix prototype warning in topology.c Yi Wang
2018-11-07  9:46 ` Ingo Molnar [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=20181107094613.GA69469@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=davidwang@zhaoxin.com \
    --cc=dwmw@amazon.co.uk \
    --cc=fenghua.yu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=puwen@hygon.cn \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=wang.yi59@zte.com.cn \
    --cc=x86@kernel.org \
    --cc=zhong.weidong@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