On 12/03/2018 21:51, Fabio Estevam wrote:
Hi Tom and Stefano,
On Mon, Mar 12, 2018 at 1:07 PM, Tom Rini trini@konsulko.com wrote:
Anyway, I am facing what we should do with this patch for 2018.03. As I said, I am not forcing anyone and I have just picked up 1/3 and 2/3. But IMHO, if there are not good reason to say that not raising an error breaks a lot of supplied device, this should flow into 2018.03, too. And then we get enough time to better explore this issue.
And I need an answer to this final part, before I can release v2018.03. Thanks all!
Bryan's points are valid, so please apply his patch for v2018.03.> Breno and team can then revisit this for v2018.05.
Agree, this is the best way to go on.
Tom, can you apply it ? I have not other pending patches for the release, and my PR had just this one.
Thanks, Stefano