On Wed, Dec 03, 2025 at 04:03:35PM -0500, Sean Anderson wrote: > Unfortunately I don't really have time to review clock patches. When I > initially started maintaining this subsystem I had more free time than I do > now. But I also found it hard to motivate myself to review patches. Many > clock patches add support for new SoCs and they are time consuming to > review properly. You effectively have to spend a few hours reading the > reference manual (if it's public!) and reviewing drivers is no small feat > either. This is made more difficult since clocking is often very different > between SoCs and it can be difficult to determine whether something is a > bug in the driver or a workaround for some hardware behavior. I mostly > don't care about any given SoC unless I'm hacking on it so I ended up with > a ton (more than 7000) of unreviewed patches piling up in my inbox. I'd > love to be more active, but I have a day job and I usually want to work on > something more interesting when I get home. I still think the clock > subsystem is a major mess but I don't care enough to fix it :l > > The subsystem itself should probably get orphaned since AFAICT all patches > go through the mach/arch maintainer or to Tom. > > Signed-off-by: Sean Anderson <[email protected]>
Thank you for your time and contributions over the years. Applied to u-boot/master. And yes, we do need to as a community figure out what to do next with the clk subsystem (and try harder to put SoC-specific parts under the SoC maintainers). -- Tom
signature.asc
Description: PGP signature
