On Thu, 20 Apr 2023, Mark Brown wrote: > On Thu, Apr 20, 2023 at 11:34:38AM +0100, Lee Jones wrote: > > > Once the regulator driver has been reviewed, I can take the set. > > > Please apply this if you have to resubmit: > > > For my own reference (apply this as-is to your sign-off block): > > > Acked-for-MFD-by: Lee Jones <lee@xxxxxxxxxx> > > For situations like this where there's a depends on to the MFD it'd be > great if you could just apply the MFD rather than waiting, the > individual drivers can either get applied on top or just go via the > subsystem and have everything sort itself out in the merge window. It'd > help things move along faster and be less confusing. > > These serieses tend to get so many resends that I'm often just not > looking at them, previously I'd have just applied the function driver > when it's ready but with the complaints when the core ends up missing > the merge window but function drivers are going in I stopped. In the > past I've ended up missing things because either there's multiple > serieses for similarly named devices out at once or (less often) some > change results in a repeat review being needed so it's easier to just > wait for things to settle down. I'll try anything once! Fair warning, I think this is going to massively complicate things. Either we're going to be left with a situation where child-driver maintainers are scrabbling around looking for previous versions for the MFD pull-request or contributors being forced to wait a full cycle for their dependencies to arrive in the maintainer's base. I'm not sure why simply providing your Ack when you're happy with the driver and forgetting about the set until the pull-request arrives, like we've been doing for nearly a decade now, isn't working for you anymore but I'm mostly sure this method will be a regression. -- Lee Jones [李琼斯]
