From: Hemanth Selam <hemanth.selam@gmail.com>
To: Naman Jain <namjain@linux.microsoft.com>
Cc: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Long Li <longli@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v2 1/2] Drivers: hv: vmbus: fix typo "substract" in comment
Date: Mon, 7 Sep 2026 17:12:03 +0530 [thread overview]
Message-ID: <20260907114203.40171-2-hemanth.selam@gmail.com> (raw)
In-Reply-To: <f307de11-8915-47f9-a743-250296f10804@linux.microsoft.com>
On Mon, 07 Sep 2026, Naman Jain wrote:
> The change-log (these 3 lines) go after "---" line as a comment so that
> these do not get propagated to the git log in kernel tree.
Understood, thanks for the pointer and the example. The changelog belongs
below the "---", not in the commit message. I have moved it there for the
respins that went out after this one.
Since the diff itself is unchanged and Michael's Reviewed-by still stands,
please just drop the three lines when you apply it. Happy to send a v3
with the changelog in the right place if you would rather have that.
next prev parent reply other threads:[~2026-09-07 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 4:49 [PATCH v2 0/2] Drivers: hv: fix typos in comments Hemanth Selam
2026-09-07 4:49 ` [PATCH v2 1/2] Drivers: hv: vmbus: fix typo "substract" in comment Hemanth Selam
2026-09-07 9:21 ` Naman Jain
2026-09-07 11:42 ` Hemanth Selam [this message]
2026-09-13 23:03 ` Wei Liu
2026-09-07 4:49 ` [PATCH v2 2/2] tools/hv: fix typo "retrive" " Hemanth Selam
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=20260907114203.40171-2-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=wei.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.