From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 0/2] x86/io: rename dpci_ IO port handlers
Date: Tue, 28 Mar 2017 21:51:57 +0100 [thread overview]
Message-ID: <0ac1ce4b-2e04-7c48-b496-bde4ea5109d8@citrix.com> (raw)
In-Reply-To: <20170328131226.13347-1-roger.pau@citrix.com>
On 28/03/2017 14:12, Roger Pau Monne wrote:
> Hello,
>
> The following series contain two cosmetic fixes for the g2m IO port handlers.
> The first one renames them to use the g2m_ prefix instead of the dpci_ one,
> since those handlers are not trapping the PCI config space in any way. The
> second fix moves the list of ports from the domain_iommu struct to the
> hvm_struct, where it fits more naturally.
Both Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>, although it
would be good to take the opportunity to s/bool_t/bool/ while committing.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-28 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 13:12 [PATCH v2 0/2] x86/io: rename dpci_ IO port handlers Roger Pau Monne
2017-03-28 13:12 ` [PATCH v2 1/2] x86/io: rename misleading dpci_ prefixed functions to g2m_ Roger Pau Monne
2017-03-28 15:56 ` Paul Durrant
2017-03-28 13:12 ` [PATCH v2 2/2] x86/io: move the list of guest to machine IO ports out of domain_iommu Roger Pau Monne
2017-03-28 15:58 ` Paul Durrant
2017-03-29 10:41 ` Andrew Cooper
2017-03-29 10:49 ` Roger Pau Monne
2017-04-04 11:06 ` Roger Pau Monne
2017-04-04 11:31 ` Jan Beulich
2017-04-04 13:23 ` Andrew Cooper
2017-04-04 13:39 ` Jan Beulich
2017-04-04 13:44 ` Roger Pau Monne
2017-03-28 20:51 ` Andrew Cooper [this message]
2017-03-29 7:14 ` [PATCH v2 0/2] x86/io: rename dpci_ IO port handlers Roger Pau Monne
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=0ac1ce4b-2e04-7c48-b496-bde4ea5109d8@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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).