Searched refs:wrong (Results 1 – 25 of 154) sorted by relevance
1234567
| /linux-3.4.99/Documentation/networking/ |
| D | xfrm_proc.txt | 23 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
26 e.g. SA key is wrong
41 e.g. Inbound SAs are correct but SP rule is wrong
|
| /linux-3.4.99/drivers/staging/comedi/drivers/addi-data/ |
| D | APCI1710_Ttl.c | 819 | -1: The handle parameter of the board is wrong |
820 | -2: The module parameter is wrong |
822 | -4: The selected digital output is wrong |
|
| D | APCI1710_82x54.c | 439 | -1: The handle parameter of the board is wrong |
440 | -2: Module selection wrong |
441 | -3: Timer selection wrong |
445 | -6: Interrupt parameter is wrong |
|
| /linux-3.4.99/Documentation/ |
| D | ManagementStyle | 46 Namely that you are in the wrong job, and that _they_ should be managing
57 can be made small by just always making sure that if you were wrong (and
58 you _will_ be wrong), you can always undo the damage later by
60 _two_ inconsequential decisions - the wrong one _and_ the right one.
85 wrong is sometimes very hard indeed.
97 might be the wrong thing. You should always reserve the right to change
124 something wrong with both projects, and the reason the people involved
125 couldn't decide was that they were both wrong. You end up coming up
208 Things will go wrong, and people want somebody to blame. Tag, you're it.
239 somebody else puts on airs, it _really_ rubs us the wrong way. You may
|
| D | mutex-design.txt | 5 "Why on earth do we need a new mutex subsystem, and what's wrong
8 firstly, there's nothing wrong with semaphores. But if the simpler
|
| /linux-3.4.99/drivers/staging/xgifb/ |
| D | TODO | 9 - remove useless/wrong/unused #ifdef/code/...
|
| /linux-3.4.99/Documentation/EDID/ |
| D | HOWTO.txt | 7 booting or it displays the wrong area. Cases when this happens are:
36 most probably complain about a wrong CRC. Fortunately, the utility also
|
| /linux-3.4.99/drivers/staging/media/cxd2099/ |
| D | TODO | 6 But this is wrong. There are some discussions about the proper way for
|
| /linux-3.4.99/arch/sparc/mm/ |
| D | btfixup.c | 35 static char wrong[] __initdata = "Wrong address for %c fixup %p\n"; variable
138 prom_printf(wrong, type, p); in btfixup()
|
| /linux-3.4.99/Documentation/hwmon/ |
| D | adm1025 | 43 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
|
| D | thmc50 | 55 A typical symptom of wrong setting is a fan forced to full speed.
|
| /linux-3.4.99/arch/x86/boot/ |
| D | setup.ld | 60 . = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
|
| /linux-3.4.99/Documentation/devicetree/bindings/ |
| D | eeprom.txt | 16 manual of your device, that value varies a lot. A wrong value
|
| /linux-3.4.99/Documentation/power/ |
| D | tricks.txt | 13 wrong, force fsck when you have a chance]
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | debugfs-ec | 20 not get switched on again after you did a wrong write.
|
| /linux-3.4.99/Documentation/dvb/ |
| D | faq.txt | 115 which ifconfig outputs. (Note: If the MAC address is wrong,
118 all then maybe the PID is wrong. If there are error packets,
119 then either the PID is wrong or the stream does not conform to
|
| /linux-3.4.99/arch/mips/loongson/ |
| D | Kconfig | 74 this option at first, otherwise, You will get wrong system time.
|
| /linux-3.4.99/Documentation/video4linux/bttv/ |
| D | README.WINVIEW | 13 is wrong. If it doesn't work, send me email.
|
| /linux-3.4.99/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 7 Note that the driver's will not load on the "wrong" hardware,
|
| /linux-3.4.99/tools/perf/config/ |
| D | utilities.mak | 142 # trying too hard and getting things wrong).
152 # trying too hard and getting things wrong).
|
| /linux-3.4.99/arch/cris/arch-v32/mach-fs/ |
| D | dram_init.S | 56 ; is wrong for a group 1 only hardware (such as the grand old
|
| /linux-3.4.99/Documentation/cgroups/ |
| D | cpuacct.txt | 45 - It is theoretically possible to see wrong values for user and system times.
|
| /linux-3.4.99/Documentation/i2c/ |
| D | fault-codes | 14 result for an operation ... it doesn't indicate that anything is wrong
71 This rather vague error means something went wrong when
|
| /linux-3.4.99/fs/befs/ |
| D | ChangeLog | 46 * Fixed bug in befs_find_brun_indirect() that would result in the wrong
250 Subtle, because the old version was only sometimes wrong.
314 This fixed the problmem with wrong file sizes from du and others.
378 * Fixed wrong number of args bug in befs_dump_inode
|
| /linux-3.4.99/drivers/staging/comedi/drivers/ |
| D | poc.c | 200 #ifdef wrong in dac02_ao_winsn()
|
1234567