From: Dave Hansen <dave.hansen@intel.com>
To: "Huang, Kai" <kai.huang@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>, "bp@alien8.de" <bp@alien8.de>,
"hpa@zytor.com" <hpa@zytor.com>
Cc: "samitolvanen@google.com" <samitolvanen@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/virt/tdx: Add ENDBR for low level SEAMCALL assembly functions
Date: Wed, 4 Jun 2025 16:23:59 -0700 [thread overview]
Message-ID: <5876fb5f-dc8c-401a-833a-a33265ff1fc1@intel.com> (raw)
In-Reply-To: <f442380c2d8cc51b38105c6316cbe224a248fdfe.camel@intel.com>
On 6/4/25 16:16, Huang, Kai wrote:
> Could you also let me know whether I should keep the Fixes tag, and the
> history in the changelog?
Yeah, I think you should keep the Fixes: tag, unless I'm missing something.
As for the history lesson, you can just say that you think that the TDX
code was OK when merged, but wasn't converted with the rest of the
Fixes: commit. That's all you need.
next prev parent reply other threads:[~2025-06-04 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 0:38 Kai Huang
2025-06-04 19:46 ` Dave Hansen
2025-06-04 23:16 ` Huang, Kai
2025-06-04 23:23 ` Dave Hansen [this message]
2025-06-04 23:27 ` Huang, Kai
2025-06-04 23:57 ` Huang, Kai
2025-06-05 13:12 ` Huang, Kai
2025-06-05 13:10 ` [PATCH v2] x86/virt/tdx: Annotate TDX assembly to allow indirect calls Kai Huang
2025-06-05 14:07 ` [PATCH] x86/virt/tdx: Add ENDBR for low level SEAMCALL assembly functions Peter Zijlstra
2025-06-05 14:21 ` Peter Zijlstra
2025-06-05 14:54 ` Dave Hansen
2025-06-05 14:59 ` Peter Zijlstra
2025-06-05 23:20 ` Huang, Kai
2025-06-05 23:23 ` Dave Hansen
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=5876fb5f-dc8c-401a-833a-a33265ff1fc1@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®