From: Gerd Hoffmann <kraxel@redhat.com>
To: Pierre Ossman <ossman@cendio.se>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc: track LED state separately
Date: Wed, 04 Jan 2017 09:57:19 +0100 [thread overview]
Message-ID: <1483520239.5670.47.camel@redhat.com> (raw)
In-Reply-To: <9ef03a73-2139-e586-7c2d-c234863bdcac@cendio.se>
On Fr, 2016-12-16 at 10:00 +0100, Pierre Ossman wrote:
> On 15/12/16 17:41, Gerd Hoffmann wrote:
> >>
> >> - caps = ledstate & QEMU_CAPS_LOCK_LED ? 1 : 0;
> >> - num = ledstate & QEMU_NUM_LOCK_LED ? 1 : 0;
> >> - scr = ledstate & QEMU_SCROLL_LOCK_LED ? 1 : 0;
> >> + if (ledstate != vd->ledstate)
> >> + return;
> >
> > Hmm? Shouldn't that be (ledstate == vd->ledstate)?
> >
>
> Right, sorry. Brain fart. :)
/me wonders how you've tested the patch ...
> Can you fix that up before commit or do you want a new patch?
Tried, but checkpatch found some more issues:
=== checkpatch complains ===
ERROR: braces {} are necessary for all arms of this statement
#71: FILE: ui/vnc.c:1691:
+ if (ledstate != vd->ledstate)
[...]
ERROR: braces {} are necessary for all arms of this statement
#106: FILE: ui/vnc.c:3159:
+ if (vd->lock_key_sync)
[...]
ERROR: braces {} are necessary for all arms of this statement
#115: FILE: ui/vnc.c:3728:
+ if (lock_key_sync)
[...]
total: 3 errors, 0 warnings, 125 lines checked
Please fix and resend.
thanks,
Gerd
>
> Regards
next prev parent reply other threads:[~2017-01-04 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 13:16 [Qemu-devel] [PATCH] vnc: track LED state separately Pierre Ossman
2016-12-15 16:41 ` Gerd Hoffmann
2016-12-16 9:00 ` Pierre Ossman
2017-01-04 8:57 ` Gerd Hoffmann [this message]
2017-01-09 16:14 ` Pierre Ossman
-- strict thread matches above, loose matches on Subject: below --
2017-01-09 16:14 Pierre Ossman
2017-01-10 11:40 ` Gerd Hoffmann
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=1483520239.5670.47.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ossman@cendio.se \
--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 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).