Hi Quentin, On Tue, 7 Jul 2026 at 10:09, Quentin Schulz <[email protected]> wrote: > > Simplify the ARM ROCKCHIP entry in MAINTAINERS by making extensive use > of the N: regex. For some reason, it slightly modifies the list of > people returned by get_maintainer.pl but I believe the ones reported as > maintainers are still correct. > > Add more files under the ARM ROCKCHIP umbrella. > > Remove inactive maintainer (Philipp Tomsich). > > @Simon, since you don't have permission to push to the Rockchip > custodian tree, I was planning to remove you from Rockchip maintainers > as well to reflect the reality but since you're still an active > reviewer/contributor, maybe you would like to be kept as Rockchip > reviewer (R:)?
Since Kever took over I haven't been doing PRs. As you say below, it has been great to have the vendor looking after this. I will likely see patches anyway, but keeping me around as R: sounds good to me. I have quite a few boards and I hope that RK3399 VBE will be merged at some point. > > Add myself as maintainer. > > As could be seen over the last year or so, Rockchip support in U-Boot > has almost ground to a halt with Kever only being able to find time for > his maintainership every few months due to his responsibilities at > Rockchip having changed. > I would like to express thanks to Kever as it is not that often we get > people from the SoC vendor actually contributing to upstream projects, > let alone maintain them. I'm hoping you can keep helping us especially > for things that aren't documented in manuals or for odd behaviors. This > is my reason for still keeping you as maintainer for now, but if you > would like to be switched to Reviewer or dropped entirely from > MAINTAINERS, please let us know. I likely will automatically switch you > to reviewer in a few weeks/months if you aren't migrated to the new > GitLab instance and thus do not have the rights to push to the Rockchip > custodian tree. > > I've reviewed Rockchip stuff for a few years already and my current > employer has all its products based on Rockchip for almost 10 years now. > I want to be very clear with what to expect from my maintainership: I am > likely not going to spend substantially more time than I am today > reviewing things, I'm essentially just going to unblock the merging part > of anything Rockchip once they are reviewed. There are many things I'm > unfamiliar with, so I'll likely ask odd questions or clarifications until > I can get some basic knowledge in new areas. > Things aren't going to go faster by themselves so this is also a call to > action. If you do find yourself frustrated because things take time to > get reviewed, please consider spending some time reviewing or testing > other people's patches to help with the global effort. If you do find > yourself in a position where you can spare some time to review or test > things, please feel free to do those things (be it for anything Rockchip > or anything in U-Boot really, or even in FOSS in general). > Finally, I've never been a maintainer and I haven't really figured out > my workflow yet so I'll likely make mistakes and asks many questions in > the beginning, so bear with me and report anything odd or wrong. > > @Tom, if/when this gets merged, anything needing to be done in the new > GitLab and/or patchwork to get me the appropriate permissions and > duties? For patchwork, I'm already registered under qschulz. For the new > GitLab, as quentin.schulz. > > Signed-off-by: Quentin Schulz <[email protected]> > --- Regards, Simon
