Messages in this thread | | | Subject | RE: [patch] kernel events layer | Date | Sun, 25 Jul 2004 23:04:31 -0700 | From | "Perez-Gonzalez, Inaky" <> |
| |
> From: Chris Wedgwood > > This part worries me a lot. I would alsmost rather all possible > messages get stuck somewhere common so driver writes can't add these > ad-hoc and we can avoid a proliferation of either similar or pointless > messages. > > Forcing these into a common place lets people eyeball if a new > messages really is necessary --- and it makes writing applications to > deal with these things easier (since you don't have to scan the entire > kernel tree).
That sounds to me like the perfect job for grep. In fact, it is _very_ similar to the job the GNU guys did on the early days of i18n. They had the tool that extracted all the strings in _("xlate me") [#define _(a) a ] and built a catalog.
If you guys are up to it, I volunteer to write/port such a tool to scan out the send_kevent{_atomic,}()s and make a catalog out of it.
Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own (and my fault) - 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/
| |