|
|
Log in / Subscribe / Register

Organizing kernel messages

Organizing kernel messages

Posted Oct 1, 2010 9:23 UTC (Fri) by error27 (subscriber, #8346)
Parent article: Organizing kernel messages

Why not: [git hash][file number][line number]

You would use a tool to check out the correct code.

The [git hash] would be the hash from most recent Linus tree. The [file number] would be the hash of the filename.

You could also assign a more permanent number by looking at the git hash for the patch which added the printk(). You could look the permentent number up on google or in your binder.

Actually the [git hash] would be stored in a file under /sys.


to post comments

Organizing kernel messages

Posted Oct 4, 2010 17:02 UTC (Mon) by Lennie (subscriber, #49641) [Link]

I was thinking the same thing.

But it is not useful to everyone.

It would only be useful as a (distribution)support or admin-tool.

If you are a kernel developer it wouldn't help you much.

To me, this seems fine, but maybe not for the people working on this.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds