From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Mark Lord <liml@rtr.ca>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH pata-2.6] cmd64x: procfs code fixes/cleanups (take 2)
Date: Mon, 16 Apr 2007 16:15:21 +0400 [thread overview]
Message-ID: <462368D9.8060407@ru.mvista.com> (raw)
In-Reply-To: <46215347.2000403@rtr.ca>
Hello.
Mark Lord wrote:
>>>> - 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].
> We normally name things with a combination of brand and chip number.
> Lots of companies could have chips with PCI in the name,
> but the CMD64x designator makes it quite clear what we're dealing with
> here.
Note that I'm only changing designator in the procfs output, i.e. not something important to end user.
> In the machines I have here with these chips,
> they are clearly labelled as "CMD" and then "PCI646.."
Although I've never seen the chip, I guess that should be logo, not the name.
> -ml
MBR, Sergei
next prev parent reply other threads:[~2007-04-16 12:14 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
2007-04-14 22:18 ` Mark Lord
2007-04-16 12:15 ` Sergei Shtylyov [this message]
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=462368D9.8060407@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=liml@rtr.ca \
--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.