| /linux-4.1.27/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 77 echo $FUNCNAME $memory: unexpected fail >&2
79 echo $FUNCNAME $memory: unexpected offline >&2
88 echo $FUNCNAME $memory: unexpected success >&2
90 echo $FUNCNAME $memory: unexpected online >&2
99 echo $FUNCNAME $memory: unexpected fail >&2
101 echo $FUNCNAME $memory: unexpected offline >&2
110 echo $FUNCNAME $memory: unexpected success >&2
112 echo $FUNCNAME $memory: unexpected offline >&2
|
| /linux-4.1.27/tools/testing/selftests/cpu-hotplug/ |
| D | cpu-on-off-test.sh | 91 echo $FUNCNAME $cpu: unexpected fail >&2
93 echo $FUNCNAME $cpu: unexpected offline >&2
102 echo $FUNCNAME $cpu: unexpected success >&2
104 echo $FUNCNAME $cpu: unexpected online >&2
113 echo $FUNCNAME $cpu: unexpected fail >&2
115 echo $FUNCNAME $cpu: unexpected offline >&2
124 echo $FUNCNAME $cpu: unexpected success >&2
126 echo $FUNCNAME $cpu: unexpected offline >&2
|
| /linux-4.1.27/arch/tile/kernel/ |
| D | unaligned.c | 319 bool unexpected = false; in check_regs() local
321 unexpected = true; in check_regs()
324 unexpected = true; in check_regs()
328 unexpected = true; in check_regs()
331 unexpected = true; in check_regs()
333 return unexpected; in check_regs()
579 bool unexpected = false; in jit_bundle_gen() local
646 unexpected = true; in jit_bundle_gen()
665 unexpected = true; in jit_bundle_gen()
675 unexpected = true; in jit_bundle_gen()
[all …]
|
| /linux-4.1.27/drivers/infiniband/hw/ipath/ |
| D | ipath_intr.c | 1071 static unsigned unexpected = 0; in ipath_intr() local
1097 ipath_bad_intr(dd, &unexpected); in ipath_intr()
1116 if (unexpected) in ipath_intr()
1117 unexpected = 0; in ipath_intr()
|
| /linux-4.1.27/Documentation/arm64/ |
| D | legacy_instructions.txt | 57 be unexpected results in the application.
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | floppy.txt | 162 Print a warning message when an unexpected interrupt is received.
167 Don't print a message when an unexpected interrupt is received. This
169 to be an interaction between video and floppy. The unexpected
|
| D | paride.txt | 343 transfers, or unexpected failures, you may wish to increase the
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 1171 about the unexpected token YYTOKEN for the state stack whose top is
1190 /* Number of reported tokens (one for the "unexpected", one per
1206 that there is no unexpected or expected token to report. In that
1263 YYCASE_(1, YY_("syntax error, unexpected %s"));
1264 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"));
1662 { zconf_error("unexpected end statement"); }
1673 zconf_error("unexpected option \"%s\"", kconf_id_strings + (yyvsp[(2) - (4)].id)->name);
[all …]
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 1246 about the unexpected token YYTOKEN for the state stack whose top is
1265 /* Number of reported tokens (one for the "unexpected", one per
1281 that there is no unexpected or expected token to report. In that
1338 YYCASE_(1, YY_("syntax error, unexpected %s"));
1339 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"));
1908 error_with_pos("unexpected second declaration name");
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 1074 about the unexpected token YYTOKEN for the state stack whose top is
1092 /* Number of reported tokens (one for the "unexpected", one per
1108 that there is no unexpected or expected token to report. In that
1167 YYCASE_(1, YY_("syntax error, unexpected %s"));
1168 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/scripts/ |
| D | spelling.txt | 985 unexecpted||unexpected
986 unexpectd||unexpected
987 unexpeted||unexpected
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | SoundPro | 38 settings can have unexpected effects. Use the WSS mixer for best results.
|
| /linux-4.1.27/Documentation/arm/ |
| D | kernel_mode_neon.txt | 85 instructions appearing in unexpected places if no special care is taken.
|
| /linux-4.1.27/Documentation/ |
| D | binfmt_misc.txt | 121 cause unexpected behaviour and can be a security hazard.
|
| D | robust-futex-ABI.txt | 133 exits (perhaps it gets an unexpected signal 9 in the middle of
|
| D | email-clients.txt | 28 Don't send patches with "format=flowed". This can cause unexpected
|
| D | oops-tracing.txt | 249 some unexpected page flags.
|
| D | applying-patches.txt | 168 A message similar to "patch: **** unexpected end of file in patch" or "patch
|
| D | kprobes.txt | 260 and it causes an unexpected result.
|
| /linux-4.1.27/drivers/mmc/host/ |
| D | sdhci.c | 2567 u32 intmask, mask, unexpected = 0; in sdhci_irq() local
2645 unexpected |= intmask; in sdhci_irq()
2657 if (unexpected) { in sdhci_irq()
2659 mmc_hostname(host->mmc), unexpected); in sdhci_irq()
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | CMIPCI.txt | 253 problem (especially unexpected behavior of mixer), please attach the
|
| /linux-4.1.27/Documentation/i2c/ |
| D | instantiating-devices | 236 unexpected address.
|
| /linux-4.1.27/Documentation/serial/ |
| D | tty.txt | 101 handle unexpected calls. Must not sleep.
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README | 387 the interface's link. Note that this can cause unexpected dialouts,
391 "manual" is a dial mode created to prevent the unexpected dialouts.
|
| /linux-4.1.27/Documentation/ioctl/ |
| D | ioctl-number.txt | 45 error rather than some unexpected behaviour.
|
| /linux-4.1.27/Documentation/vm/ |
| D | frontswap.txt | 110 underutilized RAM (e.g. with "selfballooning"), sudden unexpected
|
| /linux-4.1.27/Documentation/networking/ |
| D | timestamping.txt | 456 software time stamping and therefore could lead to unexpected deltas
|
| D | ip-sysctl.txt | 101 unexpected packet loss. The current default value is calculated
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig | 674 be unexpected results in the applications.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | f2fs.txt | 70 This cleaning job may cause unexpected long delays, so the most important goal
|
| D | ext4.txt | 506 zeroout, unexpected ENOSPC, or possible data
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ncr53c8xx.txt | 1041 it. By the way, if you experience badnesses like 'unexpected disconnections',
1285 When the driver detects an unexpected error condition, it may display a
|
| D | ChangeLog.sym53c8xx | 24 - Fix an issue in the ncr_int_udc() (unexpected disconnect)
|
| D | sym53c8xx_2.txt | 611 When the driver detects an unexpected error condition, it may display a
|
| D | ChangeLog.lpfc | 591 * Ignore more unexpected completions in lpfc_nportdisc.c.
595 * Introduce and use less lethal event handler for unexpected
|
| D | ChangeLog.1992-1997 | 1927 * aha1542.c: Handle unexpected interrupts better.
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 612 This prevents unexpected resource control from a hidden css and
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 2120 * the host. Additionally, properly catch unexpected non-packet
2172 * The unexpected nonpkt phase handler assumes that any
|
| /linux-4.1.27/Documentation/RCU/ |
| D | whatisRCU.txt | 999 a synchronization primitive is a bit unexpected. ;-)
|
| /linux-4.1.27/drivers/video/fbdev/ |
| D | Kconfig | 38 device-aware may cause unexpected results. If unsure, say N.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 439 and incurs unexpected behavior.
|