Hi Tejun, > Hmmm? I don't think ata.h is visible to userland, is it? I had done so locally so I wouldn't have to re-define all of the opcodes. > Let's add the opcodes when it becomes actually used in the kernel then > unless it's gonna be a PITA on your end. Sounds good! Thanks, Marc On Jul 22, 2013, at 1:45 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
