<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style> mchehab: <u>crope</u>: unping. I ended by applying this patch upstream: <br> 78bab93026ab [media] si2157: detect if firmware is running <br> if not ok, please ping me back qwebirc86425: hello, what does the following 'azap' error mean: "FE_GET_PROPERTY failed, ret=-1" crope: <u>mchehab</u>: do not apply. or if you already applied, then it is not big mistake still mchehab: <u>crope</u>: I applied it earlier today <br> should it be reverted? crope: <u>mchehab</u>: ok, let it be mchehab: ok <br> I'm applying today those small patches that are there for a long time <br> that means that I should still parse those two patches on my queue: https://patchwork.linuxtv.org/project/linux-media/list/?submitter=27 <br> are them ok or not? <br> ok, one of them you said that it shouldn't be applied <br> https://patchwork.linuxtv.org/patch/33481/ <br> I'll mark this one as rejected <br> <u>crope</u>: so, on your patch series, the only one that I'll likely handle before the merge window is this one: https://patchwork.linuxtv.org/patch/34115/ <br> please let me know if this one is OK or should be postponed/rejected crope: <u>mchehab</u>: I just pull requested that af9035 patch mchehab: OK crope: <u>mchehab</u>: 33481 will go via i2c tree, it is that new i2c-mux change mchehab: OK crope: <u>mchehab</u>: I havent done any changes to those drivers which has I2C-mux so there should not be conflicts mchehab: good crope: <u>mchehab</u>: and 34115 is jut 5 mins ago pull-requested :) <br> <u>mchehab</u>: everything from me should be now OK mchehab: If the patch is identical, I may end by applying 34115 directly and marking the pull request as superseded... <br> as I intend to only look at git pull requests if I have time after handling the individual patches ***: TeLLuS has quit IRC (Ping timeout: 264 seconds) <br> awalls1 has left qwebirc86425: hello, what does the following 'azap' error mean: "FE_GET_PROPERTY failed, ret=-1"