From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: anyone including <linux/perf_counter.h>?
Date: Wed, 16 Dec 2009 09:42:50 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912160939510.7588@localhost> (raw)
just prepping to run my cleanup suggestion scripts after the merge
window closes, quick test run on some scripts and ran across the fact
that no one appears to be including <linux/perf_counter.h>.
any value to that file? just curious. much more pedantry after the
merge window, of course.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-12-16 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 14:42 Robert P. J. Day [this message]
2009-12-16 14:51 ` anyone including <linux/perf_counter.h>? Kyle McMartin
2009-12-16 14:56 ` Robert P. J. Day
2009-12-16 14:58 ` Kyle McMartin
2009-12-16 15:01 ` Robert P. J. Day
2009-12-16 15:04 ` Kyle McMartin
2009-12-16 15:06 ` Robert P. J. Day
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=alpine.LFD.2.00.0912160939510.7588@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@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