All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Module parameters reimplementation 0/4
Date: Wed, 13 Nov 2002 23:16:52 -0500	[thread overview]
Message-ID: <3DD323B4.6080404@pobox.com> (raw)
In-Reply-To: <20021114032456.3337E2C057@lists.samba.org>

Rusty Russell wrote:

> Finally, if you do not use your own types, PARAM() can be #defined
> into a MODULE_PARM statement for 2.4 kernels (ie. backwards
> compatible).  Patch 4/4 also translates old-style MODULE_PARM() into
> PARAMs at load time, for existing modules.



Let's be more friendly to the namespace and call it something less 
ambiguous, like MODULE_PARAM, even if that might not be strictly true in 
1% of the cases.  IMO there are certainly valid local uses of 'PARAM' in 
kernel code.

You can see from the totally gratuitous patch to 
include/asm-i386/setup.h which should have been a clue...

If this was C++ we could just stick PARAM in the "rusty" namespace and 
be done with it, but such as things are......  ;-)

	Jeff




  reply	other threads:[~2002-11-14  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  4:23 [PATCH] Module parameters reimplementation 0/4 Rusty Russell
2002-11-14  4:16 ` Jeff Garzik [this message]
2002-11-14  5:45   ` Rusty Russell
2002-11-14 15:03 ` Andrey Panin
2002-11-14 17:35   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 12:39 Matthew Wilcox
2002-11-14 17:33 ` 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=3DD323B4.6080404@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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 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.