From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bastian Blank <waldi@debian.org>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] xen: Add privcmd device driver
Date: Wed, 14 Dec 2011 13:54:36 -0500 [thread overview]
Message-ID: <20111214185436.GA24598@phenom.dumpdata.com> (raw)
In-Reply-To: <1323541791-18006-2-git-send-email-waldi@debian.org>
On Sat, Dec 10, 2011 at 07:29:46PM +0100, Bastian Blank wrote:
> Access to arbitrary hypercalls is currently provided via xenfs. This
> adds a standard character device to handle this. The support in xenfs
> remains for backward compatibility and uses the device driver code.
Bastian Blank (5):
xen: Add privcmd device driver
xen: Add xenbus device driver
xen: Add xenbus_backend device
xen/privcmd: Remove unused support for arch specific privcmp mmap
xen/xenbus-frontend: Make error message more clear
Will wait for the re-worked sixth patch from you.
next prev parent reply other threads:[~2011-12-14 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 18:29 [PATCH 0/6] V3, Move stuff out of xenfs Bastian Blank
2011-12-10 18:29 ` [PATCH 1/6] xen: Add privcmd device driver Bastian Blank
2011-12-14 18:54 ` Konrad Rzeszutek Wilk [this message]
2011-12-10 18:29 ` [PATCH 2/6] xen: Add xenbus " Bastian Blank
2011-12-10 18:29 ` [PATCH 3/6] xen: Add xenbus_backend device Bastian Blank
2011-12-10 18:29 ` [PATCH 4/6] xen/privcmd: Remove unused support for arch specific privcmp mmap Bastian Blank
2011-12-10 18:29 ` [PATCH 5/6] xen/xenbus-frontend: Make error message more clear Bastian Blank
2011-12-12 9:25 ` [Xen-devel] " Ian Campbell
2011-12-10 18:29 ` [PATCH 6/6] xen/xenbus-backend: Only register device if communication ring is local Bastian Blank
2011-12-12 9:30 ` [Xen-devel] " Ian Campbell
2011-12-12 15:42 ` Konrad Rzeszutek Wilk
2011-12-12 18:28 ` [Xen-devel] " Bastian Blank
2011-12-14 19:22 ` Konrad Rzeszutek Wilk
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=20111214185436.GA24598@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=waldi@debian.org \
--cc=xen-devel@lists.xensource.com \
/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
Powered by JetHome