public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tejun Heo <tj@home-tj.org>
Cc: mochel@osdl.org,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH] Per-device parameter support (11/16)
Date: Mon, 25 Oct 2004 14:57:29 +1000	[thread overview]
Message-ID: <1098680249.8098.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20041023043040.GL3456@home-tj.org>

On Sat, 2004-10-23 at 13:30 +0900, Tejun Heo wrote:
>  dp_11_module_param_arr.diff
> 
>  This is the 11st patch of 16 patches for devparam.
> 
>  The unsigned int * @nump of module_param_array is changed back to
> unsigned int @num, and new sets of macros named module_param_arr*()
> are added.  These new macros don't take the num argument.  This change
> is made for two reasons
> 
>  1. To be consistent with devparam macros.  In devparam, we'll be
>     using field name of struct elements, so we won't be able to use
>     pointer argument.
>  2. It's more consistent with other moduleparam macros.
> 
>  This patch only modifies moduleparam.h and doesn't modify the users
> of the modified macros.  The next patch takes care of that.  This and
> the next patch (dp_12_module_param_arr_apply.diff) are optional.

It's finely balanced, but the module_param macro only skips the "&"
because it turns it into a name.  module_param_named() should probably
be changed to take a ptr too.  But you'll get a warning if you use the
interface wrong, so it's not a huge issue.

The balance is tipped here I think because the massive number of
functions we're starting to sprout into.

Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman


      reply	other threads:[~2004-10-25  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23  4:30 [RFC/PATCH] Per-device parameter support (11/16) Tejun Heo
2004-10-25  4:57 ` Rusty Russell [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=1098680249.8098.31.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=tj@home-tj.org \
    /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