From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Adrian Bunk <bunk@stusta.de>,
lksctp-developers@lists.sourceforge.net,
Gabriel C <nix.or.die@googlemail.com>,
"Nelson, Shannon" <shannon.nelson@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [Lksctp-developers] __unsafe() usage
Date: Wed, 25 Jul 2007 10:55:46 -0400 [thread overview]
Message-ID: <46A76472.1060204@hp.com> (raw)
In-Reply-To: <1185316027.1803.351.camel@localhost.localdomain>
Rusty Russell wrote:
> On Tue, 2007-07-24 at 09:05 -0400, Vlad Yasevich wrote:
>> Please don't remove module_exit point for SCTP. Simply removing the __unsafe() call will
>> be sufficient.
>>
>> The code has recently been cleaned up to allow safe unloading and I working on final
>> cleanups. It currently works correctly with forced unloading.
>
> Thanks Vlad!
>
> I think that's everyone...
Acked-by: Vlad Yasevich <vladislav.yasevich@hp.com>
prev parent reply other threads:[~2007-07-25 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46A3FE3E.20300@googlemail.com>
2007-07-23 1:15 ` drivers/dma/ioatdma.c - address of '__this_module' will always evaluate as 'true' , warning Gabriel C
2007-07-23 16:05 ` Nelson, Shannon
2007-07-23 16:36 ` Gabriel C
2007-07-23 19:17 ` Nelson, Shannon
2007-07-23 17:59 ` __unsafe() usage Adrian Bunk
2007-07-23 23:16 ` Rusty Russell
2007-07-23 23:40 ` Nelson, Shannon
2007-07-23 23:42 ` Dan Williams
2007-07-24 13:05 ` [Lksctp-developers] " Vlad Yasevich
2007-07-24 22:27 ` Rusty Russell
2007-07-25 14:55 ` Vlad Yasevich [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=46A76472.1060204@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=nix.or.die@googlemail.com \
--cc=rusty@rustcorp.com.au \
--cc=shannon.nelson@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