sailus, did you have time to check those warning cleanups I did for atomisp? mchehab: please note https://patchwork.linuxtv.org/patch/48143/. The driver fixes definitely should go to 4.17, the doc fixes can slip to 4.18, but I feel most/all of those should also go to 4.17 since the docs are simply wrong. Your call, though. hverkuil: I'm sending right now what we already have for 4.17... after having it applied, I'll take a look on it I'd like to also send the atomisp patches I made too, if sailus is ok... as it does lots of changes at atomisp... not applying it would very likely mean that we'll receive atomisp patches that won't apply cleanly after we merge it on our tree so, better apply it for -rc1 No problem, as long as it will be applied :-) we should likely take a look at patchwork to double check if aren't there any build fix patches there is one from Dan, afaikt... but it is from something that I received another fix from Arnd not sure if they were applied upstream This one from Arnd is in my pull request: https://git.linuxtv.org/hverkuil/media_tree.git/commit/?h=for-v4.17f&id=a193b0bc5407f7f30f789997785032434c821e19 I applied on a tree here locally together with other patches for 4.18 I'm developing no, it is related to I2C new binding way BTW: Jasmin has been doing a great job on media_build: we now have an OK. Still some sparse warnings, though. great well, with the atomisp patchset, we'll get rid of lots of sparse/smatch warnings I'm not building atomisp for the daily build at the moment. ah I wander if atomisp driver works :-) mchehab: I wouldn't bet on that :-) the code looks so crappy/scarry that I doubt it works as I said before I doubt it will ever get out of staging well, it will... most likely going to /dev/null that will be a shame, as I bet people put a lot of effort writing it time, yes. effort, yes. quality... :-) heh, true hans, this patch: Subject: [PATCH] media: dvb-core: Check for allocation failure in dvb_module_probe() it should go to 4.17 too, but I'm pretty sure that either I or someone else wrote the same fix Subject: [PATCH 01/30] media: dvbdev: handle ENOMEM error at dvb_module_probe() I did and it was merged already Sorry, what does that have to do with me? https://patchwork.linuxtv.org/patch/48231/ (08:19:00) mchehab: we should likely take a look at patchwork to double check if aren't there any build fix patches (08:19:18) mchehab: there is one from Dan, afaikt... not related to anything you should do... it is just related to the above commens I made ^ Uh, okay. on this particular case, all it needs is to mark https://patchwork.linuxtv.org/patch/48231/ as superseeded. I'll do that done anyway, similar patches (if any) may need to be applied for 4.17 as well so, what I meant to say is that we should take a quick look if are there any patches fixing issues for 4.17 submitted by the usual jenitors just to be sure that we're not missing anything important I'll probably add https://patchwork.linuxtv.org/patch/48346/ for 4.17 as well How about this: https://patchwork.linuxtv.org/patch/47966/ i prefer apply it after -rc1 no need to hush on it also, it has potential of causing some harm as it removes depends on from kconfigs if one of dependencies chain there is wrong, it could cause build issues