kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unable to remove kernel module showing permanent using lsmod
Date: Mon, 18 Apr 2011 00:14:08 +0700	[thread overview]
Message-ID: <BANLkTim+v8SXFtP7rhALK5xBZqw+Pb6G1g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinx=5LT4SS_HmoAZD13goAuK0zTtw@mail.gmail.com>

On Sun, Apr 17, 2011 at 13:19, sakthi selvam <sakthi.cdm@gmail.com> wrote:
> Dear all,
>
> ??????????????? Thanks for your suggestion. Finally, I identified the
> solution for the permanent issued I faced after loading my kernel module.
> The solution is the kernel macro; 'USE_IMMEDIATE' has to be defined (to be
> given as -DUSE_IMMEDIATE along with compiler flags) during compilation of my
> module.

Great! :)

Well, I think this is what this list for...to help someone able to
solve his/her own problem... and for sure, you learn something :)

Regarding the macro, I never read about that before...quite likely
that's an internal "define" block that enable a block of code (ala "if
define then....")..and it seems, that's somewhat critical...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2011-04-17 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  5:08 Unable to remove kernel module showing permanent using lsmod sakthi selvam
2011-03-24  6:38 ` Mulyadi Santosa
2011-03-24  7:47   ` Kacrut
2011-03-24 15:05     ` Greg KH
2011-03-25  3:21 ` Dave Hylands
2011-04-17  6:19 ` sakthi selvam
2011-04-17 17:14   ` Mulyadi Santosa [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=BANLkTim+v8SXFtP7rhALK5xBZqw+Pb6G1g@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).