On 29-08-25, 14:16, Zihuan Zhang wrote: > Thanks for applying the patch! > > I’ve been thinking further — instead of using __free directly, maybe we > could introduce a small macro wrapper around it to make the release scope > more controllable and consistent. > > Link: > https://lore.kernel.org/all/6174bcc8-30f5-479b-bac6-f42eb1232b4d@xxxxxxxxxx/ > > Do you think this would be a better approach, or should we just stick with > the current use of __free? Lets keep it simple for now and use __free directly. And keep this similar with other parts of the kernel. -- viresh
