Searched full:boundaries (Results 1 – 25 of 1066) sorted by relevance
12345678910>>...43
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | falloc.h | 21 * filesystem block size boundaries, but this boundary may be larger or
53 * boundaries, but this boundary may be larger or smaller depending on
70 * block size boundaries, but this boundary may be larger or smaller
|
| D | types.h | 42 * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
43 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | falloc.h | 21 * filesystem block size boundaries, but this boundary may be larger or
53 * boundaries, but this boundary may be larger or smaller depending on
70 * block size boundaries, but this boundary may be larger or smaller
|
| D | types.h | 49 * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
50 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | gsc-hwmon.rst | 44 PWM value will be scaled depending on 6 temperature boundaries.
45 The tempeature boundaries are read-write and in millidegree Celsius and the
|
| D | adt7475.rst | 132 speed when the temperature is between the two temperature boundaries.
133 Temperature boundaries are associated to temperature channels rather than
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | gsc-hwmon.rst | 44 PWM value will be scalled depending on 6 temperature boundaries.
45 The tempeature boundaries are read-write and in millidegree Celcius and the
|
| D | adt7475.rst | 132 speed when the temperature is between the two temperature boundaries.
133 Temperature boundaries are associated to temperature channels rather than
|
| /kernel/linux/linux-5.10/arch/mips/net/ |
| D | bpf_jit_asm.S | 63 /* Offset within header boundaries */
92 /* Offset within header boundaries */
113 /* Offset within header boundaries */
145 /* Quick check. Are we within reasonable boundaries? */ \
|
| /kernel/linux/linux-6.6/drivers/char/ipmi/ |
| D | ipmi_dmi.c | 182 case 0: /* Byte boundaries */ in dmi_decode_ipmi()
185 case 1: /* 32-bit boundaries */ in dmi_decode_ipmi()
188 case 2: /* 16-byte boundaries */ in dmi_decode_ipmi()
|
| /kernel/linux/linux-5.10/drivers/char/ipmi/ |
| D | ipmi_dmi.c | 182 case 0: /* Byte boundaries */ in dmi_decode_ipmi()
185 case 1: /* 32-bit boundaries */ in dmi_decode_ipmi()
188 case 2: /* 16-byte boundaries */ in dmi_decode_ipmi()
|
| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 135 At function call boundaries the stack and other unwind state is expected to be
150 boundaries. Note that it may be reliable to unwind across certain
155 have no such cases) should attempt to unwind across exception boundaries, as
307 the case must reject unwinding across exception boundaries unless they can
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/intel/i40e/ |
| D | i40e_lan_hmc.h | 17 * boundaries. If we do not have the width of the variable set to the correct
50 * boundaries. If we do not have the width of the variable set to the correct
|
| /kernel/linux/linux-6.6/drivers/thermal/ |
| D | thermal_acpi.c | 17 * the boundaries for the [trips] temperature returned by the
18 * firmware. Any values out of these boundaries may be considered
|
| D | thermal_trip.c | 40 * The function computes the next temperature boundaries by browsing
102 "new temperature boundaries: %d < x < %d\n", low, high); in __thermal_zone_set_trips()
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/i40e/ |
| D | i40e_lan_hmc.h | 15 * boundaries. If we do not have the width of the variable set to the correct
48 * boundaries. If we do not have the width of the variable set to the correct
|
| /kernel/linux/linux-6.6/drivers/misc/lkdtm/ |
| D | stackleak.c | 41 * within the expected task stack boundaries. These tests should never in check_stackleak_irqoff()
42 * fail unless the boundaries are incorrect or we're clobbering the in check_stackleak_irqoff()
|
| /kernel/linux/linux-6.6/arch/powerpc/xmon/ |
| D | xmon_bpts.S | 7 /* Prefixed instructions can not cross 64 byte boundaries */
|
| /kernel/linux/linux-5.10/arch/powerpc/xmon/ |
| D | xmon_bpts.S | 7 /* Prefixed instructions can not cross 64 byte boundaries */
|
| /kernel/linux/linux-5.10/include/uapi/linux/sched/ |
| D | types.h | 83 * the utilization boundaries within which it should schedule the task. These
84 * boundaries are valuable hints to support scheduler decisions on both task
|
| /kernel/linux/linux-6.6/include/uapi/linux/sched/ |
| D | types.h | 79 * the utilization boundaries within which it should schedule the task. These
80 * boundaries are valuable hints to support scheduler decisions on both task
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | romfs.rst | 51 byte boundaries for fast access. The minimum space a file will take
146 aligned to 16 byte boundaries, but most hardware devices and the block
181 boundaries, thus it would be possible to directly map a big portion of
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | romfs.rst | 51 byte boundaries for fast access. The minimum space a file will take
146 aligned to 16 byte boundaries, but most hardware devices and the block
181 boundaries, thus it would be possible to directly map a big portion of
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries.
99 must lie completely inside the crop boundaries and the driver may
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries.
99 must lie completely inside the crop boundaries and the driver may
|
12345678910>>...43