Searched refs:expecting (Results 1 – 23 of 23) sorted by relevance
| /linux-2.6.39/Documentation/x86/ |
| D | usb-legacy-support.txt | 20 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-2.6.39/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-2.6.39/net/netfilter/ |
| D | nf_conntrack_expect.c | 55 master_help->expecting[exp->class]--; in nf_ct_unlink_expect_report()
327 master_help->expecting[exp->class]++; in nf_ct_expect_insert()
421 master_help->expecting[expect->class] >= p->max_expected) { in __nf_ct_expect_check()
423 if (master_help->expecting[expect->class] in __nf_ct_expect_check()
|
| /linux-2.6.39/include/net/netfilter/ |
| D | nf_conntrack.h | 98 u8 expecting[NF_CT_MAX_EXPECT_CLASSES]; member
|
| /linux-2.6.39/Documentation/connector/ |
| D | connector.txt | 112 are expecting, then it is a new message. If we receive a message and
113 its sequence number is the same as one we are expecting, but its
|
| /linux-2.6.39/Documentation/scsi/ |
| D | scsi-parameters.txt | 113 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 | 1347 was not expecting this to happen. A device may behave so to
|
| /linux-2.6.39/arch/arm/mach-omap1/ |
| D | ams-delta-fiq-handler.S | 150 cmp r10, #0 @ are we expecting start bit?
|
| /linux-2.6.39/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 1000 YY_("syntax error, unexpected %s, expecting %s");
1001 YY_("syntax error, unexpected %s, expecting %s or %s");
1002 YY_("syntax error, unexpected %s, expecting %s or %s or %s");
1003 YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s");
1008 static char const yyexpecting[] = ", expecting %s";
|
| /linux-2.6.39/scripts/genksyms/ |
| D | parse.c_shipped | 1248 YY_("syntax error, unexpected %s, expecting %s");
1249 YY_("syntax error, unexpected %s, expecting %s or %s");
1250 YY_("syntax error, unexpected %s, expecting %s or %s or %s");
1251 YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s");
1256 static char const yyexpecting[] = ", expecting %s";
|
| /linux-2.6.39/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 1199 YY_("syntax error, unexpected %s, expecting %s");
1200 YY_("syntax error, unexpected %s, expecting %s or %s");
1201 YY_("syntax error, unexpected %s, expecting %s or %s or %s");
1202 YY_("syntax error, unexpected %s, expecting %s or %s or %s or %s");
1207 static char const yyexpecting[] = ", expecting %s";
|
| /linux-2.6.39/Documentation/cdrom/ |
| D | ide-cd | 229 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-2.6.39/Documentation/ |
| D | unaligned-memory-access.txt | 87 access. You'd be expecting field2 to be located at offset 2 bytes into the
|
| D | rtc.txt | 113 than expecting a single battery-backed MC146818 clone on every system.
|
| D | HOWTO | 426 expecting?
|
| /linux-2.6.39/drivers/scsi/aic7xxx_old/ |
| D | aic7xxx.seq | 245 * We aren't expecting a
272 * We aren't expecting a
|
| D | aic7xxx.reg | 715 * when we were expecting
|
| /linux-2.6.39/drivers/usb/serial/ |
| D | ChangeLog.history | 230 accidenatly buy the device, expecting it to work with Linux.
|
| /linux-2.6.39/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 163 * We aren't expecting a bus free, so interrupt
|
| /linux-2.6.39/Documentation/uml/ |
| D | UserModeLinux-HOWTO.txt | 1939 backing file and expecting that all of the COW files using it will see
|