Re: [PATCHv2 01/12] x86/tdx: Consolidate TDX error handling

[Edgecombe, Rick P]

On Thu, 2025-07-31 at 16:31 -0700, Sean Christopherson wrote:
> On Wed, Jul 30, 2025, Rick P Edgecombe wrote:
> > So STATUS_OPERAND_BUSY() seems like an ok thing to try next for v3 of this
> > series at least. Unless anyone has any strong objections ahead of time.
> 
> Can you make it IS_TDX_STATUS_OPERAND_BUSY() so that it's obviously a check and
> not a statement/value, and to scope it to TDX?

It's a mouthful, but I can live with it. Yea, it def should have TDX in the name.