From: Tom Rini <trini@kernel.crashing.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 CPM DP ram free function
Date: Fri, 21 May 2004 12:23:33 -0700 [thread overview]
Message-ID: <20040521192333.GI6763@smtp.west.cox.net> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B06DADE@ismail.innsys.innovsys.com>
On Fri, May 21, 2004 at 12:35:01PM -0500, Rune Torgersen wrote:
> It adds functionality to the 8260 CPM to free() allocated host and dp
> ram memory. (nice for loadable drivers that use DP ram)
First, when this has come up in the past, the first question is why is
this useful, given that with the hardware and peripherals in question,
loadable drivers aren't really useful (and don't shoot the messenger
please).
Second, you removed the EXPORT_SYMBOL for the old alloc, but I didn't
see quickly how a module would make use of the new infrastructure since
there weren't any new EXPORT_SYMBOLs.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-21 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 17:35 8260 CPM DP ram free function Rune Torgersen
2004-05-21 19:23 ` Tom Rini [this message]
2004-05-24 13:50 ` Wolfgang Denk
2004-05-24 14:06 ` Pantelis Antoniou
2004-05-24 14:28 ` Wolfgang Denk
2004-05-24 15:24 ` Tom Rini
2004-05-21 21:44 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2004-05-21 19:34 Rune Torgersen
2004-05-21 19:50 ` Tom Rini
2004-05-21 20:16 Rune Torgersen
2004-05-21 20:26 ` Tom Rini
2004-05-21 21:41 Rune Torgersen
2004-05-21 21:52 Rune Torgersen
2004-05-24 16:03 Rune Torgersen
[not found] ` <20040524161520.GQ6763@smtp.west.cox.net>
2004-05-25 11:00 ` Dan Malek
2004-05-25 16:04 Rune Torgersen
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=20040521192333.GI6763@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=runet@innovsys.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;
as well as URLs for NNTP newsgroup(s).