[QUESTION] Your way doing kernel/module development

I'd like to get some short but, however, fully descriptive statements about how
you do your module development. I mean, what your way of doing coding,
insmod-ing, rmmod-ing, ... And what about code, that cannot be <M>, just [*] or
must-be-built-in.

Hm, actually there's nothing more to say. Except that I'm tired of rebooting. ;)
I tried kexec() but somehow I dont have all IDE devices sometimes on 'kexec -e'.
So this just not a solution for me... :)

Marc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [QUESTION] Your way doing kernel/module development
    • From: Jim Crilly <[email protected]>

• Prev by Date: Re: [BUG GIT] Unable to handle kernel paging request at virtual address e1380288
• Next by Date: Re: CD-blanking leads to machine freeze with current -git
• Previous by thread: [PATCH] matrox maven: memory allocation and other cleanups
• Next by thread: Re: [QUESTION] Your way doing kernel/module development
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]