[PATCH 2/2] clk/qcom: sm8250: Fix variable name of msm_clk_data

[Casey Connolly]

On 6/18/25 13:11, Luca Weiss wrote:
> On Tue Jun 17, 2025 at 10:27 AM CEST, Luca Weiss wrote:
>> On Fri Jun 13, 2025 at 6:55 PM CEST, Casey Connolly wrote:
>>>
>>>
>>> On 6/13/25 08:45, Luca Weiss wrote:
>>>> On Thu Jun 12, 2025 at 5:49 PM CEST, Alexey Minnekhanov wrote:
>>>>> On 11.06.2025 15:08, Luca Weiss wrote:
>>>>>> Update the variable name to sm8250_gcc_data as it's in the sc7280
>>>>>> driver.
>>>>>
>>>>> Hi!
>>>>> But why are you mentioning sc7280 here, while fixing clock-sm8250.c ?
>>>>
>>>> Copy paste from the other patch :'(
>>>>
>>>> Will fix, thanks for spotting!
>>>
>>> I'll fix this while applying, np (already picked this patch up...)
>>
>> Thank you!
> 
> Quick process question, how do I find out if a patch has been
> accepted/applied? Am I supposed to check patchwork, or are there
> b4-ty-style emails for it?

I will be sending b4 ty emails, I have made the mistake lately of 
leaving some things that ought to be done during review until the point 
where I pick the patches, and I want to make sure CI is passing and 
everything applies before sending those.

I'm hoping to get better at it this cycle...>
> I'm trying to keep track of patches in my inbox that are still
> outstanding with labels, so it's basically about when I can mark it as
> accepted.

You can check patchwork or see what's pushed to the snapdragon custodian 
branch

https://source.denx.de/u-boot/custodians/u-boot-snapdragon

Kind regards,

> 
> Regards
> Luca
> 
>>
>>>
>>> Thanks>
>>>>>
>>>>>> ---
>>>>>>     drivers/clk/qcom/clock-sm8250.c | 4 ++--
>>>>>>     1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>>
>>>>>> diff --git a/drivers/clk/qcom/clock-sm8250.c b/drivers/clk/qcom/clock-sm8250.c
>>>>>
>>>>>
>>>>> ---
>>>>> Regards,
>>>>> Alexey Minnekhanov
>>>>
> 

-- 
Casey (she/they)