linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 7/8] ide: make legacy IDE VLB modules check for the "probe" kernel params
Date: Wed, 14 Feb 2007 12:07:27 +0100	[thread overview]
Message-ID: <200702141207.27483.bzolnier@gmail.com> (raw)
In-Reply-To: <20070214105329.3cc6ec27@localhost.localdomain>


On Wednesday 14 February 2007 11:53, Alan wrote:
> On Wed, 14 Feb 2007 02:57:12 +0100
> Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> 
> > [PATCH] ide: make legacy IDE VLB modules check for the "probe" kernel params
> > 
> > Legacy IDE VLB host drivers didn't check for "probe" options when compiled
> > as modules, which was obviously wrong as we don't want module to poke at
> > random I/O ports by simply loading it.  Fix it by adding "probe" module param
> > to legacy IDE VLB host drivers and obsolete old "ide0=dtc2278", "ide0=ht6560b",
> > "ide0=qd65xx", "ide0=ali14xx", "ide0=umc8672" IDE driver options.
> 
> No point obsoleting the old ones. By the time being obsolete turns into
> being anything like "gone", the hardware won't exist. It just causes

We don't have stable rules for kernel parameters.

In theory they can be gone as soon as in 2.6.22 if patch hits 2.6.21
(not that I intend to do this).

> questions, confusion, noise and hassle, leave the old options be and make
> the module options work too.

I'll make warnings more verbose, i.e.

'please use "ali14xx.probe" boot option instead of obsoleted "ide0=probe"'

which should greatly help to avoid questions/confusion/noise/hassle.

Bart

  reply	other threads:[~2007-02-14 11:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  1:56 [PATCH 1/8] alim15x3: PIO fallback fix Bartlomiej Zolnierkiewicz
2007-02-14  1:56 ` [PATCH 2/8] alim15x3: use ide_tune_dma() Bartlomiej Zolnierkiewicz
2007-02-14  1:56 ` [PATCH 3/8] pdc202xx_new: " Bartlomiej Zolnierkiewicz
2007-02-14  1:56 ` [PATCH 4/8] ide: remove some obsoleted kernel params Bartlomiej Zolnierkiewicz
2007-02-14  1:56 ` [PATCH 5/8] ide: add "initializing" argument to ide_register_hw() Bartlomiej Zolnierkiewicz
2007-02-14  1:57 ` [PATCH 6/8] ide: add ide_proc_register_port() Bartlomiej Zolnierkiewicz
2007-02-14  1:57 ` [PATCH 7/8] ide: make legacy IDE VLB modules check for the "probe" kernel params Bartlomiej Zolnierkiewicz
2007-02-14 10:53   ` Alan
2007-02-14 11:07     ` Bartlomiej Zolnierkiewicz [this message]
2007-02-14 11:17       ` Alan
2007-02-14 11:19         ` Bartlomiej Zolnierkiewicz
2007-02-14 19:52         ` [PATCH 7/8] ide: make legacy IDE VLB modules check for the "probe" kernel params (v2) Bartlomiej Zolnierkiewicz
2007-02-14  1:57 ` [PATCH 8/8] ide: fix ide.c Bartlomiej Zolnierkiewicz
2007-08-18 13:50 ` [PATCH 1/8] alim15x3: PIO fallback fix Sergei Shtylyov
2007-08-18 19:18   ` Bartlomiej Zolnierkiewicz
2007-08-18 19:26     ` Sergei Shtylyov
2007-11-09 16:58   ` Sergei Shtylyov

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=200702141207.27483.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).