From mboxrd@z Thu Jan  1 00:00:00 1970
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
Date: Mon, 18 Apr 2011 00:14:08 +0700
Subject: Unable to remove kernel module showing permanent using lsmod
In-Reply-To: <BANLkTinx=5LT4SS_HmoAZD13goAuK0zTtw@mail.gmail.com>
References: <AANLkTi=0sakZeHHsZufAv3B3d_PUO-aLU+jSEJhH8Ebj@mail.gmail.com>
	<BANLkTinx=5LT4SS_HmoAZD13goAuK0zTtw@mail.gmail.com>
Message-ID: <BANLkTim+v8SXFtP7rhALK5xBZqw+Pb6G1g@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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