In article <[email protected]>, Izaak <[email protected]> wrote: >Hi, > >Sorry for my silence on the aprint project. I was busy in the last >while, but I have more time to dedicate to it now. > >Anyway, I am currently working on the first task, converting printf to >the appropriate aprint during autoconfiguration. Having read through >many files, I have found that often printf is wrapped in a macro like >'DPRINTF', which is occasionally used both in the driver attachment >function and also elsewhere in the file. I am not sure whether to >replace the 'printf' inside the macro; make a new macro just for >attachment; replace the macro with a direct call to an aprint function. >Also, some macros contain uprintf, ttyprintf or tprintf (e.g. >/sys/dev/acpi/acpi_apm.c) -- Martin told me to leave those intact. I >suppose this question holds also for general macro usage, so what is the >best way to deal with that?
I think it is best to leave them alone too for now... christos
