public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chao Li" <lichao@loongson.cn>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Zhiguang Liu <zhiguang.liu@intel.com>,
	Eric Dong <eric.dong@intel.com>, Ray Ni <ray.ni@intel.com>,
	Rahul Kumar <rahul1.kumar@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Abner Chang <abner.chang@amd.com>,
	Daniel Schaefer <git@danielschaefer.me>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Andrei Warkentin <andrei.warkentin@intel.com>,
	Sunil V L <sunilvl@ventanamicro.com>,
	Bibo Mao <maobibo@loongson.cn>
Subject: Re: [edk2-devel] [PATCH v8 00/37] Enable LoongArch virtual machine in edk2
Date: Fri, 2 Feb 2024 10:50:08 +0800	[thread overview]
Message-ID: <0f5ce19f-5ab2-474f-9671-b34034ae691a@loongson.cn> (raw)
In-Reply-To: <371b242d-32e1-f088-6290-644fbdd6de17@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

OK, the new series has been submitted, it is starting from v1.


Thanks,
Chao
On 2024/2/2 06:23, Laszlo Ersek wrote:
> On 2/1/24 09:30, Chao Li wrote:
>> Hi Liming, Mike, Ray, Laszlo, Ard, Gerd Leif and Sunil,
>>
>> Since there are some mixed voices regarding patches for UefiCpuPkg, and
>> the stable202402 feature deadline is approaching, so may I suggest that
>> splitting this series into two or more smaller series, and having
>> patches of don't depend on UefiCpuPkg merged into stable202402 first,
>> involving patches 1-10, 17- 25, other patches still need to be reviewed
>> and merged to master later. So what do you suggest?
> This sounds good to me.
>
> I think you should submit a new series that contains only the patches
> that you mention above, also picking up any new review tags you've
> received for v8. This will provide maintainers with a good overview.
> (And this will be needed anyway for the actual PR.)
>
> I think the only missing R-b has been for "[PATCH v8 20/37] ArmVirtPkg:
> Enable CpuMmio2Dxe", but I have reviewed that patch now. So I believe
> further patch-level reviews shouldn't be necessary, only an overview of
> those selected patches organized into a dedicated series.
>
> Regards,
> Laszlo


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115006): https://edk2.groups.io/g/devel/message/115006
Mute This Topic: https://groups.io/mt/103971622/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 2838 bytes --]

  reply	other threads:[~2024-02-02  2:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17ADD1C0483F8D84.24595@groups.io>
2024-01-26  6:43 ` [edk2-devel] [PATCH v8 00/37] Enable LoongArch virtual machine in edk2 Chao Li
     [not found] ` <17ADD29C1061FE55.11113@groups.io>
2024-02-01  8:30   ` Chao Li
2024-02-01 22:23     ` Laszlo Ersek
2024-02-02  2:50       ` Chao Li [this message]
2024-02-02  3:36     ` Ni, Ray
2024-02-02 14:10       ` Laszlo Ersek
2024-01-26  6:27 Chao Li

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=0f5ce19f-5ab2-474f-9671-b34034ae691a@loongson.cn \
    --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