Searched full:interested (Results 1 – 25 of 525) sorted by relevance
12345678910>>...21
/linux-6.8/drivers/remoteproc/ |
D | Kconfig | 83 It's safe to say N here if you're not interested in multimedia 128 It's safe to say n here if you're not interested in multimedia 138 It's safe to say N here if you're not interested in the Keystone 162 not interested in the PRU or if you are unsure. 339 It's safe to say N here if you're not interested in utilizing 352 It's safe to say N here if you're not interested in utilizing 366 It's safe to say N if not interested in using RPU r5f cores.
|
/linux-6.8/tools/testing/selftests/bpf/progs/ |
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()
|
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-6.8/Documentation/ABI/testing/ |
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
|
D | dell-smbios-wmi | 30 call you're interested in. Typically SMBIOS buffers have 32 with the data you are interested in.
|
/linux-6.8/fs/notify/ |
D | fsnotify.c | 143 /* Are inode/sb/mount interested in parent and name info with this event? */ 172 * if parent is watching or if inode/sb/mount are interested in events with 176 * inode/sb/mount are not interested in events with parent and name info. 215 * groups require parent info or the parent is interested in this event. in __fsnotify_parent() 307 * interested) and once to child without name (if interested). in fsnotify_handle_event() 344 /* Are any of the group marks interested in this event? */ in send_to_group() 423 * is watching children and interested in this event, in fsnotify_iter_select_report_types()
|
/linux-6.8/Documentation/ABI/stable/ |
D | sysfs-bus-mhi | 10 Users: Any userspace application or clients interested in device info. 21 Users: Any userspace application or clients interested in device info.
|
/linux-6.8/drivers/net/wireless/ath/wil6210/ |
D | Kconfig | 42 option if you are interested in debugging the driver. 54 option if you are interested in debugging the driver.
|
/linux-6.8/Documentation/hid/ |
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-6.8/drivers/acpi/acpica/ |
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
|
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-6.8/arch/x86/kvm/mmu/ |
D | page_track.c | 204 * interested in by itself. 252 * @kvm: the guest instance we are interested in. 282 * @kvm: the guest instance we are interested in.
|
/linux-6.8/drivers/gpu/drm/i915/display/ |
D | intel_frontbuffer.c | 37 * and when the frontbuffer is exchanged with a flip. Subsystems interested in 40 * interested int. 43 * work like a special cache (FBC and PSR) and are interested when they should
|
/linux-6.8/Documentation/power/ |
D | energy-model.rst | 29 These subsystems are more interested in estimation of power used in the past, 40 framework, and interested clients reading the data from it:: 168 Subsystems interested in the energy model of a CPU can retrieve it using the
|
/linux-6.8/Documentation/pcmcia/ |
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-6.8/arch/sparc/include/asm/ |
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-6.8/drivers/net/wwan/iosm/ |
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-6.8/Documentation/admin-guide/media/ |
D | dvb_references.rst | 13 https://linuxtv.org/lists.php. If you're interested on that for historic
|
/linux-6.8/Documentation/rust/ |
D | index.rst | 18 maintainers interested in the Rust support, so that they can start working on
|
/linux-6.8/arch/hexagon/include/uapi/asm/ |
D | user.h | 10 * Interested parties: libc, gdb...
|
/linux-6.8/Documentation/process/ |
D | kernel-docs.rst | 11 get interested in the Kernel. But reading the sources is not always 179 it if you are interested in memory management development!
|
/linux-6.8/Documentation/arch/powerpc/ |
D | mpc52xx.rst | 37 is not supported, and I'm not sure anyone is interested in working on it
|
/linux-6.8/drivers/net/wireless/ath/ath5k/ |
D | Kconfig | 49 option if you are interested in debugging the driver.
|
/linux-6.8/Documentation/trace/ |
D | events-nmi.rst | 29 Let's also say you are only interested in when that function is
|
/linux-6.8/Documentation/gpu/ |
D | automated_testing.rst | 12 be tested. Moreover, it isn't practical for each person interested in this 22 people interested in testing it can use this shared infrastructure to save
|
12345678910>>...21