From: Oleksandr <olekstysh@gmail.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: xen-devel@lists.xenproject.org,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Wei Liu" <wl@xen.org>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Juergen Gross" <jgross@suse.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo
Date: Tue, 12 Oct 2021 21:22:47 +0300 [thread overview]
Message-ID: <9e6e1378-7ee3-b692-b57d-29b597160661@gmail.com> (raw)
In-Reply-To: <24933.52939.127687.784369@mariner.uk.xensource.com>
On 12.10.21 21:07, Ian Jackson wrote:
Hi Ian
> Oleksandr writes ("Re: [PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo"):
>> Please note, it is going to be a new version of this patch based on
>> today's discussion with Jan.
> OK. Please retain my R-b if you don't change any of the tools parts.
Sure, thanks for confirming. There won't be no new changes for the tools.
>
> Ian.
--
Regards,
Oleksandr Tyshchenko
next prev parent reply other threads:[~2021-10-12 18:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 17:48 [PATCH V6 0/2] Add handling of extended regions (safe ranges) on Arm (Was "xen/memory: Introduce a hypercall to provide unallocated space") Oleksandr Tyshchenko
2021-10-11 17:48 ` [PATCH V6 1/2] xen/arm: Introduce gpaddr_bits field to struct xen_domctl_getdomaininfo Oleksandr Tyshchenko
2021-10-11 20:01 ` Stefano Stabellini
2021-10-12 9:24 ` Jan Beulich
2021-10-12 11:28 ` Oleksandr
2021-10-12 11:49 ` Jan Beulich
2021-10-12 13:18 ` Oleksandr
2021-10-12 13:26 ` Jan Beulich
2021-10-12 15:15 ` Ian Jackson
2021-10-12 15:48 ` Oleksandr
2021-10-12 16:18 ` Ian Jackson
2021-10-12 17:57 ` Oleksandr
2021-10-12 18:07 ` Ian Jackson
2021-10-12 18:22 ` Oleksandr [this message]
2021-10-12 21:22 ` Oleksandr Tyshchenko
2021-10-13 13:50 ` Oleksandr
2021-10-13 13:56 ` Jan Beulich
2021-10-13 15:05 ` Oleksandr
2021-10-13 15:17 ` Julien Grall
2021-10-13 15:24 ` Oleksandr
2021-10-11 17:48 ` [PATCH V6 2/2] libxl/arm: Add handling of extended regions for DomU Oleksandr Tyshchenko
2021-10-11 20:00 ` Stefano Stabellini
2021-10-12 15:11 ` Ian Jackson
2021-10-12 15:22 ` Oleksandr
2021-10-12 15:32 ` Ian Jackson
2021-10-12 15:38 ` Oleksandr
2021-10-12 16:05 ` Julien Grall
2021-10-12 17:42 ` Oleksandr
2021-10-12 21:22 ` Julien Grall
2021-10-12 21:43 ` Oleksandr
2021-10-13 13:46 ` Oleksandr
2021-10-13 15:15 ` Julien Grall
2021-10-13 15:49 ` Oleksandr
2021-10-13 16:24 ` Julien Grall
2021-10-13 16:44 ` Oleksandr
2021-10-13 17:07 ` Julien Grall
2021-10-13 18:26 ` Oleksandr
2021-10-13 20:19 ` Oleksandr
2021-10-13 20:24 ` Stefano Stabellini
2021-10-14 11:44 ` Oleksandr
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=9e6e1378-7ee3-b692-b57d-29b597160661@gmail.com \
--to=olekstysh@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.