Messages in this thread | | | Date | 25 Sep 2007 03:50:27 -0400 | From | linux@horizon ... | Subject | Re: [RFC] New kernel-message logging API |
| |
>> Even the "kp_" prefix is actually pretty unnecessary. It's "info" >> and a human-readable string that make it recognizable as a log message.
> While I agree a prefix isn't necessary, info, warn, err > are already frequently #define'd and used. > > kp_<level> isn't currently in use. > > $ egrep -r -l --include=*.[ch] "^[[:space:]]*#[[:space:]]*define[[:space:]]+(info|err|warn)\b" * | wc -l > 29
Sorry for being unclear. I wasn't seriously recommending no prefix, due to name collisions (exactly your point), but rather saying that no prefix is necessary for human understanding.
Something to avoid the ambiguity is still useful. I was just saying that it can be pretty much anything withouyt confusing the casual reader.
We're in violent agreement, I just didn't say it very well the first time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |