mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Balbir Singh" <bsingharora@gmail.com>
To: risrajak@in.ibm.com
Cc: ltp-coverage@lists.sourceforge.net,
	ltp-announce@lists.sourceforge.net, lxc-dev@googlegroups.com,
	linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Container Code Coverage for 2.6.23 mainline kernel
Date: Wed, 9 Jan 2008 14:38:32 +0530	[thread overview]
Message-ID: <661de9470801090108k2e81e8fawf885d643b0aeeafe@mail.gmail.com> (raw)
In-Reply-To: <1199863373.4440.9.camel@localhost.localdomain>

On Jan 9, 2008 12:52 PM, Rishikesh K. Rajak <risrajak@linux.vnet.ibm.com> wrote:
>
>  Hi All,
>
>  You can find the code coverage data for container code which has been
> merged with mainline linux-2.6.23 and respective testcases are merged with
> ltp for the feature called SYSVIPC NAMESPACE & UTS NAMESPACE .
>
>  I have genrated the code on s390x machine, the more info you can find
> below.
>
>  Linux  2.6.23-gcov-autokern1 #1 SMP Wed Jan 9 00:27:11 EST 2008 s390x s390x
> s390x GNU/Linux
>
>  Please let me know if you need more info.
>
>  Thanks
>  Rishi
>

Rishi,

Something is wrong with the HTML within the tarball, it still points
to files in /home/rishi/....
Could you please fix that.

Thanks,
Balbir

       reply	other threads:[~2008-01-09  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1199863373.4440.9.camel@localhost.localdomain>
2008-01-09  9:08 ` Balbir Singh [this message]
2008-01-09  9:15   ` Subrata Modak
2008-01-09  9:18     ` Balbir Singh
     [not found]       ` <1199870509.4415.27.camel@subratamodak.linux.ibm.com>
     [not found]         ` <661de9470801090131l3c640ac4ga3b33af846c6defa@mail.gmail.com>
2008-01-09  9:55           ` Subrata Modak

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=661de9470801090108k2e81e8fawf885d643b0aeeafe@mail.gmail.com \
    --to=bsingharora@gmail.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 \
    --cc=lxc-dev@googlegroups.com \
    --cc=risrajak@in.ibm.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
all inboxes | Powered by JetHome®