From: Jeff Garzik <jeff@garzik.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: albertl@mail.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata passthru: support PIO multi commands
Date: Wed, 13 Jun 2007 14:55:06 -0400 [thread overview]
Message-ID: <46703D8A.4040403@garzik.org> (raw)
In-Reply-To: <46703DB1.9010702@ru.mvista.com>
Sergei Shtylyov wrote:
> This is generally a bad practice to guess protocol based on opcode.
> What if the code will have to handle a vendor unique command (or some
> other command not yet known to it but known to issuer)?
Agreed -- we simply cannot rely on guessing protocol from opcode, we
MUST take the protocol that is specified.
Jeff
prev parent reply other threads:[~2007-06-13 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706112200.l5BM0qFn005767@hera.kernel.org>
[not found] ` <20070611233917.4bd8c6d7@the-village.bc.nu>
[not found] ` <466DE438.70108@garzik.org>
[not found] ` <20070612111621.10074408@the-village.bc.nu>
2007-06-12 15:18 ` libata passthru: support PIO multi commands Jeff Garzik
2007-06-12 16:05 ` Alan Cox
2007-06-13 2:57 ` Albert Lee
2007-06-13 18:40 ` Mark Lord
2007-06-13 18:55 ` Sergei Shtylyov
2007-06-13 18:55 ` Jeff Garzik [this message]
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=46703D8A.4040403@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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).