All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	linux-kernel@vger.kernel.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 3/16] LTTng 0.6.36 for 2.6.18 : Linux Kernel Markers
Date: Tue, 28 Nov 2006 20:06:31 -0500	[thread overview]
Message-ID: <20061129010631.GD8910@redhat.com> (raw)
In-Reply-To: <20061128054036.GA29273@infradead.org>

Hi -

On Tue, Nov 28, 2006 at 05:40:36AM +0000, Christoph Hellwig wrote:
> [...]
> > > Are you sure the license_gplok check is necessary here?  We should
> > > consider encouraging non-gpl module writers to instrument their code,
> > > to give users a slightly better chance of debugging problems.

> > [... the authors of clearcase] have the funny habit of
> > distributing their kernel modules as ".ko" files instead of
> > sending a proper ".o" and later link it against a wrapper.  The
> > result is, I must say, quite bad [...]  the structure is
> > corrupted.

> Please don't add hacks like that for non-GPL modules.  

Indeed, offline Matheiu elaborated on his problem, and it turns out
that good old modversions would have solved it.

> But neither should we export any tracing functionality for them.
> They're not the kind of people we want to help at all,

Making that sort of political decision is beyond my pay grade.  
I merely suggested its consideration.

> and Frank just shows once again that he should rather stay away from
> kernel stuff and keep on writing C++.

Now now, if you don't like my C++, wait till you see my Smalltalk-80.
Or are you just jealous that my initials subsume yours?

- FChE (this space for rent)

      reply	other threads:[~2006-11-29  1:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 21:54 [PATCH 3/16] LTTng 0.6.36 for 2.6.18 : Linux Kernel Markers Mathieu Desnoyers
2006-11-28  2:23 ` Frank Ch. Eigler
2006-11-28  2:33   ` Mathieu Desnoyers
2006-11-28  5:40     ` Christoph Hellwig
2006-11-29  1:06       ` Frank Ch. Eigler [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=20061129010631.GD8910@redhat.com \
    --to=fche@redhat.com \
    --cc=akpm@osdl.org \
    --cc=compudj@krystal.dyndns.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.