Searched full:wrong (Results 1 – 25 of 180) sorted by relevance
12345678
| /Documentation/driver-api/mei/ |
| D | mei.rst | 106 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
107 EINVAL Wrong IOCTL Number
143 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
144 EINVAL Wrong IOCTL Number or tag == 0
172 EINVAL Wrong IOCTL Number
197 EINVAL Wrong IOCTL Number
|
| /Documentation/networking/ |
| D | xfrm_proc.rst | 33 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
37 e.g. SA key is wrong
58 e.g. Inbound SAs are correct but SP rule is wrong
|
| /Documentation/process/ |
| D | management-style.rst | 51 Namely that you are in the wrong job, and that **they** should be managing
62 can be made small by just always making sure that if you were wrong (and
63 you **will** be wrong), you can always undo the damage later by
65 **two** inconsequential decisions - the wrong one **and** the right one.
91 wrong is sometimes very hard indeed.
103 might be the wrong thing. You should always reserve the right to change
130 something wrong with both projects, and the reason the people involved
131 couldn't decide was that they were both wrong. You end up coming up
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
252 somebody else puts on airs, it **really** rubs us the wrong way. You may
|
| /Documentation/hwmon/ |
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
|
| D | thmc50.rst | 66 A typical symptom of wrong setting is a fan forced to full speed.
|
| /Documentation/power/ |
| D | tricks.rst | 15 wrong, force fsck when you have a chance]
|
| /Documentation/ABI/testing/ |
| D | debugfs-ec | 21 not get switched on again after you did a wrong write.
|
| D | sysfs-class-fpga-manager | 13 wrong during FPGA programming (something that the driver can't
|
| /Documentation/admin-guide/ |
| D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
|
| /Documentation/admin-guide/media/ |
| D | faq.rst | 187 address is wrong, ``dvb_net`` won't get any input; thus you have to
189 packets at all then maybe the PID is wrong. If there are error packets,
190 then either the PID is wrong or the stream does not conform to
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
76 This rather vague error means something went wrong when
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | lltc,ltc294x.yaml | 37 Can be negative value when the battery has been connected to the wrong end of the resistor.
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 64 It's a 'Something is wrong, I give up!' type of error.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cpuacct.rst | 46 - It is theoretically possible to see wrong values for user and system times.
|
| /Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 18 - Wrong residual values were returned in some situations.
47 - Remove a wrong cpu_to_scr() (np->targtbl_ba)
|
| D | qlogicfas.rst | 62 Don't enable all the speedups first. If anything is wrong, they will make
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 79 It's a 'Something is wrong, I give up!' type of error.
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 54 went wrong, but it is impossible to tell what order the blocks were linked into
100 mis-directed writes - a write might be misdirected to the wrong LUN and so be
101 written to the "correct block" of the wrong filesystem. Hence location
121 freespace btree block written to the wrong AG).
|
| /Documentation/w1/slaves/ |
| D | w1_ds2413.rst | 53 The driver is checking this complement, and when it is wrong then it is
|
| /Documentation/gpu/amdgpu/ |
| D | debugging.rst | 21 out what is going wrong in your application. A page fault in your kernel
|
| /Documentation/devicetree/bindings/regulator/ |
| D | palmas-pmic.txt | 50 ti,smps-range - OTP has the wrong range set for the hardware so override
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | fsl,ls-extirq.yaml | 109 # wrong.
|
| /Documentation/driver-api/firmware/ |
| D | request_firmware.rst | 77 If something went wrong request_firmware() returns non-zero and fw_entry
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-frequency.rst | 100 field is wrong.
|
| /Documentation/security/ |
| D | siphash.rst | 27 If you're not deriving your key from here, you're doing it wrong.
150 If you're not deriving your key from here, you're doing it wrong.
|
12345678