public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Kisel <romank@linux.microsoft.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, decui@microsoft.com,
	haiyangz@microsoft.com, hpa@zytor.com, kys@microsoft.com,
	mingo@redhat.com, tglx@linutronix.de, wei.liu@kernel.org,
	ssengar@linux.microsoft.com, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	apais@microsoft.com, benhill@microsoft.com,
	sunilmut@microsoft.com
Subject: Re: [PATCH hyperv-next v2 0/2] x86/hyperv: VTL mode reboot fixes
Date: Mon, 24 Feb 2025 08:57:27 -0800	[thread overview]
Message-ID: <97010881-4b5e-4fb7-b8b3-b6c9e440e692@linux.microsoft.com> (raw)
In-Reply-To: <Z7h50PqiXxdfMegl@gmail.com>



On 2/21/2025 5:04 AM, Ingo Molnar wrote:
> 
> * Roman Kisel <romank@linux.microsoft.com> wrote:
> 
>> Roman Kisel (2):
>>    x86/hyperv: VTL mode emergency restart callback
>>    x86/hyperv: VTL mode callback for restarting the system
> 
> A: These two patch titles verbs.
> ...
> ...
> B: These two patch titles are missing verbs.
> 
> Like me you prefer B too, right? If so, please add back the missing
> verbs to the titles. I suggest "Add"/"Introduce", and "Call". Thank you!

Right :) Thank you for taking the time to help me, much appreciated!

> 
> 	Ingo

-- 
Thank you,
Roman


      reply	other threads:[~2025-02-24 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 20:23 [PATCH hyperv-next v2 0/2] x86/hyperv: VTL mode reboot fixes Roman Kisel
2025-02-20 20:23 ` [PATCH hyperv-next v2 1/2] x86/hyperv: VTL mode emergency restart callback Roman Kisel
2025-02-20 20:23 ` [PATCH hyperv-next v2 2/2] x86/hyperv: VTL mode callback for restarting the system Roman Kisel
2025-02-21 13:04 ` [PATCH hyperv-next v2 0/2] x86/hyperv: VTL mode reboot fixes Ingo Molnar
2025-02-24 16:57   ` 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=97010881-4b5e-4fb7-b8b3-b6c9e440e692@linux.microsoft.com \
    --to=romank@linux.microsoft.com \
    --cc=apais@microsoft.com \
    --cc=benhill@microsoft.com \
    --cc=bp@alien8.de \
    --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=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=ssengar@linux.microsoft.com \
    --cc=sunilmut@microsoft.com \
    --cc=tglx@linutronix.de \
    --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