From: Rusty Russell <rusty@rustcorp.com.au>
To: Takao Indoh <indou.takao@jp.fujitsu.com>
Cc: rostedt@goodmis.org, masami.hiramatsu.pt@hitachi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module: Introduce MODULE_STATE_COMING_FINAL to avoid ftrace warning
Date: Tue, 22 Apr 2014 16:20:05 +0930 [thread overview]
Message-ID: <874n1lj1sy.fsf@rustcorp.com.au> (raw)
In-Reply-To: <534B4CB5.9010401@jp.fujitsu.com>
Takao Indoh <indou.takao@jp.fujitsu.com> writes:
> ping, any comments?
Sorry, was away on paternity leave.
I prefer to mark NX before changing the module to MODULE_STATE_COMING,
but perhaps that will break everyone else?
See my reply to the other thread.
Thanks,
Rusty.
prev parent reply other threads:[~2014-04-22 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 7:54 [PATCH] module: Introduce MODULE_STATE_COMING_FINAL to avoid ftrace warning Takao Indoh
2014-04-02 12:36 ` Steven Rostedt
2014-04-14 2:49 ` Takao Indoh
2014-04-14 4:09 ` Masami Hiramatsu
2014-04-14 13:48 ` Steven Rostedt
2014-04-22 6:50 ` 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=874n1lj1sy.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=indou.takao@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=rostedt@goodmis.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