On Wed, 13 Jun 2007 12:04:56 PDT, Joe Perches said: > I believe it better to simply add __FILE__ & __LINE__ to the > macro rather than some other externally specified unique > identifier that adds developer overhead and easily gets stale. There's been plenty of times I've wished for that. Now if we just found a way to do something sane for drivers/net/wireless/mac80211/iwlwifi/base.c ;) Of course, I'm probably atypical - for me, kernel messages come in two forms, the kind that are immediately obvious at first reading, and the kind that you end up having to look at the code and wonder WTF? it was doing inside that never-should-happen-on-this-hardware while loop in the first place... :)
Attachment:
pgppHX8ZZJBMU.pgp
Description: PGP signature
- Follow-Ups:
- Re: [RFC/PATCH] Documentation of kernel messages
- From: "H. Peter Anvin" <[email protected]>
- Re: [RFC/PATCH] Documentation of kernel messages
- References:
- [RFC/PATCH] Documentation of kernel messages
- From: holzheu <[email protected]>
- Re: [RFC/PATCH] Documentation of kernel messages
- From: Greg KH <[email protected]>
- Re: [RFC/PATCH] Documentation of kernel messages
- From: holzheu <[email protected]>
- Re: [RFC/PATCH] Documentation of kernel messages
- From: Joe Perches <[email protected]>
- [RFC/PATCH] Documentation of kernel messages
- Prev by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Previous by thread: Re: [RFC/PATCH] Documentation of kernel messages
- Next by thread: Re: [RFC/PATCH] Documentation of kernel messages
- Index(es):