From: "Stefan Völkel" <stefan.voelkel@millenux.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Heiko Carstens <Heiko.Carstens@de.ibm.com>
Subject: Re: Patch: s390 root on scsi disc
Date: Sat, 19 Jun 2004 16:39:00 +0000 [thread overview]
Message-ID: <1087663139.26437.43.camel@localhost> (raw)
In-Reply-To: <20040619142738.GA6062@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Sat, 2004-06-19 at 14:27, Christoph Hellwig wrote:
> --- zfcp_aux.c.orig 2004-06-19 16:01:25.000000000 +0000
> +++ zfcp_aux.c 2004-06-19 16:00:01.000000000 +0000
> @@ -146,6 +146,17 @@
> module_param(flags_dump, uint, 0);
> #endif
>
> +#ifndef MODULE
> +/* remember kernel boot time parameter */
> +static int __init zfcp_device(char *str)
> +{
> + device = str;
> + return 1;
> +}
> +
> +__setup("zfcpdevice=", zfcp_device);
> +#endif
>
> please use module_param instead. still wondering why zfcp needs paramters
> anyway..
Well, my problem was that passing device=foo at boot time (zfcp compiled
into the kernel) resulted in device beeing empty. device is
module_param(device, charp, 0);
MODULE_PARM_DESC(device, "specify initial device");
regards
Stefan
--
Stefan Völkel stefan.voelkel@millenux.com
Millenux GmbH mobile: +49.170.79177.17
Lilienthalstraße 2 phone: +49.711.88770.300
70825 Stuttgart-Korntal fax: +49.711.88770.349
-= linux without limits -=- http://linux.zSeries.org/ =-
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-19 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 16:13 Patch: s390 root on scsi disc Stefan Völkel
2004-06-19 14:27 ` Christoph Hellwig
2004-06-19 16:39 ` Stefan Völkel [this message]
2004-06-19 14:52 ` Christoph Hellwig
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=1087663139.26437.43.camel@localhost \
--to=stefan.voelkel@millenux.com \
--cc=Heiko.Carstens@de.ibm.com \
--cc=hch@infradead.org \
--cc=linux-scsi@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.