On Mon, Jun 16, 2014 at 08:10:28AM -0700, Brian Buhrow wrote: > Hello. Perhaps my question is naive, but why does there need to be a > distinction between what log_dev() and aprint_*() do? Why not just change > aprint_* functions under the hood to use the log facilities of the kernel > as appropriate. then as a device driver writer, I don't need to change my > code to keep it working in the netbsd tree nor do I need to worry about > when which is appropriate to use. Adding a new logging function wich is > essentially the same as a function as is already being used, I'm talking > from a users' perspective, not a technical perspective, seems like a lot of > unnecessary code churn for very little gain. As long as I know how to make > the kernel squawk when I need it to, I don't much care if it uses log() or > printf(), so long as the messages get to a place where I can see them. > Ok, there, I've asked. I'm prepared to be enlightened as to the error > of my ways. Lol.
When I say "retire", I mostly mean "stop documenting". As you point you, there is little point (beside annoying people) in removing the aprint_* API. But if it could gently be pushed out to the retirement castle, I wouldn't mind the slightest. -- Quentin Garnier - c...@cubidou.net "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
pgpjc5dmAjpt3.pgp
Description: PGP signature
