On Mon, 15 Jun 2020 21:40:38 +1000 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > Thanks for investigating. I now realise that this was sent against > my first patch which did have this problem, which was fixed in my > second patch. Sorry for the false alarm. Which is why it is recommended that new patches start their own threads ;-) That said, Acked-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx> for the v2 patch. -- Steve
