On Mon 2022-02-07 17:17 +0000, Christophe Leroy wrote:
Yes and that's the purpose of the patch I proposed at
https://patchwork.kernel.org/project/linux-modules/patch/203348805c9ac9851d8939d15cb9802ef047b5e2.1643919758.git.christophe.leroy@csgroup.eu/
I see.
Allthough I need to find out what's the problem reported by the robot.
I'll have a look too.
As suggested by Luis, this fix should go once all ongoing work is done.
But it would be nice if you could just remove patch 5 from you series,
otherwise we would have to revert it later.
Perhaps it might be easier if I keep the patch within the series; once
merged into module-next, by Luis, you can rebase and then add the "Fixes:"
tag to resolve the issue, no?
Kind regards,
--
Aaron Tomlin