From: Roman Kisel <romank@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>, Michael Kelley <mhklinux@outlook.com>
Cc: "bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"decui@microsoft.com" <decui@microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"kys@microsoft.com" <kys@microsoft.com>,
"mikelley@microsoft.com" <mikelley@microsoft.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"tiala@microsoft.com" <tiala@microsoft.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"apais@microsoft.com" <apais@microsoft.com>,
"benhill@microsoft.com" <benhill@microsoft.com>,
"bperkins@microsoft.com" <bperkins@microsoft.com>,
"sunilmut@microsoft.com" <sunilmut@microsoft.com>
Subject: Re: [PATCH hyperv-next] x86/hyperv: Fix APIC ID and VP ID confusion in hv_snp_boot_ap()
Date: Mon, 28 Apr 2025 10:29:41 -0700 [thread overview]
Message-ID: <0001941a-2946-44ab-87f5-78bee7619fe1@linux.microsoft.com> (raw)
In-Reply-To: <aA7QZPFS7WWOsahp@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
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
prev parent reply other threads:[~2025-04-28 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 21:57 [PATCH hyperv-next] x86/hyperv: Fix APIC ID and VP ID confusion in hv_snp_boot_ap() Roman Kisel
2025-04-25 6:15 ` Wei Liu
2025-04-25 9:14 ` [EXTERNAL] " Saurabh Singh Sengar
2025-04-25 16:43 ` Roman Kisel
2025-04-25 17:18 ` Saurabh Singh Sengar
2025-04-25 18:22 ` Roman Kisel
2025-04-25 21:12 ` Wei Liu
2025-04-28 17:26 ` Roman Kisel
2025-04-25 15:12 ` Michael Kelley
2025-04-25 16:35 ` Roman Kisel
2025-04-25 16:55 ` Michael Kelley
2025-04-28 0:48 ` Wei Liu
2025-04-28 17:29 ` Roman Kisel [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-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=0001941a-2946-44ab-87f5-78bee7619fe1@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=apais@microsoft.com \
--cc=benhill@microsoft.com \
--cc=bp@alien8.de \
--cc=bperkins@microsoft.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=sunilmut@microsoft.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
/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