From: Amos Kong <akong@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ui/input: strictly check console in finding input handler
Date: Thu, 6 Nov 2014 14:37:54 +0800 [thread overview]
Message-ID: <20141106063754.GF8764@air.redhat.com> (raw)
In-Reply-To: <1415177267.11011.1.camel@nilsson.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Wed, Nov 05, 2014 at 09:47:47AM +0100, Gerd Hoffmann wrote:
> On Mi, 2014-11-05 at 00:49 +0800, Amos Kong wrote:
> > qemu_input_find_handler() prefers a handler associated with con.
> > But if none exists, it takes any. This patch added a parameter
> > to strictly check console, in case we want to input event to
> > special console.
If console is assigned, it will try to find right handler by first
loop in qemu_input_find_handler(). The second loop is used to find
mask matched handler if console isn't assigned.
If we assigned console and didn't find handler in first loop, it
skip second loop body by 'continue', and return NULL.
It seems my concern is wrong, we don't need this repeated parameter.
NACK this patch.
Thanks.
> > 'input-send-event' has a parameter to assign special console,
> > so we should enable strict checking in finding handler.
>
> I don't think we want do that by default. It only matters in case of a
> multiseat setup where you actually have multiple input devices of the
> same kind. Which isn't a very typical use case.
>
> Options I see are:
>
> (a) Turn console into an optional parameter, do strict checking in
> case it is present.
> (b) Add a optional 'strict' parameter.
--
Amos.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-06 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:49 [Qemu-devel] [PATCH] ui/input: strictly check console in finding input handler Amos Kong
2014-11-05 8:47 ` Gerd Hoffmann
2014-11-06 6:37 ` Amos Kong [this message]
2014-11-06 15:01 ` Amos Kong
2014-11-07 4:16 ` Amos Kong
2014-11-06 9:00 ` Markus Armbruster
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=20141106063754.GF8764@air.redhat.com \
--to=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=mtosatti@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 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).