From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] char: Send out OPENED events only on char dev open; not on qemu initial reset
Date: Wed, 7 Oct 2009 16:40:37 +0530 [thread overview]
Message-ID: <1254913840-10358-1-git-send-email-amit.shah@redhat.com> (raw)
Hello,
These patches rename the CHR_EVENT_RESET event to CHR_EVENT_OPENED,
which is what it really is.
The check for initial_reset_issued was not really necessary, so that has
been done away with.
Finally, this event is now only sent when a char dev is opened instead
of the current behaviour of also sending it when qemu does its early
init of char state. The consumers of the event shouldn't be interested
in this anyway.
I've tested this with the monitor.
next reply other threads:[~2009-10-07 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 11:10 Amit Shah [this message]
2009-10-07 11:10 ` [Qemu-devel] [PATCH 1/3] char: check for initial_reset_issued unnecessary Amit Shah
2009-10-07 11:10 ` [Qemu-devel] [PATCH 2/3] char: rename CHR_EVENT_RESET to CHR_EVENT_OPENED Amit Shah
2009-10-07 11:10 ` [Qemu-devel] [PATCH 3/3] char: emit the OPENED event only when a new char connection is opened Amit Shah
2009-10-07 12:15 ` [Qemu-devel] Re: [PATCH 1/3] char: check for initial_reset_issued unnecessary Amit Shah
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=1254913840-10358-1-git-send-email-amit.shah@redhat.com \
--to=amit.shah@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).