From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>,
linfeng.sun.dev@gamil.com, mst@redhat.com,
patches@lists.linux.dev, stable@vger.kernel.org,
Linfeng Sun <linfeng.sun.dev@gmail.com>
Subject: Re: [PATCH 7.1 065/271] vhost_iotlb: bound map allocation in add_range
Date: Tue, 18 Aug 2026 11:43:13 -0400 [thread overview]
Message-ID: <20260818153252.GA1958243@sashalap> (raw)
In-Reply-To: <8C74607E-84F5-46BF-BE37-7F04B62D865E@gmail.com>
On Tue, Aug 18, 2026 at 11:55:21AM +0800, Linfeng Sun wrote:
>For subsequent kernel commits, I have already requested the correction
>through .mailmap
That part is already sorted: b3cfa692878e ("mailmap: update email address
for Linfeng Sun") is in linux-next and maps gamil.com -> gmail.com, so this
commit will resolve to your correct address once that reaches mainline.
>If it is still possible to update the author information here, I would like
>it to be changed to:
>Linfeng Sun <linfeng.sun.dev@gmail.com>
The stable backport carries the author line verbatim from the upstream
commit, so the queued patch is a faithful copy of 1ed35ac7f3fe. Editing it
here would make the stable authorship diverge from mainline, so I'm going
to leave it as-is and let the .mailmap entry take care of it.
No trouble at all, thanks for the heads-up.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-18 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 3:55 [PATCH 7.1 065/271] vhost_iotlb: bound map allocation in add_range Linfeng Sun
2026-08-18 15:43 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-17 13:28 [PATCH 7.1 000/271] 7.1.9-rc1 review Greg Kroah-Hartman
2026-08-17 13:29 ` [PATCH 7.1 065/271] vhost_iotlb: bound map allocation in add_range Greg Kroah-Hartman
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=20260818153252.GA1958243@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linfeng.sun.dev@gamil.com \
--cc=linfeng.sun.dev@gmail.com \
--cc=mst@redhat.com \
--cc=patches@lists.linux.dev \
--cc=stable@vger.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