From: Andrii Anisov <andrii.anisov@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii_anisov@epam.com>
Subject: [PATCH 0/2] Dangling fixes for ARM iommu
Date: Mon, 21 Jan 2019 19:04:05 +0200 [thread overview]
Message-ID: <1548090247-20078-1-git-send-email-andrii.anisov@gmail.com> (raw)
From: Andrii Anisov <andrii_anisov@epam.com>
Dear All,
With moving our working setup to 4.12-rc2 (IPMMU series especially),I've
realized that we have a couple of patches from IPMMU series [1] which are
fixes, got RB/AB, but not reached mainline yet. I really hope those RB/AB
would not be treated as stale, and patches are OK to go into 4.12 release.
Oleksandr Tyshchenko (2):
iommu/arm: Misc fixes for arch specific part
RB from Julien is here [2]
xen/arm: domain_build: Don't expose IOMMU specific properties to the
guest
AB from Julien is here [3]
[1] https://lists.xen.org/archives/html/xen-devel/2017-07/msg02545.html
[2] https://patchwork.kernel.org/patch/9862567/
[3] https://patchwork.kernel.org/patch/9862565/
xen/arch/arm/domain_build.c | 10 ++++++++++
xen/drivers/passthrough/arm/iommu.c | 7 +++++--
2 files changed, 15 insertions(+), 2 deletions(-)
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-01-21 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 17:04 Andrii Anisov [this message]
2019-01-21 17:04 ` [PATCH 1/2] iommu/arm: Misc fixes for arch specific part Andrii Anisov
2019-01-21 17:04 ` [PATCH 2/2] xen/arm: domain_build: Don't expose IOMMU specific properties to the guest Andrii Anisov
2019-10-01 15:04 ` [Xen-devel] " Julien Grall
2019-10-01 15:25 ` Oleksandr
2019-10-01 15:36 ` Julien Grall
2019-10-01 16:07 ` Oleksandr
2019-10-01 19:07 ` Julien Grall
2019-10-03 12:18 ` Oleksandr
2019-10-07 21:02 ` Julien Grall
2019-10-08 15:34 ` Oleksandr
2019-01-21 17:29 ` [PATCH 0/2] Dangling fixes for ARM iommu Julien Grall
2019-01-22 13:48 ` Andrii Anisov
2019-01-22 14:31 ` Julien Grall
2019-01-23 17:53 ` Andrii Anisov
2019-01-23 18:14 ` Julien Grall
2019-01-23 18:29 ` Andrii Anisov
2019-01-23 18:34 ` Julien Grall
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=1548090247-20078-1-git-send-email-andrii.anisov@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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).