From: Gonglei <arei.gonglei@huawei.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] 9pfs-proxy: tiny cleanups in proxy_pwritev and proxy_preadv
Date: Tue, 10 Mar 2015 15:27:40 +0800 [thread overview]
Message-ID: <54FE9CEC.9060704@huawei.com> (raw)
In-Reply-To: <54FE9B50.3040504@msgid.tls.msk.ru>
On 2015/3/10 15:20, Michael Tokarev wrote:
> 10.03.2015 10:15, Gonglei wrote:
>> On 2015/3/10 13:54, Michael Tokarev wrote:
>>> Don't compare syscall return with -1, use "<0" condition.
>>> Don't introduce useless local variables when we already
>>> have similar variable
>>> Rename local variable to be consistent with other usages
>>>
>>> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
>>> ---
>>> hw/9pfs/virtio-9p-proxy.c | 12 +++++-------
>>> 1 file changed, 5 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/hw/9pfs/virtio-9p-proxy.c b/hw/9pfs/virtio-9p-proxy.c
>>> index 59c7445..a01804a 100644
>>> --- a/hw/9pfs/virtio-9p-proxy.c
>>> +++ b/hw/9pfs/virtio-9p-proxy.c
>>> @@ -696,9 +696,9 @@ static ssize_t proxy_preadv(FsContext *ctx, V9fsFidOpenState *fs,
>>> #ifdef CONFIG_PREADV
>>> return preadv(fs->fd, iov, iovcnt, offset);
>>> #else
>>> - int err = lseek(fs->fd, offset, SEEK_SET);
>>> - if (err == -1) {
>>> - return err;
>>> + int ret = lseek(fs->fd, offset, SEEK_SET);
>>> + if (err < 0)
>>> + return ret;
>>
>> The above code fragment is confused.
>
> Sorry I don't understand, can you elaborate please?
> Note I haven't changed much in there, just variable
> rename and changed the condition within if: s/== -1/< 0/.
>
You use 'ret' instead of 'err', but remain using 'if (err < 0)',
and missing '{' at the end of if statement.
hw/9pfs/virtio-9p-proxy.c: In function ‘proxy_preadv’:
hw/9pfs/virtio-9p-proxy.c:700: error: ‘err’ undeclared (first use in this function)
hw/9pfs/virtio-9p-proxy.c:700: error: (Each undeclared identifier is reported only once
hw/9pfs/virtio-9p-proxy.c:700: error: for each function it appears in.)
hw/9pfs/virtio-9p-proxy.c:702: warning: control reaches end of non-void function
hw/9pfs/virtio-9p-proxy.c: At top level:
hw/9pfs/virtio-9p-proxy.c:702: error: expected identifier or ‘(’ before ‘else’
hw/9pfs/virtio-9p-proxy.c:706: error: expected identifier or ‘(’ before ‘}’ token
make: *** [hw/9pfs/virtio-9p-proxy.o] Error 1
Regards,
-Gonglei
> (BTW, a code fragment can't be confused, it might be
> confusing I think, with a reader being confused.
> A confused code is um.. something -- a code who doesn't
> know what to do... ;) Sorry can't resist ;)
>
> Thanks,
>
> /mjt
>
next prev parent reply other threads:[~2015-03-10 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 5:54 [Qemu-devel] [PATCH] 9pfs-proxy: tiny cleanups in proxy_pwritev and proxy_preadv Michael Tokarev
2015-03-10 7:15 ` Gonglei
2015-03-10 7:20 ` Michael Tokarev
2015-03-10 7:27 ` Gonglei [this message]
2015-03-10 17:23 ` Aneesh Kumar K.V
2015-03-12 6:30 ` Michael Tokarev
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=54FE9CEC.9060704@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).