From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH pata-2.6] cmd64x: procfs code fixes/cleanups (take 2)
Date: Sun, 15 Apr 2007 00:16:47 +0400 [thread overview]
Message-ID: <462136AF.9060505@ru.mvista.com> (raw)
In-Reply-To: <200704142011.l3EKBBhf025590@harpo.it.uu.se>
Hello.
Mikael Pettersson wrote:
>>While at it, also perform the following cleanups:
> ...
>>- correct the chipset names (from CMDxxx to PCI-xxx)
> Please explain why this rename is a correction.
Because the chips are officially named PCI064[036] and PCI-64[89].
> Did the company making these chips change name at some point?
> Or did they change the names of the chips?
It's just that Linux named them differently.
> CMD64x is an established name, while PCI-xxx is something
> I've never heard of (and it sounds awfully generic).
Specs are available from http://gkernel.sourceforge.net/specs/ -- you can see the names on the first pages.
> /Mikael
MBR, Sergei
next prev parent reply other threads:[~2007-04-14 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 20:11 [PATCH pata-2.6] cmd64x: procfs code fixes/cleanups (take 2) Mikael Pettersson
2007-04-14 20:16 ` Sergei Shtylyov [this message]
2007-04-14 22:18 ` Mark Lord
2007-04-16 12:15 ` Sergei Shtylyov
2007-04-17 17:59 ` Mark Lord
2007-04-17 18:04 ` Sergei Shtylyov
2007-04-17 14:07 ` Alan Cox
2007-04-17 14:09 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2007-02-03 20:09 [PATCH] (2.6.20-rc7) cmd64x: fix PIO mode setup Sergei Shtylyov
2007-02-03 21:04 ` [PATCH] (2.6.20-rc7) cmd64x: fix PIO mode setup (take 2) Sergei Shtylyov
2007-02-15 19:17 ` [PATCH] (pata-2.6 fix queue) cmd64x: procfs code fixes/cleanups Sergei Shtylyov
2007-04-14 19:41 ` [PATCH pata-2.6] cmd64x: procfs code fixes/cleanups (take 2) Sergei Shtylyov
2007-04-23 21:58 ` 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=462136AF.9060505@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.