Searched full:looked (Results 1 – 25 of 269) sorted by relevance
1234567891011
| /Linux-v6.6/lib/ |
| D | linear_ranges.c | 66 * @r: pointer to linear range where value is looked from
78 * @r: pointer to linear range where value is looked from
101 * @r: pointer to array of linear ranges where value is looked from
126 * @r: pointer to linear range where selector is looked from
165 * @r: pointer to array of linear ranges where selector is looked from
207 * @r: pointer to linear range where selector is looked from
246 * @r: pointer to linear range where selector is looked from
|
| /Linux-v6.6/Documentation/driver-api/firmware/ |
| D | lookup-order.rst | 6 Below is chronological order of how firmware will be looked for once
11 * The ''Firmware cache'' is looked at next. If the firmware is found we
|
| D | built-in-fw.rst | 7 the filesystem. Instead, firmware can be looked for inside the kernel
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | files.rst | 103 6. Since both fdtable and file structures can be looked up
105 API. If they are looked up lock-free, rcu_dereference()
109 7. While updating, the fdtable pointer must be looked up while
|
| /Linux-v6.6/tools/perf/util/ |
| D | metricgroup.h | 19 * generally exists in perf_stat_config. The evsel is looked up in the rblist
31 * will be looked up, matching either a value (from metric_events) or a
|
| D | sharded_mutex.h | 12 * where the mutex is looked up from a hash value. This can lead to collisions
|
| /Linux-v6.6/drivers/net/mdio/ |
| D | fwnode_mdio.c | 91 * can be looked up later in fwnode_mdiobus_phy_device_register()
146 * can be looked up later. in fwnode_mdiobus_register_phy()
|
| /Linux-v6.6/Documentation/networking/ |
| D | dns_resolver.rst | 86 looked up. The default query type is a straight hostname to IP address
106 The kernel maintains an internal keyring in which it caches looked up keys.
|
| /Linux-v6.6/fs/squashfs/ |
| D | namei.c | 34 * alphabetically larger than the filename being looked up. At this point the
117 * Return index (f_pos) of the looked up metadata block. Translate in get_dir_index_using_name()
|
| /Linux-v6.6/arch/arm/mach-omap2/ |
| D | omap2-restart.c | 46 * Some clocks need to be looked up in advance for the SoC restart
|
| /Linux-v6.6/fs/ext4/ |
| D | truncate.h | 38 * which resulted in random data in an inode which looked enough in ext4_blocks_for_truncate()
|
| /Linux-v6.6/net/openvswitch/ |
| D | datapath.h | 38 * @n_mask_hit: Number of masks looked up for flow match.
39 * @n_mask_hit / (@n_hit + @n_missed) will be the average masks looked
|
| /Linux-v6.6/arch/openrisc/include/asm/ |
| D | pgalloc.h | 59 * initialized. This needs to be looked into.
|
| /Linux-v6.6/Documentation/devicetree/bindings/thermal/ |
| D | generic-adc-thermal.yaml | 34 When ADC is read, the value is looked up on the table to get the
|
| /Linux-v6.6/arch/arc/include/asm/ |
| D | mach_desc.h | 21 * (XXX: although only 1st entry is looked at)
|
| /Linux-v6.6/drivers/hid/ |
| D | hid-primax.c | 27 * Thus a report data set which looked like: in px_raw_event()
|
| /Linux-v6.6/Documentation/staging/ |
| D | crc32.rst | 146 lookup in a 65536-entry table, the two high bytes are looked up in
158 broken into bytes and looked up in the tables. Because the 32-bit shift
|
| /Linux-v6.6/fs/ubifs/ |
| D | Kconfig | 56 Originally UBIFS did not support atime, because it looked like a bad idea due
|
| /Linux-v6.6/Documentation/devicetree/bindings/regulator/ |
| D | palmas-pmic.txt | 21 - interrupts : The interrupt number and the type which can be looked up here:
|
| /Linux-v6.6/include/linux/ |
| D | kref.h | 100 * objects that can be looked up from a lookup structure, and which are
|
| D | bpf_local_storage.h | 39 * When a bpf local storage is being looked up for a
|
| /Linux-v6.6/Documentation/fb/ |
| D | internals.rst | 79 are looked up in separate red, green, and blue lookup tables.
|
| /Linux-v6.6/drivers/interconnect/ |
| D | debugfs-client.c | 64 * If we've already looked up a path, then use the existing one instead in icc_get_set()
|
| /Linux-v6.6/Documentation/process/ |
| D | 2.Process.rst | 93 serious. For this reason, patches which cause regressions are looked upon
113 5.2 kernel's history looked like this (all dates in 2019):
477 increasingly, they are looked down upon. New developers wishing to
|
| /Linux-v6.6/include/drm/ |
| D | drm_mode_object.h | 42 * looked up using drm_mode_object_find(). Besides basic uapi interface
|
1234567891011
