On Wed 2022-03-02 14:46 -0800, Luis Chamberlain wrote: > Since we are doing this to help with the cleaning this crap up > the natural thing to do is have the code be a helper which only > built-in code can use, so writing a helper starting with > list_for_each_entry() which prints the modules out. I'm > surprised we have no other users of this. There is nothing > kdb specific about the functionality in that code. So it should > just be moved. Hi Luis, Good point, albeit is it really worth it since the only external user is kernel/debug/kdb/ code? Kind regards, -- Aaron Tomlin