From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: busy loops in kernel
Date: Sun, 22 Jan 2012 12:17:08 +0000 [thread overview]
Message-ID: <1327234629.10566.82.camel@thorin> (raw)
In-Reply-To: <CAFTXME+fNAqqZjO4oRmbwt2cFbaDgbLW9gg94tzJvF4bwy7DtQ@mail.gmail.com>
Hi!
On Mit, 2012-01-18 at 09:48 -0800, Asim wrote:
[....]
> is actually: count, line numbers and C file. In some cases, when
> driver comprises of multiple files, line numbers may be shifted (since
> all files are merged together for analysis).
It's somewhat off-topic, but people are probably more motivated if they
get correct filenames+line numbers of the original source.
Other source munging tools like yacc/bison or lex/flex use "#line" to
get the C compiler to report in errors and warnings the correct
reference to the source.
Kind regards,
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
prev parent reply other threads:[~2012-01-22 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 4:15 busy loops in kernel Asim
2012-01-18 4:55 ` Greg Dietsche
2012-01-18 7:37 ` Dan Carpenter
2012-01-18 7:39 ` Dan Carpenter
2012-01-18 17:45 ` Asim
2012-01-18 17:48 ` Asim
2012-01-21 17:33 ` Asim
2012-01-21 19:04 ` Julia Lawall
2012-01-21 20:46 ` Asim
2012-01-21 20:50 ` Julia Lawall
2012-01-21 22:32 ` Asim
2012-01-22 6:09 ` Julia Lawall
2012-01-22 12:17 ` Bernd Petrovitsch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327234629.10566.82.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox