Re: [PATCH] x86/tdx, KVM: fix HKID leak when kexec is initiated with active TDs

[Sean Christopherson <seanjc@google.com>]

Restoring the Cc (especially the lists), as this is generally useful information
for newcomers (e.g. for other people reading along that might be new to upstream).

On Wed, Apr 22, 2026, Nowicki, Robert wrote:
> Hi Sean,
> Thank you for your reply,

Please don't top post.  https://people.kernel.org/tglx/notes-about-netiquette has
a lot of useful information for dealing with the lists.

I also recommend asking others at Intel for tips on setting up your mail client,
and other aspects of their upstream workflows.  Many/most companies (especially
big ones) have restricted environments that can make it annoying to get a "good"
setup for upstream development.

> I am not yet well familiar how processes are working here with new features
> development, trying to learn that.

No worries, pretty much everyone goes through the same experience :-)

> That's the first time I am working with reporting issues faced as just
> started validating TDX module on top of linux kernel, didn't know how it
> should be processed. 
>
> Intention was to let Vishal know about potential issue and suggest some fix
> which worked for me.

For patches that have been posted, but not yet merged, reporting issues (real or
theorized) is handled like code review.  Just reply to the patch email itself
with the (suspected) issue.  If you have a potential fix, you can include a sample
patch, a diff, a snippet of code, or something in between (that's the glorious
part of an email based patch+review system, it's very free-form so almost anything
goes).