Searched refs:expecting (Results 1 – 25 of 29) sorted by relevance
12
/kernel/linux/linux-5.10/Documentation/x86/ |
D | usb-legacy-support.rst | 24 system crashes, because the SMM BIOS is not expecting to be in PAE mode. 28 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
|
/kernel/linux/linux-5.10/Documentation/filesystems/ |
D | dnotify.rst | 55 name "a/x" should be notified to a program expecting notifications on 56 directory "a", but will not be notified to one expecting notifications on
|
/kernel/linux/linux-5.10/net/netfilter/ |
D | nf_conntrack_expect.c | 60 master_help->expecting[exp->class]--; in nf_ct_unlink_expect_report() 389 master_help->expecting[exp->class]++; in nf_ct_expect_insert() 451 master_help->expecting[expect->class] >= p->max_expected) { in __nf_ct_expect_check() 453 if (master_help->expecting[expect->class] in __nf_ct_expect_check()
|
D | nft_ct.c | 1241 if (help->expecting[NF_CT_EXPECT_CLASS_DEFAULT] >= priv->size) { in nft_ct_expect_obj_eval()
|
/kernel/linux/linux-5.10/Documentation/ABI/stable/ |
D | vdso | 22 vDSO, specify the version you are expecting.
|
/kernel/linux/linux-5.10/include/net/netfilter/ |
D | nf_conntrack_helper.h | 77 u8 expecting[NF_CT_MAX_EXPECT_CLASSES]; member
|
/kernel/linux/linux-5.10/Documentation/driver-api/ |
D | connector.rst | 83 are expecting, then it is a new message. If we receive a message and 84 its sequence number is the same as one we are expecting, but its
|
/kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/ |
D | README | 48 expecting), using the same logic/perspective as in the arm64 Kernel signals
|
/kernel/linux/linux-5.10/Documentation/scsi/ |
D | scsi-parameters.rst | 101 allowing boot to proceed. none ignores them, expecting
|
D | ChangeLog.sym53c8xx_2 | 142 consistent with what archs are expecting.
|
D | FlashPoint.rst | 93 caused grief for many people who inadvertently purchased a system expecting
|
/kernel/linux/linux-5.10/arch/arm/mach-omap1/ |
D | ams-delta-fiq-handler.S | 146 cmp r10, #0 @ are we expecting start bit?
|
/kernel/linux/linux-5.10/arch/mips/boot/dts/ingenic/ |
D | ci20.dts | 237 * for REG9 and the driver expecting that,
|
/kernel/linux/linux-5.10/Documentation/admin-guide/ |
D | rtc.rst | 113 than expecting a single battery-backed MC146818 clone on every system.
|
/kernel/linux/linux-5.10/Documentation/cdrom/ |
D | ide-cd.rst | 227 it was expecting one (on any feasible IRQ). If <n> is negative, 229 it was expecting to receive just one from the CDROM drive.
|
/kernel/linux/linux-5.10/Documentation/networking/ |
D | sfp-phylink.rst | 38 and we are expecting to use and honor the in-band negotiation or
|
D | ppp_generic.rst | 392 expecting times as either 32-bit or 64-bit time_t seconds.
|
/kernel/linux/linux-5.10/Documentation/core-api/ |
D | unaligned-memory-access.rst | 96 access. You'd be expecting field2 to be located at offset 2 bytes into the
|
/kernel/linux/linux-5.10/Documentation/doc-guide/ |
D | contributing.rst | 137 from the documentation build, then we can start expecting developers to
|
/kernel/linux/linux-5.10/Documentation/target/ |
D | tcmu-design.rst | 233 TCMU device as expecting to be backed by a certain handler, and <path>
|
/kernel/linux/linux-5.10/Documentation/process/ |
D | deprecated.rst | 59 smaller allocation being made than the caller was expecting. Using those
|
D | howto.rst | 436 expecting?
|
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
D | cpuidle.rst | 225 reprogrammed in that case. Second, if the governor is expecting a non-timer 236 energy. Hence, if the governor is expecting a wakeup of any kind within the 241 In any case, the governor knows what it is expecting and the decision on whether
|
/kernel/linux/linux-5.10/Documentation/gpu/ |
D | drm-uapi.rst | 220 is expecting. This applies also to ioctls that faked success.
|
/kernel/linux/linux-5.10/Documentation/networking/dsa/ |
D | dsa.rst | 273 the Ethernet switch on the other end, expecting a tag will typically drop this
|
12