From: "Huang, Kai" <kai.huang@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Jun Miao <jun.miao@intel.com>
Cc: <dave.hansen@linux.intel.com>, <linux-coco@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/virt/tdx: Correct the errors in the comments
Date: Thu, 13 Feb 2025 11:09:39 +1300 [thread overview]
Message-ID: <b2bd829a-99b2-4dd1-b5f3-58072fe98a60@intel.com> (raw)
In-Reply-To: <r7shaamvucw35wqymhkmceu3gpu2fedgv2umlcgdglglw65m4o@heaniim3gikx>
On 13/02/2025 1:01 am, Kirill A. Shutemov wrote:
> On Wed, Feb 12, 2025 at 03:58:05PM +0800, Jun Miao wrote:
>> In comment of config_global_keyid(), the "will fail" is duplicate, delete it.
>
> In the comment for config_global_keyid(), the phrase "will fail" is
> duplicated. Remove it.
>
>> Signed-off-by: Jun Miao <jun.miao@intel.com>
>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>
Acked-by: Kai Huang <kai.huang@intel.com>
prev parent reply other threads:[~2025-02-12 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 7:58 [PATCH] x86/virt/tdx: Correct the errors in the comments Jun Miao
2025-02-12 12:01 ` Kirill A. Shutemov
2025-02-12 22:09 ` Huang, Kai [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=b2bd829a-99b2-4dd1-b5f3-58072fe98a60@intel.com \
--to=kai.huang@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jun.miao@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@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