From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Daniel McNeil <daniel@osdl.org>
Cc: "netdev@oss.sgi.com" <netdev@oss.sgi.com>,
davem@redhat.com, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@intercode.com.au
Subject: Re: [PATCH 2.5.69] net/ipv6 missing kmem_cache_destroy in module exit
Date: Tue, 13 May 2003 23:46:29 -0300 [thread overview]
Message-ID: <20030514024629.GF28128@conectiva.com.br> (raw)
In-Reply-To: <1052864772.2442.8.camel@ibm-c.pdx.osdl.net>
Em Tue, May 13, 2003 at 03:26:13PM -0700, Daniel McNeil escreveu:
> ipv6 is missing the calls to kmem_cache_destory() in module_exit
> and some cleanup routines.
Thanks, this was overlooked because IPv6 doesn't unloads 8) But this may
well change if we get to some solution to the complex subsystem module handling
that is being discussed recently.
- Arnaldo
prev parent reply other threads:[~2003-05-14 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 22:26 [PATCH 2.5.69] net/ipv6 missing kmem_cache_destroy in module exit Daniel McNeil
2003-05-13 23:59 ` David S. Miller
2003-05-14 2:46 ` Arnaldo Carvalho de Melo [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=20030514024629.GF28128@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=daniel@osdl.org \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.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;
as well as URLs for NNTP newsgroup(s).