Re: [PATCH] firmware: smccc: support both conduits for getting hyp UUID

[Roman Kisel <romank@linux.microsoft.com>]

On 6/18/2025 5:20 AM, Anirudh Rayabharam wrote:
> On Tue, Jun 10, 2025 at 09:06:48AM -0700, Roman Kisel wrote:
>>> (sorry for the delay, found the patch in the spam 🙁)
>>
>> "b4" shows the the mail server used for the patch submission
>> doesn't pass the DKIM check, so finding the patch in the spam seems
> 
> How do you check this? I mean, what b4 command do you run?
> 
> I think it should be fix now. Let's see...


"b4 am" was showing the failed DKIM check, and all good now!

| $ b4 am 20250521094049.960056-1-anirudh@anirudhrb.com
|
| Grabbing thread from 
lore.kernel.org/all/20250521094049.960056-1-anirudh@anirudhrb.com/t.mbox.gz
| Analyzing 7 messages in the thread
| Looking for additional code-review trailers on lore.kernel.org
| Checking attestation on all messages, may take a moment...
| ---
|   ✓ [PATCH] firmware: smccc: support both conduits for getting hyp UUID
|     + Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
|     + Tested-by: Roman Kisel <romank@linux.microsoft.com> (✓ 
DKIM/linux.microsoft.com)
|     + Reviewed-by: Roman Kisel <romank@linux.microsoft.com> (✓ 
DKIM/linux.microsoft.com)
|   ---
|   ✓ Signed: DKIM/anirudhrb.com
| ---
| Total patches: 1
| ---
|  Link: 
https://lore.kernel.org/r/20250521094049.960056-1-anirudh@anirudhrb.com
|  Base: applies clean to current tree
|        git checkout -b 20250521_anirudh_anirudhrb_com HEAD
|        git am 
./20250521_anirudh_firmware_smccc_support_both_conduits_for_getting_hyp_uuid.mbx
|


[...]
>> Anirudh had been OOF for some time and would be for another
>> week iiuc so I thought I'd reply.
> 
> Thanks Roman!

My pleasure :)

> 
> Regards,
> Anirudh
> 
>>
>> The patch this depends on is 13423063c7cb
>> ("arm64: kvm, smccc: Introduce and use API for getting hypervisor UUID"),
>> and this patch has already been pulled into the Linus'es tree.
>>
>> As for routing, (arm-)soc should be good it appears as the change
>> is contained within the firmware drivers path. Although I'd trust more to your,
>> Arnd's or Wei's opinion than mine!
>>
>>>
>>> --
>>> Regards,
>>> Sudeep

-- 
Thank you,
Roman