public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ankur Arora" <ankur.a.arora@oracle.com>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: imammedo@redhat.com, boris.ostrovsky@oracle.com,
	Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Aaron Young <aaron.young@oracle.com>
Subject: Re: [PATCH v5 1/9] OvmfPkg/CpuHotplugSmm: refactor hotplug logic
Date: Tue, 26 Jan 2021 14:53:03 -0800	[thread overview]
Message-ID: <b64b73a7-56d2-4064-c257-193ae1ef7652@oracle.com> (raw)
In-Reply-To: <0bcaba31-2e44-f228-1ab6-396194c3b77f@redhat.com>

On 2021-01-26 1:32 p.m., Laszlo Ersek wrote:
> On 01/26/21 22:17, Ankur Arora wrote:
>> On 2021-01-26 1:07 p.m., Laszlo Ersek wrote:
>>> On 01/26/21 20:15, Ankur Arora wrote:
>>>> On 2021-01-26 11:01 a.m., Laszlo Ersek wrote:
>>>
>>>>> I'll continue the review later this week.
>>>>
>>>> Acking the comments above.
>>>
>>> Thank you!
>>>
>>>> Meanwhile let me reprocess the series in light of the comments above.
>>>
>>> I'm at such a point now, during the v5 review, that I think I can easily
>>> re-sync.
>>>
>>> In general, I don't mind the posting of a new version of a series
>>> mid-review, *IF* we agree about it in advance.
>>>
>>> If you prefer to post a v6, for addressing the comments I've made thus
>>> far, I'm OK with that. If you'd like me to continue reviewing v5, I'm
>>> also OK with that.
>>>
>>> So it's up to you -- please state your decision, so that I know if I
>>> should proceed with v5 (later this week), or wait for v6.
>>
>> I think I would prefer to send v6. Looking at the v5 comments so far, I'm
>> sure that there's a lot of non conforming coding style issues.
>> Addressing them now (or at least a hopefully significant subset) would
>> probably save time.
> 
> I agree; thank you.
> 
> (And, for all the yelling that ECC does, I'm really surprised it didn't
> catch the "missing space between function designator and opening paren"
> wart!)

Heh. Yeah, I was surprised at how little fault ECC found in the code.

Thanks for reviewing.
Ankur

> 
>> I'm looking at sending these out by Thursday morning PT, and given that
>> you plan to continue later this week, sounds like it might not lose too
>> much review time either.
> 
> Yes, that should work fine.
> 
> Thank you, Ankur!
> Laszlo
> 

  reply	other threads:[~2021-01-26 22:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  6:44 [PATCH v5 0/9] support CPU hot-unplug Ankur Arora
2021-01-26  6:44 ` [PATCH v5 1/9] OvmfPkg/CpuHotplugSmm: refactor hotplug logic Ankur Arora
2021-01-26 19:01   ` Laszlo Ersek
2021-01-26 19:04     ` Laszlo Ersek
2021-01-26 19:09     ` Laszlo Ersek
2021-01-26 19:15     ` Ankur Arora
2021-01-26 21:07       ` Laszlo Ersek
2021-01-26 21:17         ` Ankur Arora
2021-01-26 21:32           ` Laszlo Ersek
2021-01-26 22:53             ` Ankur Arora [this message]
2021-01-26  6:44 ` [PATCH v5 2/9] OvmfPkg/CpuHotplugSmm: collect hot-unplug events Ankur Arora
2021-01-26  6:44 ` [PATCH v5 3/9] OvmfPkg/CpuHotplugSmm: add Qemu Cpu Status helper Ankur Arora
2021-01-26  6:44 ` [PATCH v5 4/9] OvmfPkg/CpuHotplugSmm: introduce UnplugCpus() Ankur Arora
2021-01-26  6:44 ` [PATCH v5 5/9] OvmfPkg/CpuHotplugSmm: define CPU_HOT_EJECT_DATA Ankur Arora
2021-01-26  6:44 ` [PATCH v5 6/9] OvmfPkg/SmmCpuFeaturesLib: init CPU ejection state Ankur Arora
2021-01-26  6:44 ` [PATCH v5 7/9] OvmfPkg/CpuHotplugSmm: add CpuEject() Ankur Arora
2021-01-26  6:44 ` [PATCH v5 8/9] OvmfPkg/CpuHotplugSmm: add worker to do CPU ejection Ankur Arora
2021-01-26  6:44 ` [PATCH v5 9/9] OvmfPkg/SmmControl2Dxe: negotiate CPU hot-unplug Ankur Arora
2021-01-26 18:03 ` [edk2-devel] [PATCH v5 0/9] support " Laszlo Ersek
2021-01-26 20:09   ` Ankur Arora
2021-01-26 18:18 ` Laszlo Ersek

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=b64b73a7-56d2-4064-c257-193ae1ef7652@oracle.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