public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Kisel <romank@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: ardb@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
	decui@microsoft.com, dimitri.sivanich@hpe.com,
	haiyangz@microsoft.com, hpa@zytor.com, imran.f.khan@oracle.com,
	jacob.jun.pan@linux.intel.com, jgross@suse.com,
	justin.ernst@hpe.com, kprateek.nayak@amd.com, kyle.meyer@hpe.com,
	kys@microsoft.com, lenb@kernel.org, mingo@redhat.com,
	nikunj@amd.com, papaluri@amd.com, perry.yuan@amd.com,
	peterz@infradead.org, rafael@kernel.org, russ.anderson@hpe.com,
	steve.wahl@hpe.com, tglx@linutronix.de, thomas.lendacky@amd.com,
	tim.c.chen@linux.intel.com, tony.luck@intel.com, xin@zytor.com,
	yuehaibing@huawei.com, linux-acpi@vger.kernel.org,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, apais@microsoft.com, benhill@microsoft.com,
	bperkins@microsoft.com, sunilmut@microsoft.com
Subject: Re: [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the wakeup AP callback
Date: Mon, 5 May 2025 10:22:47 -0700	[thread overview]
Message-ID: <41778d44-19dc-4212-a981-d5a82eaf9577@linux.microsoft.com> (raw)
In-Reply-To: <aBUByjvfjLsPU_5f@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>



On 5/2/2025 10:32 AM, Wei Liu wrote:
> On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:

[...]

>>   arch/x86/coco/sev/core.c           | 13 ++-----------
>>   arch/x86/hyperv/hv_vtl.c           | 12 ++----------
>>   arch/x86/hyperv/ivm.c              |  2 +-
>>   arch/x86/include/asm/apic.h        |  8 ++++----
>>   arch/x86/include/asm/mshyperv.h    |  5 +++--
>>   arch/x86/kernel/acpi/madt_wakeup.c |  2 +-
>>   arch/x86/kernel/apic/apic_noop.c   |  8 +++++++-
>>   arch/x86/kernel/apic/x2apic_uv_x.c |  2 +-
>>   arch/x86/kernel/smpboot.c          | 10 +++++-----
> 
> Since this is tagged as a hyperv-next patch, I'm happy to pick this up.
> 

Thank you very much, Wei!

> Some changes should be acked by x86 maintainers.

Tom and Thomas reviewed the patch, and the `scripts/get_maintainer.pl`
prints them as x86 maintainers. If I understand correctly what you're
saying, someone who sends patches from the x86 tree to Linus should add
Acked-by to the patch. Likely I should just wait until such person gets
to this patch.

If I'm misunderstanding, I'd appreciate a quick note to help me navigate
this :)

> 
> Thanks,
> Wei.
> 
-- 
Thank you,
Roman


  reply	other threads:[~2025-05-05 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 20:47 [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the wakeup AP callback Roman Kisel
2025-04-30 22:39 ` Michael Kelley
2025-05-02 16:14 ` Thomas Gleixner
2025-05-02 17:32 ` Wei Liu
2025-05-05 17:22   ` Roman Kisel [this message]
2025-05-05 18:01     ` Wei Liu
2025-05-05 18:12       ` Dave Hansen
2025-05-06  2:52         ` Wei Liu
2025-05-06  2:57           ` Wei Liu
2025-05-06  2:58 ` Wei Liu
2025-05-07  6:22   ` [EXTERNAL] " Saurabh Singh Sengar
2025-05-07  6:23   ` Wei Liu
2025-05-07 17:07     ` Roman Kisel

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=41778d44-19dc-4212-a981-d5a82eaf9577@linux.microsoft.com \
    --to=romank@linux.microsoft.com \
    --cc=apais@microsoft.com \
    --cc=ardb@kernel.org \
    --cc=benhill@microsoft.com \
    --cc=bp@alien8.de \
    --cc=bperkins@microsoft.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=imran.f.khan@oracle.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=justin.ernst@hpe.com \
    --cc=kprateek.nayak@amd.com \
    --cc=kyle.meyer@hpe.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=papaluri@amd.com \
    --cc=perry.yuan@amd.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=russ.anderson@hpe.com \
    --cc=steve.wahl@hpe.com \
    --cc=sunilmut@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=wei.liu@kernel.org \
    --cc=x86@kernel.org \
    --cc=xin@zytor.com \
    --cc=yuehaibing@huawei.com \
    /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