Searched full:interested (Results 1 – 25 of 479) sorted by relevance
12345678910>>...20
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
36 /* Not interested in SOL_IP:IP_TOS; in _getsockopt()45 /* Not interested in SOL_SOCKET:SO_SNDBUF; in _getsockopt()53 /* Not interested in SOL_TCP:TCP_CONGESTION; in _getsockopt()111 /* 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 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.
41 option if you are interested in debugging the driver.53 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.
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
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()
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
145 /* Are inode/sb/mount interested in parent and name info with this event? */167 * if parent is watching or if inode/sb/mount are interested in events with171 * inode/sb/mount are not interested in events with parent and name info.210 * groups require parent info or the parent is interested in this event. in __fsnotify_parent()
65 only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is66 interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
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.
39 It's safe to say n here if you're not interested in SIRF hardware
10 * Interested parties: libc, gdb...
25 framework, and interested clients reading the data from it::98 Subsystems interested in the energy model of a CPU can retrieve it using the
29 Let's also say you are only interested in when that function is
51 option if you are interested in debugging the driver.
18 r0 ... r7 if SR.RB is set to the bank we are interested in, otherwise ldc/stc
15 To receive events, the events the user is interested in first must be
10 A small tool which prints out cpufreq information helpful to developers and interested users.
27 * the child is interested and not the parent.59 /* sb/mount marks are not interested in name of directory */ in fsnotify_parent()