CEPH filesystem development
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jevon Qiao <scaleqiao@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	qemu-devel@nongnu.org, haomaiwang@gmail.com, mst@redhat.com,
	aneesh.kumar@linux.vnet.ibm.com, Sage Weil <sage@newdream.net>,
	gfarnum@redhat.com, gkurz@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] add CephFS support in VirtFS
Date: Wed, 17 Feb 2016 09:37:16 +0000	[thread overview]
Message-ID: <20160217093716.GC30300@redhat.com> (raw)
In-Reply-To: <56C421F6.1000102@gmail.com>

On Wed, Feb 17, 2016 at 03:32:06PM +0800, Jevon Qiao wrote:
> Hi Daniel,
> 
> Thank you for reviewing my code, please see my reply in-line.
> On 15/2/16 17:17, Daniel P. Berrange wrote:
> >On Sun, Feb 14, 2016 at 01:06:40PM +0800, Jevon Qiao wrote:
> >>+
> >>+static int cephfs_parse_opts(QemuOpts *opts, struct FsDriverEntry *fse)
> >>+{
> >>+    const char *sec_model = qemu_opt_get(opts, "security_model");
> >>+    const char *path = qemu_opt_get(opts, "path");
> >>+
> >>+    if (!sec_model) {
> >>+        fprintf(stderr, "Invalid argument security_model specified with "
> >>+        "cephfs fsdriver\n");
> >Bad indent.
> BTW, is there any tool I can use to check the coding style in Qemu?

As already mentioned there is 'scripts/checkpatch.pl'. If you are just
wanting to check a single patch before sending it you can run it
manually eg

   git show | ./scripts/checkpatch.pl -

If you have a branch holding a whole series of patches to submit, then
it is easier to automate it. eg

 git rebase -i master -x 'git show | ./scripts/checkpatch.pl -'


NB, the script doesn't catch all style problems, but it does a pretty
good job. So even if the script passes, don't be suprised if reviewers
point out further style issues.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2016-02-17  9:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  5:06 [PATCH] add CephFS support in VirtFS Jevon Qiao
2016-02-14  6:01 ` Aneesh Kumar K.V
2016-02-14  6:41   ` Jevon Qiao
2016-02-14  7:26 ` [PATCH 1/2] " Jevon Qiao
2016-02-15  9:17 ` [Qemu-devel] [PATCH] " Daniel P. Berrange
2016-02-17  7:32   ` Jevon Qiao
2016-02-17  8:01     ` Greg Kurz
2016-02-17  8:49       ` Jevon Qiao
2016-02-17  9:04         ` Greg Kurz
2016-02-18  1:36           ` Jevon Qiao
2016-02-17  9:37     ` Daniel P. Berrange [this message]
2016-02-17 15:41       ` Eric Blake
2016-02-18  1:39       ` Jevon Qiao
2016-03-09  3:10         ` Gerard Braad
2016-03-09  9:31           ` Greg Kurz

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=20160217093716.GC30300@redhat.com \
    --to=berrange@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@redhat.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=haomaiwang@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sage@newdream.net \
    --cc=scaleqiao@gmail.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