[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a01e87c-9c03-ea72-4115-0cdeb064d1e3@oracle.com>
Date: Fri, 17 Dec 2021 14:23:02 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Oleksandr <olekstysh@...il.com>
Cc: Juergen Gross <jgross@...e.com>, xen-devel@...ts.xenproject.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Russell King <linux@...linux.org.uk>,
Julien Grall <julien@....org>,
Bertrand Marquis <bertrand.marquis@....com>,
Wei Chen <Wei.Chen@....com>, Henry Wang <Henry.Wang@....com>,
Kaly Xin <Kaly.Xin@....com>, Jiamei Xie <Jiamei.Xie@....com>
Subject: Re: [PATCH V4 0/6] xen: Add support of extended regions (safe ranges)
on Arm
On 12/17/21 2:19 PM, Oleksandr wrote:
>
> On 17.12.21 21:13, Boris Ostrovsky wrote:
>
> Hi Boris
>
>>
>> On 12/16/21 5:02 PM, Oleksandr wrote:
>>>
>>> On 09.12.21 22:05, Oleksandr Tyshchenko wrote:
>>>
>>>
>>> Hello Juergen, Boris
>>>
>>>
>>> May I please ask, are you happy (or otherwise) with current patch series (I assume, especially with commits #3-4)?
>>
>>
>> I think I mentioned last time, in patch 4:
>>
>>
>> + if (target_resource != &iomem_resource) {
>> + tmp_res = kzalloc(sizeof(*tmp_res), GFP_KERNEL);
>> + if (!res) {
>
> Yes, this is already fixed in V4 of patch [1]
So this email did escape. Yes, I realized I was looking at V3 but apparently didn't hit ^C quickly enough ;-)
-boris
Powered by blists - more mailing lists