From: Domen Puncer <domen.puncer@telargo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Problem in compiling a kernel module
Date: Wed, 14 Mar 2007 07:54:11 +0100 [thread overview]
Message-ID: <20070314065411.GD14658@moe.telargo.com> (raw)
In-Reply-To: <20070314043305.GB27011@server.idefix.lan>
On 14/03/07 05:33 +0100, Matthias Fechner wrote:
> Hello Ben,
>
> * Ben Warren <bwarren@qstreams.com> [13-03-07 05:55]:
> > Is there any chance that you qualify private data as
> > __init within the driver? Can you post the cleanup()
> > function and any private (static) functions that it
> > calls?
>
> no problem, I attached the file. It is bery basic from now and it is
> not written very well, but it should have all necessary parts in it.
>
> PS: It's not necessary to CC me I'm on the list :)
>
...
> static int __initdata max6633_initialized = 0;
__initdata
>
> void max6633_cleanup(void)
> {
> int res;
> if(max6633_initialized==1)
But you access it from non-init code.
Domen
next prev parent reply other threads:[~2007-03-14 6:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 17:00 Problem in compiling a kernel module Matthias Fechner
2007-03-12 18:36 ` Grant Likely
2007-03-13 4:30 ` Matthias Fechner
2007-03-13 4:55 ` Grant Likely
2007-03-13 12:55 ` Ben Warren
2007-03-14 4:33 ` Matthias Fechner
2007-03-14 6:54 ` Domen Puncer [this message]
2007-03-15 4:27 ` Matthias Fechner
2007-08-07 17:42 ` Fedora 7 on a non FPU system Michael Brian Willis
2007-08-07 19:11 ` Roland Dreier
2007-08-07 19:29 ` Josh Boyer
2007-08-07 21:43 ` Clemens Koller
2007-08-08 22:18 ` Michael Brian Willis
-- strict thread matches above, loose matches on Subject: below --
2011-07-10 4:37 Problem in compiling a kernel module Ponkumaran Annadurai
2011-07-10 5:33 ` Prashant Shah
2011-07-10 6:06 ` Ponkumaran Annadurai
2011-07-10 6:14 ` Prashant Shah
2011-07-10 6:18 ` Prashant Shah
2011-07-10 6:45 ` Prashant Shah
2011-07-10 6:54 ` Ponkumaran Annadurai
2011-07-10 16:39 ` Niamathullah sharief
2011-07-10 16:59 ` Ponkumaran Annadurai
2011-07-10 17:25 ` Prashant Shah
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=20070314065411.GD14658@moe.telargo.com \
--to=domen.puncer@telargo.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.