The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tom Zanussi <zanussi@us.ibm.com>,
	Karim Yaghmour <karim@opersys.com>,
	Paul Mundt <lethal@linux-sh.org>, Jes Sorensen <jes@sgi.com>,
	Richard J Moore <richardj_moore@uk.ibm.com>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	Michel Dagenais <michel.dagenais@polymtl.ca>,
	Douglas Niehaus <niehaus@eecs.ku.edu>,
	ltt-dev@shafik.org, systemtap@sources.redhat.com
Subject: Re: [PATCH 15/16] LTTng 0.6.36 for 2.6.18 : Userspace tracing
Date: Fri, 24 Nov 2006 22:12:49 -0500	[thread overview]
Message-ID: <20061125031249.GA25728@Krystal> (raw)
In-Reply-To: <20061125025448.GA15515@linux-mips.org>

* Ralf Baechle (ralf@linux-mips.org) wrote:
> On Fri, Nov 24, 2006 at 05:04:13PM -0500, Mathieu Desnoyers wrote:
> 
> > Userspace tracing : facility registration and event logging through system
> > call.
> 
> The patch defines the syscall numbers for several architectures but
> doesn't change arch/i386/kernel/syscall_table.S, arch/mips/kernel/scall*.S
> etc.
> 
>   Ralf
> 

Hi Ralf,

I stripped them from my complete version (it is in my instrumentation
patches). Only tracing from user space application is affected. As this is a
minor issue, I will only fix it in my next post.

Thanks,

Mathieu

OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

      reply	other threads:[~2006-11-25  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 22:04 [PATCH 15/16] LTTng 0.6.36 for 2.6.18 : Userspace tracing Mathieu Desnoyers
2006-11-25  2:54 ` Ralf Baechle
2006-11-25  3:12   ` Mathieu Desnoyers [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=20061125031249.GA25728@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=jes@sgi.com \
    --cc=karim@opersys.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=mbligh@mbligh.org \
    --cc=michel.dagenais@polymtl.ca \
    --cc=mingo@redhat.com \
    --cc=niehaus@eecs.ku.edu \
    --cc=ralf@linux-mips.org \
    --cc=richardj_moore@uk.ibm.com \
    --cc=systemtap@sources.redhat.com \
    --cc=tglx@linutronix.de \
    --cc=zanussi@us.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