From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Brian Woods <brian.woods@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v3] amd-iommu: remove page merging code
Date: Tue, 11 Dec 2018 11:30:53 +0000 [thread overview]
Message-ID: <8bfae8e05ce1420bbaf16996b190f3b6@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <5C0F9DEB0200007800205062@prv1-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 11 December 2018 11:22
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Brian Woods <brian.woods@amd.com>; Suravee Suthikulpanit
> <suravee.suthikulpanit@amd.com>; xen-devel <xen-
> devel@lists.xenproject.org>
> Subject: Re: [Xen-devel] [PATCH v3] amd-iommu: remove page merging code
>
> >>> On 11.12.18 at 12:00, <Paul.Durrant@citrix.com> wrote:
> > Ping? This has acks from Andy and Brian now, but has not been committed.
> Is
> > there anything holding it up?
>
> I keep overlooking it when checking what is ready to be committed,
> sorry.
>
Just wanted to make sure I didn't need to chase anyone else :-) I need this and the flush eliding to move on with PV-IOMMU.
Paul
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-12-11 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 9:55 [PATCH v3] amd-iommu: remove page merging code Paul Durrant
2018-11-28 10:41 ` Andrew Cooper
2018-12-03 10:27 ` Paul Durrant
2018-12-04 23:31 ` Woods, Brian
2018-12-05 8:50 ` Paul Durrant
2018-12-11 11:00 ` Paul Durrant
2018-12-11 11:22 ` Jan Beulich
2018-12-11 11:30 ` Paul Durrant [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=8bfae8e05ce1420bbaf16996b190f3b6@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.com \
--cc=brian.woods@amd.com \
--cc=suravee.suthikulpanit@amd.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).