On 25.11.25 04:10, Chee, Tien Fong wrote:
> Hi Jan, Brian
> 
> On 25/11/2025 6:25 am, Sune Brian wrote:
>> [CAUTION: This email is from outside your organization. Unless you
>> trust the sender, do not click on links or open attachments as it may
>> be a fraudulent email attempting to steal your information and/or
>> compromise your computer.]
>>
>>> I'm all for finding the best technical solution in the end, but I wonder
>>> if we can at least come to an intermediate solution for the upcoming
>>> release so that folks do not need to carry too many extra patches in
>>> their pipelines (https://patchwork.kernel.org/project/cip-dev/patch/
>>> cf43e9da3cfc59771e801d3215d3b3794f3602a8.1763446144.git.jan.kis...@siemens.com/)
>> I am not sure why point to patch v4 but I did provide the final path
>> version that T.F. should be ok with.
>> https://patchwork.ozlabs.org/project/uboot/
>> patch/[email protected]/

Due to recent discussions in that thread, it floated on top of the
mailing list history for me. No other reasons.

>>
>> What this delay is that there are several feature coverage on the same
>> file.
>> Meanwhile, there are several similar patches pushed and T.F. action time
>> is a bit slow.
>>
>> The very first patch was almost two months ago.
>> https://patchwork.ozlabs.org/project/uboot/
>> patch/[email protected]/
>>
>> So I had no clue why that huge delay. BTW it is supposed to revert
>> that pointed out patch to easily fix things.
>>
> 
> Thanks for your patience. We have completed testing with Brian’s patch
> as well as Jan’s patch series, along with a few additional issues we
> identified during integration. We have addressed those issues in our own
> fixes, and we plan to send the patches out for review today.
> 
> Brian’s patch:
> https://patchwork.ozlabs.org/project/uboot/patch/20251114160423.1518-1-
> [email protected]/
> 
> Jan’s patch series:
> https://patchwork.ozlabs.org/project/uboot/cover/
> [email protected]/
> 
> During our testing, we found an issue in Jan’s series; I will follow up
> separately on those to provide detailed feedback.
> 
> Once our patches are posted, we would appreciate your review and
> testing. Please let us know if you spot anything that still needs
> adjustment.

I'm happy to test if you CC me, at least on the DE0 Nano SoC then. Also,
please tell us which patches you need updates of or which you would
integrate yourself.

Thanks,
Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

Reply via email to