Searched refs:expecting (Results 1 – 24 of 24) sorted by relevance
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | dnotify.txt | 50 name "a/x" should be notified to a program expecting notifications on
51 directory "a", but will not be notified to one expecting notifications on
|
| /Linux-v5.4/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 | 1237 if (help->expecting[NF_CT_EXPECT_CLASS_DEFAULT] >= priv->size) { in nft_ct_expect_obj_eval()
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | vdso | 16 vDSO, specify the version you are expecting.
|
| /Linux-v5.4/include/net/netfilter/ |
| D | nf_conntrack_helper.h | 77 u8 expecting[NF_CT_MAX_EXPECT_CLASSES]; member
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | connector.rst | 82 are expecting, then it is a new message. If we receive a message and
83 its sequence number is the same as one we are expecting, but its
|
| /Linux-v5.4/Documentation/scsi/ |
| D | scsi-parameters.txt | 97 allowing boot to proceed. none ignores them, expecting
|
| D | ChangeLog.sym53c8xx_2 | 142 consistent with what archs are expecting.
|
| D | FlashPoint.txt | 80 caused grief for many people who inadvertently purchased a system expecting
|
| D | sym53c8xx_2.txt | 648 was not expecting this to happen. A device may behave so to
|
| D | ncr53c8xx.txt | 1322 was not expecting this to happen. A device may behave so to
|
| /Linux-v5.4/arch/arm/mach-omap1/ |
| D | ams-delta-fiq-handler.S | 145 cmp r10, #0 @ are we expecting start bit?
|
| /Linux-v5.4/Documentation/process/ |
| D | deprecated.rst | 37 smaller allocation being made than the caller was expecting. Using those
|
| D | howto.rst | 435 expecting?
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | rtc.rst | 113 than expecting a single battery-backed MC146818 clone on every system.
|
| /Linux-v5.4/Documentation/networking/ |
| D | sfp-phylink.rst | 38 and we are expecting to use and honor the in-band negotiation or
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/ |
| D | unaligned-memory-access.txt | 96 access. You'd be expecting field2 to be located at offset 2 bytes into the
|
| /Linux-v5.4/Documentation/target/ |
| D | tcmu-design.rst | 233 TCMU device as expecting to be backed by a certain handler, and <path>
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 227 reprogrammed in that case. Second, if the governor is expecting a non-timer
238 energy. Hence, if the governor is expecting a wakeup of any kind within the
243 In any case, the governor knows what it is expecting and the decision on whether
|
| /Linux-v5.4/Documentation/networking/dsa/ |
| D | dsa.rst | 273 the Ethernet switch on the other end, expecting a tag will typically drop this
|
| /Linux-v5.4/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 163 * We aren't expecting a bus free, so interrupt
|
| /Linux-v5.4/Documentation/virt/uml/ |
| D | UserModeLinux-HOWTO.txt | 1949 backing file and expecting that all of the COW files using it will see
|
