linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Roman Kisel <romank@linux.microsoft.com>
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: Fri, 21 Feb 2025 14:04:16 +0100	[thread overview]
Message-ID: <Z7h50PqiXxdfMegl@gmail.com> (raw)
In-Reply-To: <20250220202302.2819863-1-romank@linux.microsoft.com>


* 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!

	Ingo

  parent reply	other threads:[~2025-02-21 13:04 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 ` Ingo Molnar [this message]
2025-02-24 16:57   ` [PATCH hyperv-next v2 0/2] x86/hyperv: VTL mode reboot fixes 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=Z7h50PqiXxdfMegl@gmail.com \
    --to=mingo@kernel.org \
    --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@redhat.com \
    --cc=romank@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).