Home
last modified time | relevance | path

Searched full:looked (Results 1 – 25 of 216) sorted by relevance

123456789

/linux/Documentation/driver-api/firmware/
H A Dlookup-order.rst6 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
H A Dbuilt-in-fw.rst7 the filesystem. Instead, firmware can be looked for inside the kernel
/linux/Documentation/filesystems/
H A Dfiles.rst81 5. Since both fdtable and file structures can be looked up
83 API. If they are looked up lock-free, rcu_dereference()
88 6. While updating, the fdtable pointer must be looked up while
/linux/tools/perf/util/
H A Dmetricgroup.h19 * generally exists in evlist. The evsel is looked up in the rblist
31 * will be looked up, matching either a value (from metric_events) or a
H A Dsharded_mutex.h12 * where the mutex is looked up from a hash value. This can lead to collisions
/linux/arch/arm/mach-omap2/
H A Domap2-restart.c46 * Some clocks need to be looked up in advance for the SoC restart
/linux/fs/ext4/
H A Dtruncate.h38 * which resulted in random data in an inode which looked enough in ext4_blocks_for_truncate()
/linux/tools/objtool/tests/generic/fixtures/
H A Dchecksum_skip.c14 * An entry per address is the invariant: .discard.sym_checksum is looked up by
H A Dabs_and_addressable.c14 * being looked at.
/linux/arch/openrisc/include/asm/
H A Dpgalloc.h57 * initialized. This needs to be looked into.
/linux/arch/arc/include/asm/
H A Dmach_desc.h21 * (XXX: although only 1st entry is looked at)
/linux/Documentation/devicetree/bindings/thermal/
H A Dgeneric-adc-thermal.yaml36 When ADC is read, the value is looked up on the table to get the
/linux/tools/objtool/tests/generic/
H A Dtest-abs-and-addressable.sh11 # at link time, but it is a relocation like any other and gets looked at.
H A Dtest-checksum-skip.sh6 # .discard.sym_checksum is an array of { address, checksum } looked up by the
/linux/tools/testing/selftests/filesystems/umount_propagation/
H A Dshrink_submounts_test.c6 * the propagated copy of the next one is looked up.
115 * the propagated copy of B is looked up next. R is busy, so B has to stay
/linux/drivers/hid/
H A Dhid-primax.c27 * Thus a report data set which looked like: in px_raw_event()
/linux/fs/ubifs/
H A DKconfig56 Originally UBIFS did not support atime, because it looked like a bad idea due
/linux/net/openvswitch/
H A Ddatapath.h39 * @n_mask_hit: Number of masks looked up for flow match.
40 * @n_mask_hit / (@n_hit + @n_missed) will be the average masks looked
/linux/Documentation/process/
H A D7.AdvancedTopics.rst189 even when a tag is provided, e.g. "I looked at aspects A, B and C of this
192 maintainers will not know that the reviewer has looked at the patch at all!
H A D2.Process.rst88 serious. For this reason, patches which cause regressions are looked upon
110 5.2 kernel's history looked like this (all dates in 2019):
474 increasingly, they are looked down upon. New developers wishing to
/linux/Documentation/devicetree/bindings/regulator/
H A Dpalmas-pmic.txt21 - interrupts : The interrupt number and the type which can be looked up here:
/linux/Documentation/fb/
H A Dinternals.rst79 are looked up in separate red, green, and blue lookup tables.
/linux/drivers/gpu/drm/tilcdc/
H A Dtilcdc_panel_legacy.c100 /* Looked only for these two parameter as all the other are always in tilcdc_panel_copy_props()
/linux/Documentation/bpf/
H A Dmap_cpumap.rst49 CPUMAP entries can only be updated/looked up/deleted from user space and not
/linux/drivers/s390/scsi/
H A Dzfcp_reqlist.h153 * while old requests are looked up starting at the beginning of the

123456789