From: Takashi Iwai <tiwai@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Ville Syrjala <syrjala@sci.fi>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alessandro Rubini <rubini@ipvvis.unipv.it>,
Michal Januszewski <spock@gentoo.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
linux-input@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/8] param: use ops in struct kernel_param, rather than get and set fns directly
Date: Fri, 30 Oct 2009 11:18:12 +0100 [thread overview]
Message-ID: <s5hvdhxyyl7.wl%tiwai@suse.de> (raw)
In-Reply-To: <20091022142337.EC4A85362F@mx1.suse.de>
At Fri, 23 Oct 2009 00:51:28 +1030,
Rusty Russell wrote:
>
> This is more kernel-ish, saves some space, and also allows us to
> expand the ops without breaking all the callers who are happy for the
> new members to be NULL.
>
> The few places which defined their own param types are changed to the
> new scheme.
>
> Since we're touching them anyway, we change get and set to take a
> const struct kernel_param (which they were, and will be again).
>
> To reduce churn, module_param_call creates the ops struct so the callers
> don't have to change (and casts the functions to reduce warnings).
> The modern version which takes an ops struct is called module_param_cb.
This is nice, as it also reduces the size of struct kernel_param, so
each parameter uses less footprint (who cares, though?) :)
But, just wondering whether we still need to export get/set
functions. They can be called from ops now, so if any, it can be
defined even as an inlinefunction or a macro.
thanks,
Takashi
next parent reply other threads:[~2009-10-30 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091022142337.EC4A85362F@mx1.suse.de>
2009-10-30 10:18 ` Takashi Iwai [this message]
2009-10-30 11:13 ` [PATCH 2/8] param: use ops in struct kernel_param, rather than get and set fns directly Rusty Russell
2009-11-01 10:26 ` Takashi Iwai
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=s5hvdhxyyl7.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=rubini@ipvvis.unipv.it \
--cc=rusty@rustcorp.com.au \
--cc=spock@gentoo.org \
--cc=syrjala@sci.fi \
/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