From: "Laszlo Ersek" <lersek@redhat.com>
To: Sami Mujawar <sami.mujawar@arm.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 1/4] ArmVirtPkg: Library: Memory initialization for Cloud Hypervisor
Date: Tue, 4 May 2021 20:03:47 +0200 [thread overview]
Message-ID: <c90d5a4d-b2e5-3ab4-adb3-a96dabe9a9fe@redhat.com> (raw)
In-Reply-To: <9843.1620117114951660496@groups.io>
On 05/04/21 10:31, Sami Mujawar wrote:
> Hi Laszlo,
>
> On Thu, Apr 22, 2021 at 06:56 AM, Laszlo Ersek wrote:
>
>>
>> 5) "Cloud Hypervisor" is not something that I can justifiably spend
>> much time on. I'm willing to review this series at the level at which
>> I've reviewed (for example) XenPVH or Bhyve in the past, mainly focusing
>> on style and potential regressions. However, that's not enough for the
>> long term: someone from ARM (or elsewhere) will have to step up for
>> permanent reviewership. Please add a patch for extending
>> "Maintainers.txt" appropriately. Example subsystems:
>
> I can help to review the 'Cloud Hypervisor' patches and will send out a patch to update the reviewership once the initial series is merged.
OK, thanks!
>
> Hi Jainyong,
>
> I could not find the remaining patches from your v1 series. Can you forward them to me, please?
Indeed, the v1 patches have not reached the list.
Thanks,
Laszlo
>
> I can review and provide feedback so that they are addressed in your v2 series.
>
> Regards,
>
> Sami Mujawar
>
prev parent reply other threads:[~2021-05-04 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210422082440.172160-1-jianyong.wu@arm.com>
[not found] ` <20210422082440.172160-2-jianyong.wu@arm.com>
2021-04-22 13:56 ` [PATCH v1 1/4] ArmVirtPkg: Library: Memory initialization for Cloud Hypervisor Laszlo Ersek
2021-04-22 14:13 ` Sami Mujawar
2021-04-26 8:33 ` jianyong.wu
2021-04-23 12:00 ` [edk2-devel] " Laszlo Ersek
2021-04-26 10:29 ` Jianyong Wu
2021-04-26 8:43 ` Jianyong Wu
2021-05-04 8:31 ` [edk2-devel] " Sami Mujawar
2021-05-04 18:03 ` Laszlo Ersek [this message]
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-list 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=c90d5a4d-b2e5-3ab4-adb3-a96dabe9a9fe@redhat.com \
--to=devel@edk2.groups.io \
/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