From: 소병철 <byungchul.so@samsung.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Question about xen event channel
Date: Mon, 11 Jul 2016 03:58:49 +0000 [thread overview]
Message-ID: <20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4> (raw)
In-Reply-To: CGME20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4
[-- Attachment #1.1: Type: text/html, Size: 3833 bytes --]
[-- Attachment #1.2: 201602111742151_N3WZA6X7.png --]
[-- Type: image/png, Size: 33527 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2016-07-11 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4>
2016-07-11 3:58 ` 소병철 [this message]
2016-07-11 9:26 ` Question about xen event channel David Vrabel
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=20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4 \
--to=byungchul.so@samsung.com \
--cc=xen-devel@lists.xen.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).