From: Caspar Zhang <caspar@casparzhang.com>
To: "Xu, Anhua" <anhua.xu@intel.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>,
"Song, Youquan" <youquan.song@intel.com>
Subject: Re: [LTP] [Ltp-commits] [patches 1/3]perfcounter api updates
Date: Fri, 02 Dec 2011 13:44:09 +0800 [thread overview]
Message-ID: <4ED865A9.4080801@casparzhang.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B212E02C9595@shsmsx501.ccr.corp.intel.com>
On 12/02/2011 12:59 PM, Xu, Anhua wrote:
> Hi, I'm newbie to LTP and I have some patches to submit. Not sure if it is OK to post here.
Hi, ltp-list@lists.sourceforge.net should be the right place to put your
patches. And I suggest to take a look at $LTPROOT/doc/style-guide.txt to
get your patches submitted via git.
Thanks,
Caspar
> Since perfcounter associated test cases had been out of date. I updated data structures used by new apis.
> And add a header file for both perfcounter01 and perfcounter02
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2011-12-02 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1A42CE6F5F474C41B63392A5F80372B212E02C9595@shsmsx501.ccr.corp.intel.com>
2011-12-02 5:44 ` Caspar Zhang [this message]
2012-01-05 13:02 ` [LTP] [Ltp-commits] [patches 1/3]perfcounter api updates Cyril Hrubis
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=4ED865A9.4080801@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=anhua.xu@intel.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=youquan.song@intel.com \
/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