Searched full:violations (Results 1 – 15 of 15) sorted by relevance
| /Documentation/process/ |
| D | submit-checklist.rst | 65 1) Check for trivial violations with the patch style checker prior to
67 You should be able to justify all violations that remain in
|
| D | submitting-patches.rst | 204 Check your patch for basic style violations, details of which can be
227 You should be able to justify all violations that remain in your
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 67 layering violations then the recommended way around that is to wrap ``vmalloc``
|
| D | dma-api.rst | 789 violations. If your architecture supports it you can select the "Enable
|
| /Documentation/ABI/testing/ |
| D | debugfs-driver-habanalabs | 124 Description: Dumps all security violations to dmesg. This will also ack
125 all security violations meanings those violations will not be
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl,sec-v4.0-mon.yaml | 18 violations. This also included rtc, system power off and ON/OFF key.
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pamu.txt | 22 interrupt, used for reporting access violations. The second
|
| /Documentation/gpu/ |
| D | drm-vm-bind-locking.rst | 111 lists are manipulated. However, to avoid locking order violations
128 over the gpu_vm_bo and gpu_vma lists to avoid locking-order violations.
477 reclaim context and, again, to avoid locking order violations, we can't
|
| /Documentation/wmi/ |
| D | driver-development-guide.rst | 169 violations, you can invoke it with the following command:
|
| /Documentation/dev-tools/ |
| D | checkpatch.rst | 8 style violations in patches and optionally corrects them. Checkpatch can
12 messages. If your code looks better with the violations, then its probably
|
| /Documentation/hwmon/ |
| D | sysfs-interface.rst | 58 make comparisons of readings to thresholds. This allows violations
|
| /Documentation/networking/dsa/ |
| D | sja1105.rst | 292 of dropped frames, which is a sum of frames dropped due to timing violations,
|
| /Documentation/driver-api/ |
| D | libata.rst | 265 :c:func:`ata_port_freeze` is called when HSM violations or some other
|
| /Documentation/admin-guide/LSM/ |
| D | ipe.rst | 318 checked and policy violations are logged, but the policy is not really
|
| /Documentation/networking/ |
| D | ip-sysctl.rst | 1515 frames. Such violations are normally logged via a kernel warning.
|