The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: John Levon <levon@movementarian.org>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Add module load profile hook
Date: Tue, 25 Feb 2003 12:25:23 +1100	[thread overview]
Message-ID: <20030225012823.4FA342C0BA@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 24 Feb 2003 17:16:57 -0000." <20030224171657.GA96095@compsoc.man.ac.uk>

In message <20030224171657.GA96095@compsoc.man.ac.uk> you write:
> So you'll add code in case somebody might want it, but you refuse to fix
> regressions wrt the old code because it's a "corner case" (as if corner
> cases isn't exactly what makes things complicated) ? How odd :)

You still complaining about not stashing the full path name of the
module somewhere in the kernel?

That would be because that was a HACK, and it's my job to say "no",
even when that means we're not "feature complete" by someone's
definition.

You seem to have taken the politeness of my previous response as an
indication of uncertainty.  I am sorry if I gave that impression,
allow me to translate it into Torvaldsian:

	Your patch added a specific "profile_module_loaded()" call
	which did nothing but call a notifier.  Just call a damn
	notifier directly, which is more obvious, more flexible, less
	code and more expandable, and doesn't give you a black star
	for being stupid.

Or, in Viroese, "Vetoed".

Hope that helps 8)
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-02-25  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 21:53 [PATCH] Add module load profile hook John Levon
2003-02-21  0:33 ` Rusty Russell
2003-02-21  0:54   ` John Levon
2003-02-24  0:33     ` Rusty Russell
2003-02-24 17:16       ` John Levon
2003-02-25  1:25         ` Rusty Russell [this message]
2003-02-25  2:58           ` John Levon
2003-02-25  8:07             ` Rusty Russell

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=20030225012823.4FA342C0BA@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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