| /linux/Documentation/core-api/ |
| H A D | symbol-namespaces.rst | 6 export surface of in-kernel symbols exported through the family of 14 their exported symbols into separate namespaces. That is useful for 17 kernel. As of today, modules that make use of symbols exported into namespaces, 27 Symbols can be exported into namespace using different methods. All of them are 45 ``namespace`` set accordingly. A symbol that is exported without a namespace will 67 symbol exported with EXPORT_SYMBOL_NS() while this definition is present, will 68 still be exported into the namespace that is passed as the namespace argument 82 Symbols exported using this macro are put into a module namespace. This 96 How to use Symbols exported in Namespaces 99 In order to use symbols that are exported into namespaces, kernel modules need [all …]
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | pnfs-scsi-server.rst | 12 To use pNFS SCSI layouts with the Linux NFS server, the exported file 16 exported LUN, striping or concatenation of LUNs on the MDS and clients 20 automatically enabled if the file system is exported using the "pnfs"
|
| H A D | pnfs-block-server.rst | 11 To use pNFS block layouts with the Linux NFS server the exported file 15 sit directly on the exported volume, striping or concatenation of
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-wacom | 27 <obsoleted by the LED class API now exported by the driver> 37 <obsoleted by the LED class API now exported by the driver> 46 <obsoleted by the LED class API now exported by the driver> 56 <obsoleted by the LED class API now exported by the driver> 100 <obsoleted by the LED class API now exported by the driver>
|
| H A D | sysfs-fs-xfs | 7 log. The LSN is exported in "cycle:basic block" format. 16 log. The LSN is exported in "cycle:basic block" format.
|
| H A D | sysfs-firmware-dmi-entries | 12 cannot ensure that the data as exported to userland is 46 guarantees that handles as exported are unique, and 51 exported as attributes: 91 is exported in the directory::
|
| H A D | sysfs-platform-usbip-vudc | 21 1 Device is available and can be exported 22 2 Device is currently exported
|
| H A D | sysfs-class-pwm | 47 each exported PWM channel where X is the exported PWM
|
| H A D | sysfs-class-rnbd-server | 18 Description: Is a symlink to the sysfs entry of the exported device. 27 Description: For each client a particular device is exported to, following directory will be
|
| /linux/kernel/ |
| H A D | kallsyms.c | 604 int exported; member 613 &iter->exported); in get_ksymbol_mod() 632 &iter->exported); in get_ksymbol_ftrace_mod() 646 iter->exported = 0; in get_ksymbol_bpf() 666 iter->exported = 0; in get_ksymbol_kprobe() 778 type = iter->exported ? toupper(iter->type) : in s_show()
|
| /linux/Documentation/virt/kvm/s390/ |
| H A D | s390-pv-dump.rst | 51 encrypted memory can simply be read once it has been exported. The 53 needed. Memory that has been swapped out and hence was exported can be 57 The tweaks / status flags for the exported pages need to be requested
|
| /linux/kernel/module/ |
| H A D | Kconfig | 212 This enables module versioning for exported symbols also from 409 Symbols exported with EXPORT_SYMBOL_NS*() are considered exported in 410 a namespace. A module that makes use of a symbol exported with such a 432 bool "Trim unused exported kernel symbols" 437 many of those exported symbols might never be used. 439 This option allows for unused exported symbols to be dropped from 450 By default, all unused exported symbols will be un-exported from the 454 exported at all times, even in absence of in-tree users. The value to
|
| /linux/tools/perf/Documentation/ |
| H A D | db-export.txt | 29 3. Scripts that use a database (e.g. exported-sql-viewer.py) can maintain 31 before using them. e.g. function IsSelectable() in exported-sql-viewer.py
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-gpio | 10 kernel code, it may be exported by userspace (and unexported later). 21 /gpioN ... for each exported GPIO #N OR
|
| /linux/drivers/nvme/host/ |
| H A D | Kconfig | 60 to use remote block devices exported using the NVMe protocol set. 76 exported using the NVMe protocol set. 93 exported using the NVMe protocol set.
|
| /linux/Documentation/kbuild/ |
| H A D | headers_install.rst | 8 The linux kernel's exported header files describe the API for user space 31 current architecture. The linux/asm directory of the exported kernel headers
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-expbuf.rst | 49 the index of the plane to be exported. Valid planes range from zero to 55 case of multi-planar API, every plane is exported separately using 137 - Index of the plane to be exported when using the multi-planar API.
|
| H A D | vidioc-reqbufs.rst | 62 buffers. Note that if any buffers are still mapped or exported via DMABUF, 67 orphaned and will be freed when they are unmapped or when the exported DMABUF 148 mapped or exported via DMABUF. These orphaned buffers will be freed 149 when they are unmapped or when the exported DMABUF fds are closed.
|
| /linux/fs/netfs/ |
| H A D | Kconfig | 15 caching and exported through file: 50 caching and exported through file:
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | sysfs.rst | 70 node exported using the "export" file. 86 it was exported by kernel code that didn't explicitly 155 /* create a sysfs link to an exported GPIO node */ 168 After the GPIO has been exported, gpiod_export_link() allows creating
|
| /linux/drivers/firmware/google/ |
| H A D | Kconfig | 57 the EBDA on Google servers. If found, this log is exported to 74 the coreboot table. If found, this log is exported to userland
|
| /linux/fs/vboxsf/ |
| H A D | Kconfig | 7 implements the Linux-guest side of this allowing folders exported
|
| /linux/Documentation/filesystems/ |
| H A D | splice.rst | 17 exported for use by modules.
|
| H A D | virtiofs.rst | 15 guest to mount a directory that has been exported on the host. 53 underlying filesystem of the directory that has been exported
|
| /linux/Documentation/admin-guide/ |
| H A D | cputopology.rst | 2 How CPU topology info is exported via sysfs 5 CPU topology info is exported via sysfs. Items (attributes) are similar
|