[00:56] *** ChanServ sets mode: +v mchehab
[09:55] *** ChanServ sets mode: +v snawrocki
[10:00] <snawrocki> mchehab: it seems the media-next tree has not been updated for some time now, could please check it?
[13:40] <mchehab> snawrocki: linux-next is now updated from media_tree master and fixes branch
[13:40] <mchehab> so, I'm only updating media-next when really needed
[13:41] <mchehab> (e g once during the merge window and if some patch is needed just for linux-next - like a conflict solving patch)
[13:43] <snawrocki> mchehab: ah right, I should have came to this conclusion myself when I noticed media_tree.git#master is also on the Next tree list earlier...
[13:45] <snawrocki> mchehab: sounds good, so now we are not going to have any delays getting patches in -next
[13:45] <mchehab> yes
[13:46] <mchehab> that's the big advantage
[13:46] <mchehab> no extra procedure is required for them to get our stuff... all we need to do is to wait for the next -next release :-)
[13:47] <mchehab> and, if something goes wrong, we can use the media-next to solve
[13:47] <mchehab> (I actually didn't need to use it so far)
[13:47] <mchehab> but it is there, just in case
[13:50] <snawrocki> yes, we will be getting our bugs in -next right away ;) That's a good incentive for sending you pull requests frequently
[13:55] <hverkuil> mchehab: I plan on posting the final pull request(s) for 4.14 on Wednesday morning. That should be OK, right?
[14:01] <mchehab> yeah, that should work for me
[14:01] <mchehab> snawrocki: :-)
[14:01] <mchehab> yeah, a good colateral side effect :-p
[14:02] <mchehab> we'll see our bugs being reported faster
[14:11] <snawrocki> yes, it also helps working with next in general, should there happen any critical fixes in the media tree that are fixing bugs breaking support for any development board in one way or the other