On Wed, Nov 22, 2017 at 10:50:51PM +0200, Luca Coelho wrote: > The problem, and the reason why you see it as my having dropped the > ball, is that the change we needed grew into a massive refactoring of > the entire firmware loading mechanism, with the addition of driver > data, lots of advanced options etc.
Yeah I noted that, I don't blame you :) > You certainly remember that I even reviewed the first patchset, but > then it all snowballed into discussions that led to literally > *hundreds* of emails going back and forth and I just didn't have the > time to follow anymore... Like I said, I don't blame you. Hopefully for v4.16 things will fly better. > But, personally, I'm not in a hurry. It's a bit annoying to get > reports repeatedly from the community about those warnings and having > to explain how things work, but I can live with that. > > I'd be happy to help with anything that doesn't involve following > hundreds of emails and reviewing massive refactors in code I'm not > completely familiar with. ;) Let me know. Let's shoot to get something in for v4.16, for both ath10k and iwlwifi, but first we need the cleanup to get merged. If you have time some Reviewed-by's would be nice of the last posted patches. I'll bounce you copies. Luis
