Searched full:interested (Results 1 – 25 of 1009) sorted by relevance
12345678910>>...41
83 It's safe to say N here if you're not interested in multimedia128 It's safe to say n here if you're not interested in multimedia138 It's safe to say N here if you're not interested in the Keystone162 not interested in the PRU or if you are unsure.339 It's safe to say N here if you're not interested in utilizing352 It's safe to say N here if you're not interested in utilizing366 It's safe to say N if not interested in using RPU r5f cores.
70 It's safe to say N here if you're not interested in multimedia115 It's safe to say n here if you're not interested in multimedia125 It's safe to say N here if you're not interested in the Keystone275 It's safe to say N here if you're not interested in utilizing288 It's safe to say N here if you're not interested in utilizing
40 /* Not interested in SOL_IP:IP_TOS; in _getsockopt()49 /* Not interested in SOL_SOCKET:SO_SNDBUF; in _getsockopt()57 /* Not interested in SOL_TCP:TCP_CONGESTION; in _getsockopt()130 /* Not interested in SOL_IP:IP_TOS; in _setsockopt()
59 return 1; /* only interested in SOL_CUSTOM */ in _getsockopt()84 return 1; /* only interested in SOL_CUSTOM */ in _setsockopt()
10 Users: Any userspace application or clients interested in device info.21 Users: Any userspace application or clients interested in device info.
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()
60 goto out; /* only interested in SOL_CUSTOM */ in _getsockopt()91 goto out; /* only interested in SOL_CUSTOM */ in _setsockopt()
156 /* Are inode/sb/mount interested in parent and name info with this event? */185 * if parent is watching or if inode/sb/mount are interested in events with189 * inode/sb/mount are not interested in events with parent and name info.228 * groups require parent info or the parent is interested in this event. in __fsnotify_parent()293 * children and interested in this event, which is an event in fsnotify_handle_event()295 * interested in this event? in fsnotify_handle_event()312 * interested) and once to child without name (if interested). in fsnotify_handle_event()
51 Userspace applications interested in creating mediated72 Userspace applications interested in knowing the name of85 Userspace applications interested in knowing the details of
30 call you're interested in. Typically SMBIOS buffers have32 with the data you are interested in.
154 /* Are inode/sb/mount interested in parent and name info with this event? */183 * if parent is watching or if inode/sb/mount are interested in events with187 * inode/sb/mount are not interested in events with parent and name info.226 * groups require parent info or the parent is interested in this event. in __fsnotify_parent()316 * event once to parent dir with name (if interested) and once to child in fsnotify_handle_event()317 * without name (if interested). in fsnotify_handle_event()358 /* Are any of the group marks interested in this event? */ in send_to_group()437 * is watching children and interested in this event, in fsnotify_iter_select_report_types()
42 option if you are interested in debugging the driver.54 option if you are interested in debugging the driver.
63 aware of which transport drivers are available and is not interested in it. It64 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 input275 be called again if the device driver is interested in input reports again.
23 * PARAMETERS: handle - Region we are interested in86 * PARAMETERS: handle - Region we are interested in117 * PARAMETERS: handle - Region we are interested in359 * PARAMETERS: handle - Region we are interested in386 * PARAMETERS: handle - Region we are interested in413 * PARAMETERS: handle - Region we are interested in465 * PARAMETERS: handle - Region we are interested in
81 * @kvm: the guest instance we are interested in.116 * @kvm: the guest instance we are interested in.217 * interested in by itself.
23 * PARAMETERS: handle - Region we are interested in86 * PARAMETERS: handle - Region we are interested in117 * PARAMETERS: handle - Region we are interested in359 * PARAMETERS: handle - Region we are interested in386 * PARAMETERS: handle - Region we are interested in413 * PARAMETERS: handle - Region we are interested in
204 * interested in by itself.252 * @kvm: the guest instance we are interested in.282 * @kvm: the guest instance we are interested in.
37 * and when the frontbuffer is exchanged with a flip. Subsystems interested in40 * interested int.43 * work like a special cache (FBC and PSR) and are interested when they should
15 number of interested parties (userspace driver developers) can