IDR_REPLACE(9) Basic Kernel Library Functions IDR_REPLACE(9)NAME
idr_replace - replace pointer for given id
void * idr_replace(struct idr * idp, void * ptr, int id);
pointer you want associated with the id
Replace the pointer registered with an id and return the old value. A -ENOENT return indicates that id was not found. A -EINVAL return
indicates that id was not within valid constraints.
The caller must serialize with writers.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 IDR_REPLACE(9)
Check Out this Related Man Page
DEBUGFS_CREATE_FILE(9) The debugfs filesystem DEBUGFS_CREATE_FILE(9)NAME
debugfs_create_file - create a file in the debugfs filesystem
struct dentry * debugfs_create_file(const char * name, umode_t mode, struct dentry * parent, void * data,
const struct file_operations * fops);
a pointer to a string containing the name of the file to create.
the permission that the file should have.
a pointer to the parent dentry for this file. This should be a directory dentry if set. If this paramater is NULL, then the file will
be created in the root of the debugfs filesystem.
a pointer to something that the caller will want to get to later on. The inode.i_private pointer will point to this value on the open
a pointer to a struct file_operations that should be used for this file.
This is the basic "create a file" function for debugfs. It allows for a wide range of flexibility in creating a file, or a directory (if
you want to create a directory, the debugfs_create_dir function is recommended to be used instead.)
This function will return a pointer to a dentry if it succeeds. This pointer must be passed to the debugfs_remove function when the file is
to be removed (no automatic cleanup happens if your module is unloaded, you are responsible here.) If an error occurs, NULL will be
If debugfs is not enabled in the kernel, the value -ENODEV will be returned.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 DEBUGFS_CREATE_FILE(9)