From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Brett Russ <russb@emc.com>, Jeff Garzik <jgarzik@pobox.com>,
Chris Hann <chann94501@yahoo.com>,
linux-ide list <linux-ide@vger.kernel.org>
Subject: Re: hdregs.h puts csfo at word 129 - wrong, that's vendor specific
Date: Sun, 27 Mar 2005 14:58:48 +0100 [thread overview]
Message-ID: <1111931927.14877.309.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e050325180159d5fbb1@mail.gmail.com>
> AFAIR it was Alan who added this code, so lets ask him :)
The cfso check goes back to Andre
next prev parent reply other threads:[~2005-03-27 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 1:28 hdregs.h puts csfo at word 129 - wrong, that's vendor specific Chris Hann
2005-03-25 3:03 ` Jeff Garzik
2005-03-26 1:48 ` Brett Russ
2005-03-26 2:01 ` Bartlomiej Zolnierkiewicz
2005-03-27 13:58 ` Alan Cox [this message]
2005-04-13 22:18 ` Brett Russ
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=1111931927.14877.309.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=chann94501@yahoo.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=russb@emc.com \
/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).