[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8f5a27d-ae8f-4aec-aa4b-9f4d010e45ae@amd.com>
Date: Mon, 6 Jan 2025 17:08:48 -0600
From: "Kalra, Ashish" <ashish.kalra@....com>
To: Dionna Amalie Glaze <dionnaglaze@...gle.com>
Cc: seanjc@...gle.com, pbonzini@...hat.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, thomas.lendacky@....com, john.allen@....com,
herbert@...dor.apana.org.au, davem@...emloft.net, michael.roth@....com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-coco@...ts.linux.dev
Subject: Re: [PATCH v3 1/7] crypto: ccp: Move dev_info/err messages for
SEV/SNP initialization
On 1/6/2025 11:17 AM, Dionna Amalie Glaze wrote:
> On Fri, Jan 3, 2025 at 11:59 AM Ashish Kalra <Ashish.Kalra@....com> wrote:
>>
>> From: Ashish Kalra <ashish.kalra@....com>
>>
>> Remove dev_info and dev_err messages related to SEV/SNP initialization
>
> I don't see any "remove" code in this patch.
>
>
Actually, the removal code is in the final patch after the platform initialization
stuff has been moved to KVM, and this is more of a pre-patch to move dev_info/dev_err
messages related to SEV/SNP initialization inside __sev_platform_init_locked()
and __sev_snp_init_locked(), so i will drop the remove" from commit message and
keep only the move description as part of the commit message.
Thanks,
Ashish
Powered by blists - more mailing lists