mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: Yue Haibing <yuehaibing@huawei.com>,
	christoffer.dall@arm.com, marc.zyngier@arm.com,
	james.morse@arm.com, julien.thierry@arm.com,
	suzuki.poulose@arm.com, andre.przywara@arm.com
Cc: linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] KVM: arm: vgic: Make two functions static
Date: Thu, 21 Mar 2019 00:38:24 +0530	[thread overview]
Message-ID: <de8edaed-a37b-f143-75d8-9db9c45c5543@codeaurora.org> (raw)
In-Reply-To: <20190320141813.10380-1-yuehaibing@huawei.com>


On 3/20/2019 7:48 PM, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> Fix sparse warnings:
>
> arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-its.c:1732:5: warning:
>   symbol 'vgic_its_has_attr_regs' was not declared. Should it be static?
> arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-its.c:1753:5: warning:
>   symbol 'vgic_its_attr_regs_access' was not declared. Should it be static?
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
>   virt/kvm/arm/vgic/vgic-its.c | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
> index ab3f477..a97db69 100644
> --- a/virt/kvm/arm/vgic/vgic-its.c
> +++ b/virt/kvm/arm/vgic/vgic-its.c
> @@ -1729,8 +1729,8 @@ static void vgic_its_destroy(struct kvm_device *kvm_dev)
>   	kfree(its);
>   }
>   
> -int vgic_its_has_attr_regs(struct kvm_device *dev,
> -			   struct kvm_device_attr *attr)
> +static int vgic_its_has_attr_regs(struct kvm_device *dev,
> +				  struct kvm_device_attr *attr)
>   {
>   	const struct vgic_register_region *region;
>   	gpa_t offset = attr->attr;
> @@ -1750,9 +1750,9 @@ int vgic_its_has_attr_regs(struct kvm_device *dev,
>   	return 0;
>   }
>   
> -int vgic_its_attr_regs_access(struct kvm_device *dev,
> -			      struct kvm_device_attr *attr,
> -			      u64 *reg, bool is_write)
> +static int vgic_its_attr_regs_access(struct kvm_device *dev,
> +				     struct kvm_device_attr *attr,
> +				     u64 *reg, bool is_write)
>   {
>   	const struct vgic_register_region *region;
>   	struct vgic_its *its;


Acked-by: Mukesh Ojha <mojha@codeaurora.org>

Cheers,
Mukesh


      parent reply	other threads:[~2019-03-20 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 14:18 Yue Haibing
2019-03-20 17:36 ` Marc Zyngier
2019-03-20 19:08 ` Mukesh Ojha [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=de8edaed-a37b-f143-75d8-9db9c45c5543@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=andre.przywara@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=james.morse@arm.com \
    --cc=julien.thierry@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=yuehaibing@huawei.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

all inboxes | Powered by JetHome®