From: Roman Skakun <rm.skakun@gmail.com>
To: Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org,
Roman Skakun <roman_skakun@epam.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Andrii Anisov <andrii_anisov@epam.com>,
Roman Skakun <rm.skakun@gmail.com>
Subject: Re: [RFC 0/1] tag IOMMU-protected devices in Dom0 fdt
Date: Tue, 12 Oct 2021 17:23:08 +0300 [thread overview]
Message-ID: <CADu_u-OE2ZoB6vPDwayRyBV+03szTx7Ah84GWLeQeSEGvCbjpQ@mail.gmail.com> (raw)
In-Reply-To: <243d4615-fb29-6be0-eef9-c892cb56f8bc@xen.org>
Understood.
Thank you!
вт, 12 окт. 2021 г. в 17:20, Julien Grall <julien@xen.org>:
>
>
>
> On 12/10/2021 15:11, Roman Skakun wrote:
> > Hi,
>
> Hi Roman,
>
> > Would you be so kind to look at my patches, it would help me to
> > know exactly whether I'm moving correctly and whether I've chosen
> > the right path?
>
> This is in my queue to review. At the moment, I am prioritizing work
> targeting 4.16. Unfortunately, this RFC was posted after the last
> posting date. So I will review it after the feature freeze.
>
> Best regards,
>
> --
> Julien Grall
--
Best Regards, Roman.
prev parent reply other threads:[~2021-10-12 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 9:54 [RFC 0/1] tag IOMMU-protected devices in Dom0 fdt Roman Skakun
2021-10-04 9:54 ` [RFC 1/1] xen/arm: set iommu property for IOMMU-protected devices Roman Skakun
2021-10-06 12:45 ` Oleksandr
2021-10-07 11:04 ` Roman Skakun
2021-11-08 18:30 ` Julien Grall
2021-11-10 21:12 ` Stefano Stabellini
2021-12-07 15:40 ` Sergiy Kibrik
2021-12-10 2:04 ` Stefano Stabellini
2021-10-04 9:54 ` [RFC PATCH] dma-mapping: don't set swiotlb-xen fops " Roman Skakun
2021-10-12 14:11 ` [RFC 0/1] tag IOMMU-protected devices in Dom0 fdt Roman Skakun
2021-10-12 14:20 ` Julien Grall
2021-10-12 14:23 ` Roman Skakun [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=CADu_u-OE2ZoB6vPDwayRyBV+03szTx7Ah84GWLeQeSEGvCbjpQ@mail.gmail.com \
--to=rm.skakun@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrii_anisov@epam.com \
--cc=julien@xen.org \
--cc=roman_skakun@epam.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).