From: Osier Yang <jyang@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: penberg@cs.helsinki.fi, kvm@vger.kernel.org, mingo@elte.hu,
asias.hejun@gmail.com, gorcunov@gmail.com
Subject: Re: [PATCH] kvm tools: Fix SDL exit on window close
Date: Wed, 26 Oct 2011 12:04:46 +0800 [thread overview]
Message-ID: <4EA786DE.1040208@redhat.com> (raw)
In-Reply-To: <1319543207-4950-1-git-send-email-levinsasha928@gmail.com>
于 2011年10月25日 19:46, Sasha Levin 写道:
> We've changed IPC to use sockets instead of signals, but the process of
> closing the SDL window was still trigerring an exit signal causing
> an ugly message and not cleaning up after itself.
>
> This patch switches that to use the proper method of cleaning up.
The patch works, thanks.
Osier
prev parent reply other threads:[~2011-10-26 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 11:46 [PATCH] kvm tools: Fix SDL exit on window close Sasha Levin
2011-10-26 4:04 ` Osier Yang [this message]
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=4EA786DE.1040208@redhat.com \
--to=jyang@redhat.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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).