Home
last modified time | relevance | path

Searched refs:expecting (Results 1 – 24 of 24) sorted by relevance

/linux-4.1.27/Documentation/x86/
Dusb-legacy-support.txt20 system crashes, because the SMM BIOS is not expecting to be in PAE mode.
24 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
/linux-4.1.27/net/netfilter/
Dnf_conntrack_expect.c56 master_help->expecting[exp->class]--; in nf_ct_unlink_expect_report()
348 master_help->expecting[exp->class]++; in nf_ct_expect_insert()
420 master_help->expecting[expect->class] >= p->max_expected) { in __nf_ct_expect_check()
422 if (master_help->expecting[expect->class] in __nf_ct_expect_check()
/linux-4.1.27/Documentation/filesystems/
Ddnotify.txt50 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-4.1.27/Documentation/ABI/stable/
Dvdso16 vDSO, specify the version you are expecting.
/linux-4.1.27/include/net/netfilter/
Dnf_conntrack.h65 u8 expecting[NF_CT_MAX_EXPECT_CLASSES]; member
/linux-4.1.27/Documentation/connector/
Dconnector.txt119 are expecting, then it is a new message. If we receive a message and
120 its sequence number is the same as one we are expecting, but its
/linux-4.1.27/Documentation/scsi/
Dscsi-parameters.txt107 allowing boot to proceed. none ignores them, expecting
DChangeLog.sym53c8xx_2142 consistent with what archs are expecting.
DFlashPoint.txt80 caused grief for many people who inadvertently purchased a system expecting
Dsym53c8xx_2.txt648 was not expecting this to happen. A device may behave so to
Dncr53c8xx.txt1322 was not expecting this to happen. A device may behave so to
/linux-4.1.27/arch/arm/mach-omap1/
Dams-delta-fiq-handler.S153 cmp r10, #0 @ are we expecting start bit?
/linux-4.1.27/scripts/genksyms/
Dparse.tab.c_shipped1339 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s"));
1340 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s"));
1341 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s"));
1342 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s"));
/linux-4.1.27/scripts/kconfig/
Dzconf.tab.c_shipped1264 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s"));
1265 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s"));
1266 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s"));
1267 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s"));
/linux-4.1.27/scripts/dtc/
Ddtc-parser.tab.c_shipped1168 YYCASE_(2, YY_("syntax error, unexpected %s, expecting %s"));
1169 YYCASE_(3, YY_("syntax error, unexpected %s, expecting %s or %s"));
1170 YYCASE_(4, YY_("syntax error, unexpected %s, expecting %s or %s or %s"));
1171 YYCASE_(5, YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s"));
/linux-4.1.27/Documentation/cdrom/
Dide-cd229 it was expecting one (on any feasible IRQ). If <n> is negative,
231 it was expecting to receive just one from the CDROM drive.
/linux-4.1.27/Documentation/
Drtc.txt113 than expecting a single battery-backed MC146818 clone on every system.
Dunaligned-memory-access.txt87 access. You'd be expecting field2 to be located at offset 2 bytes into the
DHOWTO425 expecting?
/linux-4.1.27/Documentation/target/
Dtcmu-design.txt202 TCMU device as expecting to be backed by a certain handler, and <path>
/linux-4.1.27/Documentation/block/
Dcfq-iosched.txt289 A2. I would think whenever one is doing synchronous write and not expecting
/linux-4.1.27/arch/arm/crypto/
Daes-armv4.S660 @ expecting the key to already have the enc_key work done (see aes_glue.c)
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq163 * We aren't expecting a bus free, so interrupt
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1949 backing file and expecting that all of the COW files using it will see