All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: "Ying Fang" <fangying1@huawei.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>, 李强 <liq3ea@163.com>,
	"Qemu Developers" <qemu-devel@nongnu.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vnc: fix memory leak when vnc disconnect
Date: Mon, 2 Sep 2019 10:02:30 +0100	[thread overview]
Message-ID: <20190902090230.GC30123@redhat.com> (raw)
In-Reply-To: <CAKXe6SKO60x5MGW22iDQuKh=JLByQVULJpwD+0DffpzeG231xw@mail.gmail.com>

On Sat, Aug 31, 2019 at 11:52:47PM +0800, Li Qiang wrote:
> <no-reply@patchew.org> 于2019年8月31日周六 下午11:46写道:
> 
> > Patchew URL:
> > https://patchew.org/QEMU/20190831153922.121308-1-liq3ea@163.com/
> >
> >
> >
> > Hi,
> >
> > This series seems to have some coding style problems. See output below for
> > more information:
> >
> > Type: series
> > Message-id: 20190831153922.121308-1-liq3ea@163.com
> > Subject: [Qemu-devel] [PATCH] vnc: fix memory leak when vnc disconnect
> >
> > === TEST SCRIPT BEGIN ===
> > #!/bin/bash
> > git rev-parse base > /dev/null || exit 0
> > git config --local diff.renamelimit 0
> > git config --local diff.renames True
> > git config --local diff.algorithm histogram
> > ./scripts/checkpatch.pl --mailback base..
> > === TEST SCRIPT END ===
> >
> > Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
> > Switched to a new branch 'test'
> > fb52b49 vnc: fix memory leak when vnc disconnect
> >
> > === OUTPUT BEGIN ===
> > ERROR: spaces required around that '*' (ctx:WxB)
> > #118: FILE: ui/vnc-enc-tight.c:355:
> > +        data = (uint##bpp##_t *)vs->tight->tight.buffer;                \
> >                                ^
> >
> >
> 
> Hello Paolo and the Checkpatch maintainers,
> 
> I also see this error in scripts/checkpatch.pl.
> However when I add sapces around '*". I got following error:
> 
> ERROR: space prohibited before that close parenthesis ')'
> 
> #124: FILE: ui/vnc-enc-tight.c:355:
> 
> +        data = (uint##bpp##_t * )vs->tight->tight.buffer;               \
> 
> 
> 
> So I'm confused how to make checkpatch.pl happy.
> 
> 
> Any one has suggests? Or we need a patch for checkpatch.pl?

Either ignore this patch warning, or figure out how to fix
checkpatch.pl though the latter quite be quite hard


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  reply	other threads:[~2019-09-02  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 15:39 [Qemu-devel] [PATCH] vnc: fix memory leak when vnc disconnect Li Qiang
2019-08-31 15:46 ` no-reply
2019-08-31 15:52   ` Li Qiang
2019-09-02  9:02     ` Daniel P. Berrangé [this message]
2019-09-09 17:18       ` Paolo Bonzini
2019-09-17 11:45 ` Gerd Hoffmann
2019-09-17 13:42   ` Li Qiang

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=20190902090230.GC30123@redhat.com \
    --to=berrange@redhat.com \
    --cc=fangying1@huawei.com \
    --cc=kraxel@redhat.com \
    --cc=liq3ea@163.com \
    --cc=liq3ea@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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.