No u-boot-rockchip pull request sent or merged for v2022.04

[Alper Nebi Yasak]

On 11/03/2022 22:25, Alper Nebi Yasak wrote:
> On 11/03/2022 22:01, Tom Rini wrote:
>> On Fri, Mar 11, 2022 at 09:56:59PM +0300, Alper Nebi Yasak wrote:
>>> On 11/03/2022 21:18, Simon Glass wrote:
>>>> Apler, would you be interested in being a co-maintainer for Rockchip?
>>>
>>> I can try. Not sure how much I'll be able to help (both time and
>>> knowledge-wise), I only have a chromebook_kevin and just know few things
>>> about rk3399 stuff at best, learning as I go along. But I would like to
>>> help.
>>>
>>>> I very much want to get your other patches landed too, particularly
>>>> the 'kevin' ones as I have that board in my lab.
>>>
>>> Me too. Would they go into -next and v2022.07 at this point?
>>
>> Well, how self contained is it all?
> 
> It's this series [1], the first three patches only affect chromebook_bob
>  (board/google/gru, dts, configs). The final patch for chromebook_kevin

I mean the first patches only affect chromebook_bob as kevin isn't there
yet, those changes still apply to or are copied to kevin by the final
patch. (Didn't sound right when I re-read it so wanted to clarify.)

> adds a single define to linux-event-codes.h, duplicates some bob code
> and Kconfig already in arch/arm/mach-rockchip, in addition to
> kevin-specific files.
> 
> [1] Improve support for Bob chromebook and add support for Kevin
> https://patchwork.ozlabs.org/project/uboot/list/?series=278350