From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Julien Grall <julien@xen.org>
Cc: "tee-dev@lists.linaro.org" <tee-dev@lists.linaro.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] optee: immediately free buffers that are released by OP-TEE
Date: Fri, 19 Jun 2020 09:01:33 +0000 [thread overview]
Message-ID: <87sger1lar.fsf@epam.com> (raw)
In-Reply-To: <57e24ddd-5ba1-eea9-2961-d7dc9ce22688@xen.org>
Julien, Paul,
Julien Grall writes:
> On 18/06/2020 23:20, Stefano Stabellini wrote:
>> Hi Paul, Julien,
>>
>> Volodymyr hasn't come back with an update to this patch, but I think it
>> is good enough as-is as a bug fix and I would rather have it in its
>> current form in 4.14 than not having it at all leaving the bug unfixed.
>>
>> I think Julien agrees.
>
> The approach is okayish but this is not ideal at least without any
> explanation why ignoring a potential bug is fine. I could settle with
> an expanded commit message for now.
>
> Therefore, I don't feel I should provide my Ack on this approach. That
> said, I am not the maintainers of this code. You are free to Ack and
> commit it.
Sorry for the delay. I'll provide v2 later today.
--
Volodymyr Babchuk at EPAM
next prev parent reply other threads:[~2020-06-19 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 1:44 [PATCH] optee: immediately free buffers that are released by OP-TEE Volodymyr Babchuk
2020-05-11 9:34 ` Julien Grall
2020-05-11 10:10 ` Andrew Cooper
2020-05-11 10:26 ` Julien Grall
2020-05-11 22:37 ` Stefano Stabellini
2020-06-18 22:20 ` Stefano Stabellini
2020-06-18 22:21 ` Stefano Stabellini
2020-06-19 8:40 ` Paul Durrant
2020-06-19 8:53 ` Julien Grall
2020-06-19 9:01 ` Volodymyr Babchuk [this message]
2020-05-18 2:04 ` Volodymyr Babchuk
2020-05-18 8:33 ` 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=87sger1lar.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=tee-dev@lists.linaro.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 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.