All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: kbuild test robot <fengguang.wu@intel.com>,
	Antonios Motakis <a.motakis@virtualopensystems.com>
Cc: kbuild-all@01.org, Alex Williamson <alex.williamson@redhat.com>,
	Baptiste Reynal <b.reynal@virtualopensystems.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH vfio] vfio: virqfd_lock can be static
Date: Tue, 17 Mar 2015 11:49:02 +0100	[thread overview]
Message-ID: <5508069E.5030706@linaro.org> (raw)
In-Reply-To: <20150316234321.GA24901@lkp-sb04>

Reviewed-by: Eric Auger <eric.auger@linaro.org>

On 03/17/2015 12:43 AM, kbuild test robot wrote:
> 
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
>  virqfd.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/vfio/virqfd.c b/drivers/vfio/virqfd.c
> index 5967899..3d19aaf 100644
> --- a/drivers/vfio/virqfd.c
> +++ b/drivers/vfio/virqfd.c
> @@ -16,7 +16,7 @@
>  #include <linux/slab.h>
>  
>  static struct workqueue_struct *vfio_irqfd_cleanup_wq;
> -DEFINE_SPINLOCK(virqfd_lock);
> +static DEFINE_SPINLOCK(virqfd_lock);
>  
>  int __init vfio_virqfd_init(void)
>  {
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2015-03-17 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 23:43 [vfio:next 19/21] drivers/vfio/virqfd.c:19:1: sparse: symbol 'virqfd_lock' was not declared. Should it be static? kbuild test robot
2015-03-16 23:43 ` [PATCH vfio] vfio: virqfd_lock can be static kbuild test robot
2015-03-17 10:49   ` Eric Auger [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=5508069E.5030706@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=a.motakis@virtualopensystems.com \
    --cc=alex.williamson@redhat.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.