From: Tejun Heo <tj@kernel.org>
To: Marc C <marc.ceeeee@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Add additional queued command opcodes from SATA spec
Date: Mon, 22 Jul 2013 16:45:10 -0400 [thread overview]
Message-ID: <20130722204510.GC13040@mtj.dyndns.org> (raw)
In-Reply-To: <7D07DE2D-D421-4E79-AB4B-27566DCB3655@gmail.com>
Hello,
On Mon, Jul 22, 2013 at 01:42:42PM -0700, Marc C wrote:
> I have some out-of-tree user apps that exploit those opcodes
> (via uapi). I eventually will have additional patches, but cannot
Hmmm? I don't think ata.h is visible to userland, is it?
> submit the pull request for them until the SATA 3.2 spec is public.
Let's add the opcodes when it becomes actually used in the kernel then
unless it's gonna be a PITA on your end.
Thanks!
--
tejun
next prev parent reply other threads:[~2013-07-22 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 1:17 [PATCH] libata: Add additional queued command opcodes from SATA spec Marc C
2013-07-22 20:00 ` Tejun Heo
2013-07-22 20:42 ` Marc C
2013-07-22 20:45 ` Tejun Heo [this message]
2013-07-22 20:48 ` Marc C
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=20130722204510.GC13040@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=marc.ceeeee@gmail.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