-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API cleanup: nvme_$NAME_get() vs nvme_get_$NAME() #206
Comments
The PR #660 is closed as correct implementation so seems the issue can be closed now. |
I've opened this issue for the various variants of our getters/setters for the non MI API. When we do the 2.0 we should go over the existing function names an make them consistent. |
Seems there is no other remaining function name to fix as below. tokunori@tokunori-desktop:~/nvme-cli/subprojects/libnvme$ git grep "_get("
examples/mi-conf.c: bus = dbus_bus_get(DBUS_BUS_SYSTEM, &berr);
examples/mi-mctp.c:int do_config_get(nvme_mi_ep_t ep, int argc, char **argv)
examples/mi-mctp.c: rc = do_config_get(ep, argc, argv);
libnvme/nvme.i: const char *nvme_host_dhchap_key_get(struct nvme_host *h) {
libnvme/nvme.i: const char *nvme_subsystem_name_get(struct nvme_subsystem *s) {
libnvme/nvme.i: struct nvme_host *nvme_subsystem_host_get(struct nvme_subsystem *s) {
libnvme/nvme.i: const char *nvme_ctrl_name_get(struct nvme_ctrl *c) {
libnvme/nvme.i: struct nvme_subsystem *nvme_ctrl_subsystem_get(struct nvme_ctrl *c) {
libnvme/nvme.i: const char *nvme_ctrl_state_get(struct nvme_ctrl *c) {
libnvme/nvme.i: const char *nvme_ctrl_dhchap_key_get(struct nvme_ctrl *c) {
libnvme/nvme.i: const char *nvme_ctrl_dhchap_host_key_get(struct nvme_ctrl *c) {
libnvme/nvme.i: const char *nvme_ns_name_get(struct nvme_ns *n) {
libnvme/nvme.i: PyObject *nbft_get(const char * filename)
libnvme/nvme.i:PyObject *nbft_get(const char * filename);
libnvme/tests/test-nbft.py: actual_nbft = nvme.nbft_get(args.filename)
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "transport");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "traddr");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "host_traddr");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "host_iface");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "trsvcid");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "dhchap_key");
src/nvme/json.c: attr_obj = json_object_object_get(port_obj, "dhchap_ctrl_key");
src/nvme/json.c: nqn_obj = json_object_object_get(subsys_obj, "nqn");
src/nvme/json.c: app_obj = json_object_object_get(subsys_obj, "application");
src/nvme/json.c: port_array = json_object_object_get(subsys_obj, "ports");
src/nvme/json.c: attr_obj = json_object_object_get(host_obj, "hostnqn");
src/nvme/json.c: attr_obj = json_object_object_get(host_obj, "hostid");
src/nvme/json.c: attr_obj = json_object_object_get(host_obj, "dhchap_key");
src/nvme/json.c: attr_obj = json_object_object_get(host_obj, "hostsymname");
src/nvme/json.c: attr_obj = json_object_object_get(host_obj, "persistent_discovery_ctrl");
src/nvme/json.c: subsys_array = json_object_object_get(host_obj, "subsystems");
src/nvme/mi-mctp.c: bus = dbus_bus_get(DBUS_BUS_SYSTEM, &berr);
src/nvme/mi.c:int nvme_mi_mi_config_get(nvme_mi_ep_t ep, __u32 dw0, __u32 dw1,
src/nvme/mi.h: * See &nvme_mi_mi_config_get() and &nvme_mi_config_set().
src/nvme/mi.h:int nvme_mi_mi_config_get(nvme_mi_ep_t ep, __u32 dw0, __u32 dw1,
src/nvme/mi.h: rc = nvme_mi_mi_config_get(ep, dw0, 0, &tmp);
src/nvme/mi.h: rc = nvme_mi_mi_config_get(ep, dw0, 0, &tmp); |
This is issue is about these function here:
vs
|
Thanks for your explanation. But seems both function lists follow the naming rules as below.
|
The current API isn't really consistent in the naming pattern. We should use one an stick to it.
The text was updated successfully, but these errors were encountered: