From: Rusty Russell <rusty@rustcorp.com.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>,
linux-kernel@vger.kernel.org, fweisbec@gmail.com,
mingo@redhat.com
Subject: Re: [PATCH] Delegate unknown module parameters to interested parties
Date: Wed, 10 Nov 2010 16:21:28 +1030 [thread overview]
Message-ID: <201011101621.28946.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1289313561.12418.96.camel@gandalf.stny.rr.com>
On Wed, 10 Nov 2010 01:09:21 am Steven Rostedt wrote:
> [ Added Rusty "Module God" Russell ]
And I also wrote the parameter parsing code, so sending to me is probably
a good idea.
So, what's this for? You want trace= as a standard module parameter
or something? If this is a once-off I'd prefer a custom hack I think.
If you can think of other users, this might be a good idea; though don't
use "void *data" use an explicit struct module *...
Cheers,
Rusty.
next prev parent reply other threads:[~2010-11-10 5:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 9:12 [PATCH 1/4] tracing: introduce for_each_token macro Yuanhan Liu
2010-11-09 9:12 ` [PATCH 2/4] tracing: introduce trace_set_clr_module_event Yuanhan Liu
2010-11-09 11:23 ` Yuanhan Liu
2010-11-09 11:27 ` Chris Wilson
2010-11-09 13:20 ` Yuanhan Liu
2010-11-09 13:31 ` Chris Wilson
2010-11-09 13:56 ` Steven Rostedt
2010-11-09 14:06 ` Yuanhan Liu
2010-11-09 13:59 ` Yuanhan Liu
2010-11-09 14:01 ` Steven Rostedt
2010-11-09 14:11 ` [PATCH] Delegate unknown module parameters to interested parties Chris Wilson
2010-11-09 14:39 ` Steven Rostedt
2010-11-10 5:51 ` Rusty Russell [this message]
2010-11-10 13:56 ` Steven Rostedt
2010-11-11 0:35 ` Rusty Russell
2010-11-11 1:05 ` Steven Rostedt
2010-11-09 9:12 ` [PATCH 3/4] tracing: update trace-events-sample.c Yuanhan Liu
2010-11-09 9:12 ` [PATCH 4/4] tracing: update the trace/events.txt documentation Yuanhan Liu
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=201011101621.28946.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=chris@chris-wilson.co.uk \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yuanhan.liu@linux.intel.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