From: Marc Koschewski <marc@osknowledge.org>
To: linux-kernel@vger.kernel.org
Subject: [QUESTION] Your way doing kernel/module development
Date: Sat, 11 Feb 2006 16:42:06 +0100 [thread overview]
Message-ID: <20060211154206.GD5721@stiffy.osknowledge.org> (raw)
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
next reply other threads:[~2006-02-11 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 15:42 Marc Koschewski [this message]
2006-02-11 21:33 ` [QUESTION] Your way doing kernel/module development Jim Crilly
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=20060211154206.GD5721@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=linux-kernel@vger.kernel.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.