| 1 |
.TH "nvme_set_root" 9 "nvme_set_root" "November 2025" "libnvme API manual" LINUX |
| 2 |
.SH NAME |
| 3 |
nvme_set_root \- Set nvme_root_t context |
| 4 |
.SH SYNOPSIS |
| 5 |
.B "void" nvme_set_root |
| 6 |
.BI "(nvme_root_t r " ");" |
| 7 |
.SH ARGUMENTS |
| 8 |
.IP "r" 12 |
| 9 |
nvme_root_t context |
| 10 |
.SH "DESCRIPTION" |
| 11 |
In order to be able to log from code paths where no root object is passed in |
| 12 |
via the arguments use the the default one which can be set via this call. |
| 13 |
When creating a new root object with \fInvme_create_root\fP the global root object |
| 14 |
will be set as well. This means the global root object is always pointing to |
| 15 |
the latest created root object. Note the first \fInvme_free_tree\fP call will reset |
| 16 |
the global root object. |
| 17 |
|
| 18 |
This function is deprecated. Use nvme_init_default_logging or/and |
| 19 |
nvme_init_logging instead. |