On May 9, 2024 11:19:39 AM GMT+02:00, Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> wrote: >Many subsystem core drivers will probe and create subsystem specific >sysfs directories on on systems that don't have any hardware needing >drivers from that subsystem (if someone manually inserts them rather >than relying on automatic module dependency handling.) >I don't see why this class driver should be different and have to jump >through hoops to satisfy this requirement. You mean it should load because "Look ma, the others do it this way". Does it make any sense? Of course not. Are you arguing for the nonsensical "it should load" case because it is simply easier this way? How hard is that "jump through hoops" thing anyway? You mean it should load so that when booting an allmodconfig kernel there are not enough modules which are loading so lemme load one more. And then I need to go and rmmod them all before I need to do localmodconfig and build a tailored kernel for the machine. Or is there some other reason to load silly modules, use up resources for no good reason whatsoever and bloat the machine? You mean, f*ck it, right? Who cares... Geez. -- Sent from a small device: formatting sucks and brevity is inevitable.
