From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Igor Pylypiv <ipylypiv@google.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
stable@vger.kernel.org, Stephan Eisvogel <eisvogel@seitics.de>,
Christian Heusel <christian@heusel.eu>,
linux-ide@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] ata: libata-core: Return sense data in descriptor format by default
Date: Mon, 12 Aug 2024 15:23:28 -0400 [thread overview]
Message-ID: <yq1ikw5zgx5.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <ZrpXu_vfI-wpCFVc@ryzen.lan> (Niklas Cassel's message of "Mon, 12 Aug 2024 20:43:07 +0200")
Niklas,
> My personal feeling is that passthrough commands should simply follow
> the storage standard exactly, and if a user space application does
> adhere to the standard, tough luck, why are you using passthrough
> commands instead of regular commands then? Passthrough commands by
> definition follow a specific storage standard, and not the Linux
> kernel block layer API.
Yeah. I'm not sure how much of a problem non-ATA passthrough is for
libata-attached devices. But it does seem messy that userland is making
these kinds of assumptions.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-08-12 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:15 [PATCH] ata: libata-core: Return sense data in descriptor format by default Niklas Cassel
2024-08-12 17:40 ` Christian Heusel
2024-08-12 18:43 ` Niklas Cassel
2024-08-12 18:46 ` Niklas Cassel
2024-08-12 19:23 ` Martin K. Petersen [this message]
2024-08-13 6:37 ` Hannes Reinecke
2024-08-13 9:41 ` Niklas Cassel
2024-08-13 12:15 ` Christoph Hellwig
2024-08-13 13:26 ` Niklas Cassel
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=yq1ikw5zgx5.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=cassel@kernel.org \
--cc=christian@heusel.eu \
--cc=dlemoal@kernel.org \
--cc=eisvogel@seitics.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=ipylypiv@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@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).