Home
last modified time | relevance | path

Searched full:int_max (Results 1 – 13 of 13) sorted by relevance

/Documentation/translations/zh_CN/core-api/
Didr.rst46 一些用户需要分配大于 ``INT_MAX`` 的ID。到目前为止,所有这些用户都满足 ``UINT_MAX``
/Documentation/ABI/obsolete/
Dsysfs-gpio14 the range 0..INT_MAX. See Documentation/admin-guide/gpio for more information.
/Documentation/dev-tools/kunit/
Dstart.rst232 KUNIT_EXPECT_EQ(test, INT_MAX, misc_example_add(0, INT_MAX));
233 KUNIT_EXPECT_EQ(test, -1, misc_example_add(INT_MAX, INT_MIN));
Dusage.rst84 KUNIT_EXPECT_EQ(test, INT_MAX, add(0, INT_MAX));
85 KUNIT_EXPECT_EQ(test, -1, add(INT_MAX, INT_MIN));
90 KUNIT_EXPECT_EQ(test, INT_MIN, add(INT_MAX, 1));
/Documentation/core-api/
Didr.rst40 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
/Documentation/devicetree/bindings/reserved-memory/
Dramoops.yaml82 This can be set to INT_MAX to store all kmsg dumps.
/Documentation/locking/
Dfutex-requeue-pi.rst131 nr_wake=1. nr_requeue should be INT_MAX for broadcast and 0 for
/Documentation/networking/
Dphonet.rst152 listen (lfd, INT_MAX);
Dip-sysctl.rst1094 Default: INT_MAX (unlimited)
1222 Possible Values: 1 - INT_MAX
2146 Default: INT_MAX (unlimited)
2152 Default: INT_MAX (unlimited)
/Documentation/scheduler/
Dsched-rt-group.rst102 * sched_rt_period_us takes values from 1 to INT_MAX.
/Documentation/dev-tools/
Dcheckpatch.rst415 &int_max -> SYSCTL_INT_MAX
/Documentation/admin-guide/sysctl/
Dkernel.rst648 Possible values to set are in range {0:``INT_MAX``}.
/Documentation/RCU/Design/Requirements/
DRequirements.rst1517 RCU limits nesting to ``INT_MAX``. This should suffice for almost all