From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH UPDATED] libata: add support for ATA_16 on ATAPI
Date: Thu, 02 Aug 2007 08:01:12 -0400 [thread overview]
Message-ID: <46B1C788.3060201@rtr.ca> (raw)
In-Reply-To: <46B09494.4080206@gmail.com>
Tejun Heo wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> Jeff, Mark, are you guys okay with the modified version?
>> Close! Thanks for revising!
>>
>> My only comment now is that I dislike atapi_scmd85. That means nothing
>> to me.
>>
>> I liked the old name better. Or maybe use atapi_passthru16.
>
> The problem with ata16_passthru is that it suggests the opposite of what
> it does. The default value 0 allows ATA_16 passthrough command while
> setting it to 1 disallows ATA_16 passthrough and passes through SCSI
> Command 0x85 which shares command byte with ATA_16. Maybe it's because
> I'm not a native speaker but the last sentence is pretty difficult to
> digest. So, IMHO, atapi_scmd85 is slightly better in that it means
> nothing rather than suggesting the opposite.
Thanks for plugging away at this one, Tejun.
And I do agree that ata16_passthru sounds backwards of what it really does.
There's got to be a nicer name for this thing.
In practice, I doubt that anyone will ever use the parameter,
so it really doesn't matter a whole lot what we call it.
But something sensible would be nice.
There's got to be a shorter version of "atapi_pass_opcode_0x85_to_device=1".
Perhaps "atapi_op_85_passthru=1" or "atapi_passthru_op_85=1" ??
Also, this is an example of something that is really a "per device"
parameter, rather than a global. But we haven't yet cracked a good way
to do that yet in libata.
Cheers
next prev parent reply other threads:[~2007-08-02 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 7:56 [PATCH UPDATED] libata: add support for ATA_16 on ATAPI Tejun Heo
2007-08-01 14:00 ` Jeff Garzik
2007-08-01 14:11 ` Tejun Heo
2007-08-02 12:01 ` Mark Lord [this message]
2007-08-07 16:08 ` [PATCH RE-UPDATED] " Tejun Heo
2007-08-15 7:23 ` Jeff Garzik
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=46B1C788.3060201@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).