| /linux/Documentation/driver-api/ |
| H A D | io_ordering.rst | 15 A more concrete example from a hypothetical device driver::
|
| H A D | clk.rst | 35 hardware-specific bits for the hypothetical "foo" hardware.
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | nvidia,tegra186-bpmp.yaml | 55 provide (e.g. a future hypothetical SPI bus service). As such, child
|
| /linux/Documentation/arch/arm/ |
| H A D | vlocks.rst | 97 if necessary, as in the following hypothetical example for 4096 CPUs::
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | ibm,powerpc-cpu-features.txt | 231 vsx2 (hypothetical) {
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 28 driver. This declaration is hypothetical only; it relies on the driver
|
| /linux/Documentation/ |
| H A D | atomic_t.txt | 258 This should not happen; but a hypothetical atomic_inc_acquire() --
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | mpo-overview.rst | 59 hypothetical hardware that we are using as an example, we have an absolute
|
| /linux/LICENSES/deprecated/ |
| H A D | GPL-1.0 | 243 The hypothetical commands `show w' and `show c' should show the
|
| /linux/tools/usb/usbip/ |
| H A D | COPYING | 321 The hypothetical commands `show w' and `show c' should show the appropriate
|
| /linux/LICENSES/preferred/ |
| H A D | GPL-2.0 | 338 The hypothetical commands `show w' and `show c' should show the appropriate
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 59 Consider an hypothetical dual-core asymmetric CPU capacity system where
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 156 what is being written. In a hypothetical binary policy design, a serializer
|
| /linux/tools/lib/bpf/ |
| H A D | bpf_helpers.h | 356 * that can be used pretty naturally. E.g., for some hypothetical cgroup
|
| /linux/include/uapi/linux/ |
| H A D | rtnetlink.h | 293 It will be used by hypothetical multiple routing daemons.
|
| /linux/tools/include/uapi/linux/ |
| H A D | rtnetlink.h | 293 It will be used by hypothetical multiple routing daemons.
|
| /linux/Documentation/i2c/ |
| H A D | i2c-topology.rst | 107 intent with such a topology would in this hypothetical example
|
| /linux/fs/xfs/scrub/ |
| H A D | ialloc.c | 354 * Check that the holemask and freemask of a hypothetical inode cluster match
|
| /linux/arch/x86/mm/ |
| H A D | tlb.c | 684 * opens a hypothetical hole vs. mm_struct reuse, which is more or in cond_mitigation()
801 * hypothetical buggy code that directly switches to swapper_pg_dir in switch_mm_irqs_off()
|
| /linux/fs/btrfs/tests/ |
| H A D | extent-io-tests.c | 478 * something repetitive that could miss some hypothetical off-by-n bug. in __test_eb_bitmaps()
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | 4965-calib.c | 111 * hypothetical listening period of 200 time units (TU), 204.8 msec: in il4965_sens_energy_cck()
|
| /linux/drivers/net/wireless/intel/iwlwifi/dvm/ |
| H A D | calib.c | 127 * hypothetical listening period of 200 time units (TU), 204.8 msec: in iwl_sens_energy_cck()
|
| /linux/kernel/kcsan/ |
| H A D | core.c | 1300 * couldn't optimize much anyway. The result of a hypothetical architecture
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-codec.rst | 1333 decoded. The standard describes it as "Part of a hypothetical
|
| /linux/Documentation/arch/x86/ |
| H A D | boot.rst | 369 e.g. 0x0204 for version 2.04, and 0x0a11 for a hypothetical version
|