From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: More IDE hackery
Date: Wed, 03 Nov 2004 17:08:35 +0000 [thread overview]
Message-ID: <1099501714.29846.71.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e04110309146ad102fc@mail.gmail.com>
> It won't work unless you modify ide_register_hw().
> See ide_register_hw() vs "initializing == 1".
I changed that to allow a fixup to be passed as well. That causes most
of the noise changes but I could make that ide_register_hw_with_fixup()
to avoid changes elsewhere adding NULL to ide_register_hw calls. Which
would you prefer and I'll go make full patches
> + /* Has a serial number but is warped */
> + if (!strstr(drive0->id->model, "Integrated Technology Express"))
> + return;
>
> This shouldn't be needed now, no?
Probably not.
next prev parent reply other threads:[~2004-11-03 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 13:16 More IDE hackery Alan Cox
2004-11-03 17:14 ` Bartlomiej Zolnierkiewicz
2004-11-03 17:08 ` Alan Cox [this message]
2004-11-03 20:17 ` Bartlomiej Zolnierkiewicz
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=1099501714.29846.71.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--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).