From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
ltp-announce@lists.sourceforge.net,
ltp-list@lists.sourceforge.net,
ltp-coverage@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Ltp-coverage] [ANNOUNCE] GCOV & LCOV Packages Released
Date: Wed, 22 Aug 2007 13:12:36 +0200 [thread overview]
Message-ID: <46CC1A24.5030509@de.ibm.com> (raw)
In-Reply-To: <661de9470708220315l24c5313by50b9c027d0e38ba2@mail.gmail.com>
Balbir Singh wrote:
> On 22 Aug 2007 12:57:47 +0200, Andi Kleen <andi@firstfloor.org> wrote:
>> Have you considered submitting these patches for review to mainline?
> I second that, it would be nice to have these features in mainline instead of
> maintaining them for every kernel release.
Actually yes, I did and am still considering to do that. Still I feel that there are a few things that need to be changed in the gcov-kernel code before it's suitable for inclusion into mainline (e.g. move from use of /proc to debugfs, use of seqfile mechanism instead of custom code). Part of that work has already been done by yyangcdl@cn.ibm.com and myself but we've stalled about half-way due to a lack of time.
Seeing that there seems to be some support for the idea, I'll try to come up with a patch for further discussion.
Regards,
Peter Oberparleiter
prev parent reply other threads:[~2007-08-22 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 9:29 [ANNOUNCE] GCOV & LCOV Packages Released Subrata Modak
2007-08-22 10:57 ` Andi Kleen
2007-08-22 10:15 ` Balbir Singh
2007-08-22 11:12 ` Peter Oberparleiter [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=46CC1A24.5030509@de.ibm.com \
--to=peter.oberparleiter@de.ibm.com \
--cc=andi@firstfloor.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-announce@lists.sourceforge.net \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
/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