On Mon, May 16, 2022 at 04:45:48PM +0300, Gil Fine wrote: > On Mon, May 16, 2022 at 04:19:46PM +0300, Mika Westerberg wrote: > > Hi Gil, > > > > On Mon, May 16, 2022 at 04:21:41PM +0300, Gil Fine wrote: > > > > So instead I suggest to put the device_for_each_child() in tmu.c and > > > > then the tb_switch_tmu_config_enable() static right above it. Please > > > > also name the resulting API function consistently. > > > > > > OK, got you and fixed that. > > > Please let me know when you think that I can send out the v4 series. > > > > You can send it whenever you want but I think it can go to v5.20 and not > > v5.19 since I was planning to send out my pull request for Greg > > tomorrow. I can pick it up after v5.19-rc1 is released. > > Ohh I see, I was hoping to meet v5.19 > Can't you send it also as part of your your pull request tomorrow? > Or it is not mature enough yet...? Well typically it is expected that patches have been sitting in linux-next for a while before going to the upstream maintainer (Greg in this case). This is to ensure they get at least some attention from the various build robots and also people running linux-next on their hardware.
