public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [PATCH] convert scsi core to use module_param interfaces
Date: Fri, 6 Jun 2003 07:37:32 +0100	[thread overview]
Message-ID: <20030606073732.B13259@infradead.org> (raw)
In-Reply-To: <20030604145717.A8394@beaverton.ibm.com>; from patmans@us.ibm.com on Wed, Jun 04, 2003 at 02:57:17PM -0700

On Wed, Jun 04, 2003 at 02:57:17PM -0700, Patrick Mansfield wrote:
> This patch converts scsi core to use the module_param interfaces
> (except for the hosts.c scsihosts usage).
> 
> With this applied, boot time (non-module) command line setting of scsi
> parameters must be prefixed by what the scsi module name would be
> (scsi_mod), for example:
> 
> 	scsi_mod.scsi_logging_level=0x180 scsi_mod.scsi_default_dev_flags=0x1
> 	scsi_mod.max_scsi_luns=5
> 
> Usage of scsi_mod as above is a bit ugly and long - if this patch is
> applied, we should consider renaming scsi.c to scsi_main.c or similiar,
> and scsi_mod.o to scsi.o. Or, somehow get our prefix set to "scsi".

I don't think we can just change the name of the scsi core module -
to much userspace stuff is relying on that.  Changing the prefix would
be nice but I have no idea how we can do that.

We should also kill the scsi substrings in the individual options now
that we have a regular prefix, I'll submit a patch.


  reply	other threads:[~2003-06-06  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 21:57 [PATCH] convert scsi core to use module_param interfaces Patrick Mansfield
2003-06-06  6:37 ` Christoph Hellwig [this message]
2003-06-06 15:17   ` Patrick Mansfield

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=20030606073732.B13259@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox