[PATCH] Allow backends to specify which opcodes they support V2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tomo, List

Please find a second version of the patch to add support to have backends
reject opcodes they dont implement with INVALID_OP_CODE.
This patch adds this capability to RDWR and SHEEPDOG.

I changed the implamentation from the first patch based on comments from Dan Mick
and are now using a much more human friendly way to specify which opcodes are supproted.
This is now done by simply creating an array with all the defines for the opcode names. The ones that are listed in static char opcodes[] are the opcodes that the backend supports, the ones not listed will be returned as INVALID_OP_CODE


regards
ronnie sahlberg

--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SCSI]     [Linux RAID]     [Linux Clusters]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]

  Powered by Linux