On Fri, Jun 23, 2023, Ladislav Michl wrote: > Hi, > > On Thu, Jun 22, 2023 at 11:01:54PM +0000, Thinh Nguyen wrote: > > Hi, > [snip] > > Please use get_maintainer.pl to get all the proper maintainers to review > > the changes. > > That's what I did. Thomas, MIPS maintainer is reading linux-mips list, > Greg is reading linux-usb list, you were the one who receives changes, > hence all patcheset was sent to you in a hope you provide some comments > about actual code changes. I can take a look at the changes. However, the patches were sent directly To: me for patches related MIPS and no one else except the linux-usb linux-mips (without Thomas), which doesn't look right. I'm not familiar with the MIPS subsystem, but typically for the USB mailing list, we capture all the emails generated from get_maintainer.pl and include them To: and Cc: should they need attention to the changes. Often we filter our emails based on whether it's directed toward us, at least I do that. Also, we can't be sure if everyone still subscribes to the corresponding mailing list. > > > Since this is a large change involving different subsystems, if > > possible, please split the changes related to MIPS and try to upstream > > those first as they will affect how dwc3 glue driver will look. > > That's pretty straightforward as patchset is arranged exactly this way, > so MIPS maintainer is free to apply patches till driver move. > However, any actual feedback would be still usefull. In case it gets > some acks I'll add them and rebase patches to the latest -next. > Then that's good. If the MIPS maintainer approves all the MIPS related changes and already pick them up, there should be no problem. Thanks, Thinh
