From: Greg Kurz <groug@kaod.org>
To: xiezhide <xiezhide@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"berto@igalia.com" <berto@igalia.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"aneesh.kumar@linux.vnet.ibm.com"
<aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-9p: fix coding style issue
Date: Mon, 12 Nov 2018 18:54:59 +0100 [thread overview]
Message-ID: <20181112185459.55d27dc9@bahia.lan> (raw)
In-Reply-To: <A02D6AA901860840B46E751C5E9E38B43CC96A40@DGGEML532-MBX.china.huawei.com>
On Mon, 12 Nov 2018 01:12:33 +0000
xiezhide <xiezhide@huawei.com> wrote:
> fix two coding style issue
>
These coding style issues seem to come from patch 1... It is weird to
introduce coding style nits and to fix them afterwards. Just avoid
them in the first place (./scripts/checkpatch.pl is your friend).
> Signed-off-by: x00390961 <xiezhide@huawei.com<mailto:xiezhide@huawei.com>>
> ---
> fsdev/qemu-fsdev-throttle.c | 2 +-
> include/qemu/throttle-options.h | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fsdev/qemu-fsdev-throttle.c b/fsdev/qemu-fsdev-throttle.c
> index 7d313f2..fa2b0c8 100644
> --- a/fsdev/qemu-fsdev-throttle.c
> +++ b/fsdev/qemu-fsdev-throttle.c
> @@ -116,7 +116,7 @@ void fsdev_get_io_throttle(FsThrottle *fst, FsdevIOThrottle **fs9pcfg,
> ThrottleLimits *tlimits;
> FsdevIOThrottle *fscfg = g_malloc(sizeof(*fscfg));
> tlimits = qapi_FsdevIOThrottle_base(fscfg);
> - fscfg->has_id = true;
> + fscfg->has_id = true;
> fscfg->id = g_strdup(fsdevice);
> throttle_config_to_limits(&cfg, tlimits);
> *fs9pcfg = fscfg;
> diff --git a/include/qemu/throttle-options.h b/include/qemu/throttle-options.h
> index 7134690..3eb1825 100644
> --- a/include/qemu/throttle-options.h
> +++ b/include/qemu/throttle-options.h
> @@ -111,6 +111,5 @@
> .type = QEMU_OPT_NUMBER,\
> .help = "when limiting by iops max size of an I/O in bytes",\
> }
> -
I'd rather keep this blank line for better readability.
> void throttle_parse_options(ThrottleConfig *, QemuOpts *);
> #endif
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2018-11-12 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A02D6AA901860840B46E751C5E9E38B42AFDB15F@DGGEML532-MBX.china.huawei.com>
2018-11-12 1:12 ` [Qemu-devel] [PATCH 2/2] virtio-9p: fix coding style issue xiezhide
2018-11-12 17:54 ` Greg Kurz [this message]
2018-11-13 10:24 ` xiezhide
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=20181112185459.55d27dc9@bahia.lan \
--to=groug@kaod.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiezhide@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;
as well as URLs for NNTP newsgroup(s).