On Mon, Oct 31, 2022 at 10:55:21PM +0100, Alexandre Belloni wrote: > > The issue with the current patch is that it forbids going for a better > solution because you will then take for granted that this driver can't > ever fail. > This is incorrect. My plan was to get this accepted first and then work with those responsible on a cleaner solution (which is much more vague). We can not wait for that cleaner solution now. There is nothing that prevents us from taking our time to find a cleaner solution, and then to change the code again to use it. Guenter