From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: danieltaylor@acm.org
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [Fwd: Re: How to get rid of unused data in LKM]
Date: Thu, 25 Jul 2002 11:55:11 +0200 [thread overview]
Message-ID: <3D3FCAFF.1030302@esd-electronics.com> (raw)
In-Reply-To: 3D3FBFBE.9050607@attbi.com
Hi Dan,
that's a better idea. I think I will do that if there is no way to free
the firmware data from my module.
I found a little code snippet to do kernel file access. It does not seem to be that complicated.
Thanks
Matthias
> Couldn't you do a kernel file open during module_init, store the
> PCI device code and close the file?
>
> Regards,
>
> Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-25 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 9:07 [Fwd: Re: How to get rid of unused data in LKM] Dan Taylor
2002-07-25 9:55 ` Matthias Fuchs [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=3D3FCAFF.1030302@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=danieltaylor@acm.org \
--cc=linuxppc-embedded@lists.linuxppc.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).