[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3308dd7c-fc74-440a-875a-6568f57e8b89@amd.com>
Date: Mon, 15 Jul 2024 20:48:55 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: Tom Lendacky <thomas.lendacky@....com>, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
seanjc@...gle.com, pbonzini@...hat.com
Cc: hpa@...or.com, rmk+kernel@...linux.org.uk, peterz@...radead.org,
james.morse@....com, lukas.bulwahn@...il.com, arjan@...ux.intel.com,
j.granados@...sung.com, sibs@...natelecom.cn, nik.borisov@...e.com,
michael.roth@....com, nikunj.dadhania@....com, babu.moger@....com,
x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
santosh.shukla@....com, ananth.narayan@....com, sandipan.das@....com,
manali.shukla@....com, jmattson@...gle.com,
Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH v2 0/4] x86/cpu: Add Bus Lock Detect support for AMD
On 15-Jul-24 8:41 PM, Tom Lendacky wrote:
> On 7/12/24 04:39, Ravi Bangoria wrote:
>> Upcoming AMD uarch will support Bus Lock Detect (called Bus Lock Trap
>
> Saying "Upcoming AMD uarch" is ok in the cover letter, but in a commit
> message it doesn't mean a lot when viewed a few years from now. I would
> just word it as, depending on the context, something like "AMD
> processors that support Bus Lock Detect ..." or "AMD processors support
> Bus Lock Detect ...".
>
> Since it looks like a v2 will be needed to address the kernel test robot
> issues, maybe re-work your commit messages.
Makes sense. Will reword it in v3.
Thanks,
Ravi
Powered by blists - more mailing lists