linux-kernel - Re: [PATCH hyperv-next] x86/hyperv: Fix APIC ID and VP ID confusion in hv_snp_boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0001941a-2946-44ab-87f5-78bee7619fe1@linux.microsoft.com>
Date: Mon, 28 Apr 2025 10:29:41 -0700
From: Roman Kisel <romank@...ux.microsoft.com>
To: Wei Liu <wei.liu@...nel.org>, Michael Kelley <mhklinux@...look.com>
Cc: "bp@...en8.de" <bp@...en8.de>,
 "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
 "decui@...rosoft.com" <decui@...rosoft.com>,
 "haiyangz@...rosoft.com" <haiyangz@...rosoft.com>,
 "hpa@...or.com" <hpa@...or.com>, "kys@...rosoft.com" <kys@...rosoft.com>,
 "mikelley@...rosoft.com" <mikelley@...rosoft.com>,
 "mingo@...hat.com" <mingo@...hat.com>,
 "tglx@...utronix.de" <tglx@...utronix.de>,
 "tiala@...rosoft.com" <tiala@...rosoft.com>,
 "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "x86@...nel.org" <x86@...nel.org>, "apais@...rosoft.com"
 <apais@...rosoft.com>, "benhill@...rosoft.com" <benhill@...rosoft.com>,
 "bperkins@...rosoft.com" <bperkins@...rosoft.com>,
 "sunilmut@...rosoft.com" <sunilmut@...rosoft.com>
Subject: Re: [PATCH hyperv-next] x86/hyperv: Fix APIC ID and VP ID confusion
 in hv_snp_boot_ap()



On 4/27/2025 5:48 PM, Wei Liu wrote:
> On Fri, Apr 25, 2025 at 04:55:42PM +0000, Michael Kelley wrote:

[...]

>>>
>>> I appreciate your help with the precision. I used loose language,
>>> agreed, would like to fix that. The patch was applied though but not yet
>>> sent to the Linus'es tree as I understand. I'd appreciate guidance on
>>> the process! Should I send a v2 nevertheless and explain the situation
>>> in the cover letter?
>>>
>>> IOW, how do I make this easier for the maintainer(s)?
>>
>> Wei Liu should give his preferences. But in the past, I think he has
>> just replaced a patch that was updated. If that's the case, you can
>> send a v2 without a lot of additional explanation.
>>
> 
> Normally if you need to send a new version because the original
> patch is buggy, you can just update your patch.
> 
> If only a commit message or comment needs to be updated, I will let the
> submitter know either to send a new version or not. Sometimes I will
> just make the changes myself to save the submitter some time.
> 

Very kind of you, thanks a lot for the explanation!

> Wei.

-- 
Thank you,
Roman