From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"pdurrant@amazon.com" <pdurrant@amazon.com>,
"julien@xen.org" <julien@xen.org>,
"xadimgnik@gmail.com" <xadimgnik@gmail.com>,
"paul@xen.org" <paul@xen.org>
Subject: Re: [PATCH] xen/arm: optee: allow plain TMEM buffers with NULL address
Date: Thu, 18 Jun 2020 23:32:34 +0000 [thread overview]
Message-ID: <871rmc2bn2.fsf@epam.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2006181523070.14005@sstabellini-ThinkPad-T480s>
Hi Stefano,
Stefano Stabellini writes:
> Hi Paul, Julien, Volodymyr,
>
> This is another bug fix that I would like to get in 4.14. It doesn't
> look like we need any changes to this patch, assuming that it is
> accurate to the spec.
>
> It would be nice if Volodymyr could provide more info on the spec side,
> but honestly I trust his experience on this.
I'm sorry for the delay. Julien asks very good and deep questions and
it sometimes requires deep research, to fully and correctly answer to
them. This was exactly that case. I'll answer timely to the next e-mails.
--
Volodymyr Babchuk at EPAM
next prev parent reply other threads:[~2020-06-18 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 1:53 [PATCH] xen/arm: optee: allow plain TMEM buffers with NULL address Volodymyr Babchuk
2020-06-06 15:19 ` Julien Grall
2020-06-18 22:26 ` Stefano Stabellini
2020-06-18 23:32 ` Volodymyr Babchuk [this message]
2020-06-19 8:47 ` Paul Durrant
2020-06-18 23:29 ` Volodymyr Babchuk
2020-06-19 9:23 ` Julien Grall
2020-06-19 9:52 ` Volodymyr Babchuk
2020-06-19 10:25 ` Julien Grall
2020-06-19 17:15 ` Stefano Stabellini
2020-06-19 17:40 ` Julien Grall
2020-06-19 18:04 ` Stefano Stabellini
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=871rmc2bn2.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=julien@xen.org \
--cc=paul@xen.org \
--cc=pdurrant@amazon.com \
--cc=sstabellini@kernel.org \
--cc=xadimgnik@gmail.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 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.