From: runcoderen <runcoderzhcn@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ldd scull_load question
Date: Sun, 05 Sep 2010 09:01:55 +0800 [thread overview]
Message-ID: <1283648515.1741.8.camel@bencharluo-laptop> (raw)
In-Reply-To: <20100904174308.409c070e.rdunlap@xenotime.net>
yes, you do!
there is another question confused me.
I have seem the command in the scull.c:
int scull_major = SCULL_MAJOR;and so on.
module_param(scull_major, int, S_IRUGO); and so on.
if we don't do "./scull_load scull_major" command.
we just use "./scull_load"
it will make scull_major = SCULL_MAJOR default?
在 2010-09-04六的 17:43 -0700,Randy Dunlap写道:
> On Sun, 05 Sep 2010 08:35:14 +0800 runcoderen wrote:
>
> > hi all:
> > I am reading ldd(3rd).
> > when I read the scull_load part.
> > I can't understand some special sentences in the scripts as follows:
> >
> > /sbin/insmod ./$module.ko $* || exit 1
> >
> > why we add $* and || exit 1 after /sbin/insmod ./$module.ko?
> >
> > can anyone help me to understand?
>
> "$*" passes all parameters of the script to the module as module parameters.
>
> "insmod module.ko || exit 1"
>
> means "if insmod is successful (no error), then the command is finished,
> otherwise exit with an error code of 1."
>
> Does that help?
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
--
/****************************************
http://runcoderen.wordpress.com
****************************************/
next prev parent reply other threads:[~2010-09-05 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:20 [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops Nicholas A. Bellinger
2010-09-02 5:56 ` Konrad Rzeszutek Wilk
2010-09-02 19:19 ` Nicholas A. Bellinger
2010-09-04 23:53 ` Nicholas A. Bellinger
2010-09-05 0:35 ` ldd scull_load question runcoderen
2010-09-05 0:43 ` Randy Dunlap
2010-09-05 1:01 ` runcoderen [this message]
2010-09-05 21:20 ` Randy Dunlap
2010-09-05 3:21 ` Adam Jiang
2010-09-07 20:56 ` [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops Konrad Rzeszutek Wilk
2010-09-08 1:44 ` Nicholas A. Bellinger
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=1283648515.1741.8.camel@bencharluo-laptop \
--to=runcoderzhcn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®