[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e29642ea59d25d60d35c082d5772f644b41692ff.camel@intel.com>
Date: Tue, 17 Jan 2023 21:41:27 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "zhi.wang.linux@...il.com" <zhi.wang.linux@...il.com>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>
CC: "Christopherson,, Sean" <seanjc@...gle.com>,
"Shahar, Sagi" <sagis@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Aktas, Erdem" <erdemaktas@...gle.com>,
"dmatlack@...gle.com" <dmatlack@...gle.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>
Subject: Re: [PATCH v11 004/113] KVM: TDX: Initialize the TDX module when
loading the KVM intel kernel module
On Tue, 2023-01-17 at 08:03 -0800, Isaku Yamahata wrote:
> > Better mention the tdx_enable() is implemented in another patch? But I guess
> > we need a wrapper here so that the compilation would succeed.
>
> The coverletter mentions it. I'll make the commit message of this patch
> mention it anyway.
When this series is merged, the TDX host series must have already been merged.
You obviously don't need to say something like "tdx_enable() is implemented in
another patch/series" in _changelog_.
Powered by blists - more mailing lists