From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: "Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>
Cc: "James Morris" <jmorris@namei.org>,
netdev@vger.kernel.org, "dccp (vger)" <dccp@vger.kernel.org>
Subject: Re: [PATCH] dccp: remove module exit functions
Date: Mon, 13 Nov 2006 13:41:20 +0000 [thread overview]
Message-ID: <200611131341.20676@strip-the-willow> (raw)
In-Reply-To: <39e6f6c70611101032v5f0be644ta65069cf533b3385@mail.gmail.com>
Quoting Arnaldo Carvalho de Melo:
| On 11/10/06, James Morris <jmorris@namei.org> wrote:
| > I wonder if this facility can be integrated more generally into the kernel
| > as a kernel hacking option, as this is not the only protocol which people
| > are developing.
| >
|
| See:
| http://www.erg.abdn.ac.uk/users/gerrit/dccp/patch-backlog/09a_release_ctl_socket_at_exit.diff
|
| This one requires a bit more thinking, so I'm postponing it for now to
| get the simple bits in Gerrit's patch queue cherrypicked and sent for
There is a similar problem in sctp and so it would indeed be useful to have a (configuration)
option. Without the `unload hack' there is no module unloading and that is very bad, especially
since DCCP development is likely to continue (there is no single consistent, full DCCP implementation
yet, so testing will be one prime activity).
next prev parent reply other threads:[~2006-11-13 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 8:48 [PATCH] dccp: remove module exit functions James Morris
2006-11-10 13:55 ` Arnaldo Carvalho de Melo
2006-11-10 16:24 ` James Morris
2006-11-10 16:27 ` James Morris
2006-11-10 18:32 ` Arnaldo Carvalho de Melo
2006-11-13 13:41 ` Gerrit Renker [this message]
2006-11-14 0:49 ` David Miller
2006-11-14 14:11 ` Arnaldo Carvalho de Melo
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=200611131341.20676@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=arnaldo.melo@gmail.com \
--cc=dccp@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).