From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>
Cc: Mukesh Rathor <mukesh.rathor@oracle.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 3/4] gdbsx: prefer privcmd character device
Date: Wed, 25 Nov 2015 11:13:02 +0000 [thread overview]
Message-ID: <1448449982.17688.70.camel@citrix.com> (raw)
In-Reply-To: <22100.45608.914912.205420@mariner.uk.xensource.com>
On Tue, 2015-11-24 at 18:53 +0000, Ian Jackson wrote:
> Doug Goldstein writes ("[PATCH 3/4] gdbsx: prefer privcmd character
> device"):
> > Prefer using the character device over the proc file if the character
> > device exists.
>
> I think this common logic (which also appears in your 1/4 patch)
> should be factored out.
>
For reasons I don't really understand gdbsc appears to avoid the use of
libxenctrl completely and has it's own h/call wrapper and such.
(Perhaps a legacy of it being out of tree?)
next prev parent reply other threads:[~2015-11-25 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:47 [PATCH 1/4] libxc: prefer using privcmd character device Doug Goldstein
2015-11-24 18:47 ` [PATCH 2/4] update outdated header comment on privcmd.h Doug Goldstein
2015-11-24 18:52 ` Ian Jackson
2015-11-24 18:47 ` [PATCH 3/4] gdbsx: prefer privcmd character device Doug Goldstein
2015-11-24 18:53 ` Ian Jackson
2015-11-24 19:19 ` Doug Goldstein
2015-11-24 20:11 ` Doug Goldstein
2015-11-25 11:14 ` Ian Jackson
2015-11-25 11:13 ` Ian Campbell [this message]
2015-11-24 18:47 ` [PATCH 4/4] xendomains initscript: test for privcmd char device Doug Goldstein
2015-11-24 18:53 ` Ian Jackson
2015-11-24 18:52 ` [PATCH 1/4] libxc: prefer using privcmd character device Ian Jackson
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=1448449982.17688.70.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cardoe@cardoe.com \
--cc=mukesh.rathor@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.