public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Willem Riede <wrlk@riede.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Selective attach for ide-scsi
Date: Wed, 11 Feb 2004 12:11:20 -0800	[thread overview]
Message-ID: <20040211121120.A24289@beaverton.ibm.com> (raw)
In-Reply-To: <20040210000205.GG28026@serve.riede.org>; from wrlk@riede.org on Mon, Feb 09, 2004 at 07:02:05PM -0500

On Mon, Feb 09, 2004 at 07:02:05PM -0500, Willem Riede wrote:
> On 2004.02.09 03:24, Mikael Pettersson wrote:
> > Willem Riede writes:

> > The patch I posted, which you apparently didn't like, doesn't
> > require the use of boot-only options: it instead adds a module_param
> > to ide-scsi which allows for greater flexibility.
> > 
> > Personally I never liked that butt-ugly hdX=ide-scsi hack.
> 
> I hear you. There are certainly advantages to use a module parameter rather
> than a boot argument.

But module_param allows module arguments when built as a module, and boot
arguments when built into the kernel.

> However, there should not be two mechanisms to achieve the same goal. For
> better or for worse, the hdX=<driver> construction exists, and people are
> using it. Its use is not limited to ide-scsi.

So does module_param not work because the usage is across modules? That
seems odd.

-- Patrick Mansfield

  reply	other threads:[~2004-02-11 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08 22:42 [PATCH] Selective attach for ide-scsi Willem Riede
2004-02-09  8:24 ` Mikael Pettersson
2004-02-10  0:02   ` Willem Riede
2004-02-11 20:11     ` Patrick Mansfield [this message]
2004-02-14 22:06       ` Willem Riede
2004-02-14 22:54         ` Bartlomiej Zolnierkiewicz
2004-02-14 23:03           ` Willem Riede

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=20040211121120.A24289@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=wrlk@riede.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