All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>, gleb@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: make the declaration of functions within 80 characters
Date: Mon, 14 Sep 2015 18:43:38 +0200	[thread overview]
Message-ID: <55F6F93A.7060705@redhat.com> (raw)
In-Reply-To: <1441951973-5566-1-git-send-email-weiyang@linux.vnet.ibm.com>



On 11/09/2015 08:12, Wei Yang wrote:
> After 'commit 0b8ba4a2b658 ("KVM: fix checkpatch.pl errors in
> kvm/coalesced_mmio.h")', the declaration of the two function will exceed 80
> characters.
> 
> This patch reduces the TAPs to make each line in 80 characters.
> 
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> ---
>  virt/kvm/coalesced_mmio.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/virt/kvm/coalesced_mmio.h b/virt/kvm/coalesced_mmio.h
> index 5cbf190..6bca74c 100644
> --- a/virt/kvm/coalesced_mmio.h
> +++ b/virt/kvm/coalesced_mmio.h
> @@ -24,9 +24,9 @@ struct kvm_coalesced_mmio_dev {
>  int kvm_coalesced_mmio_init(struct kvm *kvm);
>  void kvm_coalesced_mmio_free(struct kvm *kvm);
>  int kvm_vm_ioctl_register_coalesced_mmio(struct kvm *kvm,
> -																				struct kvm_coalesced_mmio_zone *zone);
> +					struct kvm_coalesced_mmio_zone *zone);
>  int kvm_vm_ioctl_unregister_coalesced_mmio(struct kvm *kvm,
> -																				struct kvm_coalesced_mmio_zone *zone);
> +					struct kvm_coalesced_mmio_zone *zone);
>  
>  #else
>  
> 

Ouch.  I wonder what I did to get that result.  Applied, thanks.

Paolo

      reply	other threads:[~2015-09-14 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  6:12 [PATCH] KVM: make the declaration of functions within 80 characters Wei Yang
2015-09-14 16:43 ` Paolo Bonzini [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=55F6F93A.7060705@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=weiyang@linux.vnet.ibm.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 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.