From: "Paraschiv, Andra-Irina" <andraprs@amazon.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alexandru Ciobotaru <alcioa@amazon.com>,
Greg KH <gregkh@linuxfoundation.org>,
Kamal Mostafa <kamal@canonical.com>,
Alexandru Vasile <lexnv@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
kvm <kvm@vger.kernel.org>,
ne-devel-upstream <ne-devel-upstream@amazon.com>
Subject: Re: [PATCH v3 2/7] nitro_enclaves: Update documentation for Arm64 support
Date: Tue, 31 Aug 2021 14:28:44 +0300 [thread overview]
Message-ID: <2c167a8a-3d5c-4f42-410c-294d357d85bb@amazon.com> (raw)
In-Reply-To: <20210831074341.e74quljmvp36gy5a@steredhat>
On 31/08/2021 10:43, Stefano Garzarella wrote:
> On Fri, Aug 27, 2021 at 06:49:25PM +0300, Andra Paraschiv wrote:
>> Add references for hugepages and booting steps for Arm64.
>>
>> Include info about the current supported architectures for the
>> NE kernel driver.
>>
>> Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
>> ---
>> Changelog
>>
>> v1 -> v2
>>
>> * Add information about supported architectures for the NE kernel
>> driver.
>>
>> v2 -> v3
>>
>> * Move changelog after the "---" line.
>> ---
>> Documentation/virt/ne_overview.rst | 21 +++++++++++++--------
>> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> Acked-by: Stefano Garzarella <sgarzare@redhat.com>
>
Thank you, Stefano.
Andra
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
next prev parent reply other threads:[~2021-08-31 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 15:49 [PATCH v3 0/7] nitro_enclaves: Add support for Arm64 Andra Paraschiv
2021-08-27 15:49 ` [PATCH v3 1/7] nitro_enclaves: Enable Arm64 support Andra Paraschiv
2021-08-30 15:59 ` George-Aurelian Popescu
2021-08-30 18:30 ` Paraschiv, Andra-Irina
2021-08-31 6:43 ` Greg KH
2021-08-31 7:51 ` Paraschiv, Andra-Irina
2021-11-04 19:03 ` Paraschiv, Andra-Irina
2021-08-27 15:49 ` [PATCH v3 2/7] nitro_enclaves: Update documentation for " Andra Paraschiv
2021-08-30 15:56 ` George-Aurelian Popescu
2021-08-31 7:43 ` Stefano Garzarella
2021-08-31 11:28 ` Paraschiv, Andra-Irina [this message]
2021-08-27 15:49 ` [PATCH v3 3/7] nitro_enclaves: Add fix for the kernel-doc report Andra Paraschiv
2021-08-30 15:53 ` George-Aurelian Popescu
2021-08-27 15:49 ` [PATCH v3 4/7] nitro_enclaves: Update copyright statement to include 2021 Andra Paraschiv
2021-08-30 15:49 ` George-Aurelian Popescu
2021-08-27 15:49 ` [PATCH v3 5/7] nitro_enclaves: Add fixes for checkpatch match open parenthesis reports Andra Paraschiv
2021-08-30 15:48 ` George-Aurelian Popescu
2021-08-27 15:49 ` [PATCH v3 6/7] nitro_enclaves: Add fixes for checkpatch spell check reports Andra Paraschiv
2021-08-30 15:46 ` George-Aurelian Popescu
2021-08-27 15:49 ` [PATCH v3 7/7] nitro_enclaves: Add fixes for checkpatch blank line reports Andra Paraschiv
2021-08-30 15:45 ` George-Aurelian Popescu
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=2c167a8a-3d5c-4f42-410c-294d357d85bb@amazon.com \
--to=andraprs@amazon.com \
--cc=alcioa@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamal@canonical.com \
--cc=kvm@vger.kernel.org \
--cc=lexnv@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ne-devel-upstream@amazon.com \
--cc=pbonzini@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=vkuznets@redhat.com \
/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