/linux/tools/testing/selftests/bpf/progs/ |
H A D | sockopt_sk.c | 51 /* Not interested in SOL_IP:IP_TOS; in _getsockopt() 59 /* Not interested in SOL_SOCKET:SO_SNDBUF; in _getsockopt() 67 /* Not interested in SOL_TCP:TCP_CONGESTION; in _getsockopt() 161 /* Not interested in SOL_IP:IP_TOS; in _setsockopt()
|
H A D | sockopt_inherit.c | 60 goto out; /* only interested in SOL_CUSTOM */ in _getsockopt() 91 goto out; /* only interested in SOL_CUSTOM */ in _setsockopt()
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-vfio-mdev | 51 Userspace applications interested in creating mediated 72 Userspace applications interested in knowing the name of 85 Userspace applications interested in knowing the details of
|
H A D | dell-smbios-wmi | 30 call you're interested in. Typically SMBIOS buffers have 32 with the data you are interested in.
|
/linux/drivers/net/wireless/ath/wil6210/ |
H A D | Kconfig | 42 option if you are interested in debugging the driver. 54 option if you are interested in debugging the driver.
|
/linux/fs/notify/ |
H A D | fsnotify.c | 173 /* Are inode/sb/mount interested in parent and name info with this event? */ 231 * if parent is watching or if inode/sb/mount are interested in events with 235 * inode/sb/mount are not interested in events with parent and name info. 272 * groups require parent info or the parent is interested in this event. in __fsnotify_parent() 362 * event once to parent dir with name (if interested) and once to child in fsnotify_handle_event() 363 * without name (if interested). in fsnotify_handle_event() 404 /* Are any of the group marks interested in this event? */ in send_to_group() 483 * is watching children and interested in this event, in fsnotify_iter_select_report_types()
|
/linux/Documentation/hid/ |
H A D | hid-transport.rst | 63 aware of which transport drivers are available and is not interested in it. It 64 is only interested in devices. 259 Called from HID device drivers once they are interested in data reports. 261 not interested in device data and transport drivers can put devices asleep. 270 longer interested in device reports. (Usually if user-space closed any input 275 be called again if the device driver is interested in input reports again.
|
/linux/drivers/acpi/acpica/ |
H A D | evrgnini.c | 23 * PARAMETERS: handle - Region we are interested in 86 * PARAMETERS: handle - Region we are interested in 117 * PARAMETERS: handle - Region we are interested in 359 * PARAMETERS: handle - Region we are interested in 386 * PARAMETERS: handle - Region we are interested in 413 * PARAMETERS: handle - Region we are interested in 465 * PARAMETERS: handle - Region we are interested in
|
H A D | dsinit.c | 59 * We are only interested in NS nodes owned by the table that in acpi_ds_init_one_object() 68 /* And even then, we are only interested in a few object types */ in acpi_ds_init_one_object()
|
/linux/arch/x86/kvm/mmu/ |
H A D | page_track.c | 271 * interested in by itself. 319 * @kvm: the guest instance we are interested in. 349 * @kvm: the guest instance we are interested in.
|
/linux/arch/sparc/include/asm/ |
H A D | cmpxchg_64.h | 66 * here is to get the bit shift of the byte we are interested in. 127 * here is to get the bit shift of the byte we are interested in.
|
/linux/Documentation/pcmcia/ |
H A D | driver-changes.rst | 65 only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is 66 interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
|
/linux/drivers/net/wwan/iosm/ |
H A D | iosm_ipc_protocol.c | 44 * out and is no longer interested in the response. 98 * object as we are no longer interested in the response. in ipc_protocol_msg_send()
|
/linux/drivers/gpu/drm/ttm/tests/ |
H A D | TODO | 19 1) We are interested in hardware-independent testing
|
/linux/Documentation/admin-guide/media/ |
H A D | dvb_references.rst | 13 https://linuxtv.org/lists.php. If you're interested on that for historic
|
/linux/arch/hexagon/include/uapi/asm/ |
H A D | user.h | 10 * Interested parties: libc, gdb...
|
/linux/Documentation/arch/powerpc/ |
H A D | mpc52xx.rst | 37 is not supported, and I'm not sure anyone is interested in working on it
|
/linux/drivers/net/wireless/ath/ath5k/ |
H A D | Kconfig | 49 option if you are interested in debugging the driver.
|
/linux/Documentation/trace/ |
H A D | events-nmi.rst | 29 Let's also say you are only interested in when that function is
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | dev-event.rst | 15 To receive events, the events the user is interested in first must be
|
/linux/Documentation/arch/sh/ |
H A D | register-banks.rst | 18 r0 ... r7 if SR.RB is set to the bank we are interested in, otherwise ldc/stc
|
/linux/Documentation/rust/ |
H A D | index.rst | 18 maintainers interested in the Rust support, so that they can start working on
|
/linux/arch/powerpc/kernel/ |
H A D | eeh_cache.c | 187 /* We are interested only bus addresses, not dma or other stuff */ in __eeh_addr_cache_insert_dev() 198 * @dev: PCI device whose I/O addresses we are interested in.
|
/linux/Documentation/driver-api/surface_aggregator/clients/ |
H A D | san.rst | 18 relays the dGPU events to any other driver interested via its public API and
|
/linux/tools/power/cpupower/man/ |
H A D | cpupower-frequency-info.1 | 10 A small tool which prints out cpufreq information helpful to developers and interested users.
|