From: Ankita Garg <ankita@in.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] lkdtm: cleanup headers and module_param/MODULE_PARM_DESC
Date: Thu, 26 Oct 2006 09:43:41 +0530 [thread overview]
Message-ID: <20061026041341.GA6562@in.ibm.com> (raw)
In-Reply-To: <20061023200645.1657b7ab.randy.dunlap@oracle.com>
Hi,
> #include <linux/kernel.h>
> +#include <linux/fs.h>
> #include <linux/module.h>
> +#include <linux/buffer_head.h>
> #include <linux/kprobes.h>
> -#include <linux/kallsyms.h>
> +#include <linux/list.h>
> #include <linux/init.h>
> -#include <linux/irq.h>
> #include <linux/interrupt.h>
> +#include <linux/hrtimer.h>
> #include <scsi/scsi_cmnd.h>
Why does the module require fs.h, hrtimer.h, list.h and buffer_head.h? It works fine for me without these header files. I do not get any gcc warning. Moreover, I found that even init.h and interrupt.h are also not required.
> +MODULE_PARM_DESC(cpoint_name, " Crash Point, where kernel is to be crashed");
> +module_param(cpoint_type, charp, 0644);
> +MODULE_PARM_DESC(cpoint_type, " Crash Point Type, action to be taken on "\
> + "hitting the crash point");
> +module_param(cpoint_count, int, 0644);
> +MODULE_PARM_DESC(cpoint_count, " Crash Point Count, number of times the "\
^^not required now!
> + "crash point is to be hit to trigger action");
>
Thanks for fixing the typo.
> ---
> ~Randy
--
Ankita Garg
Linux Technology Center
next prev parent reply other threads:[~2006-10-26 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 3:06 [PATCH] lkdtm: cleanup headers and module_param/MODULE_PARM_DESC Randy Dunlap
2006-10-26 4:13 ` Ankita Garg [this message]
2006-10-26 4:50 ` Randy.Dunlap
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=20061026041341.GA6562@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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