Searched full:reason (Results 1 – 25 of 327) sorted by relevance
12345678910>>...14
| /Documentation/ABI/testing/ |
| D | sysfs-platform-power-on-reason | 5 Description: Shows system power on reason. The following strings/reasons can
10 "unknown reason".
|
| /Documentation/networking/ |
| D | lapb-module.rst | 44 void (*connect_confirmation)(int token, int reason);
45 void (*connect_indication)(int token, int reason);
46 void (*disconnect_confirmation)(int token, int reason);
47 void (*disconnect_indication)(int token, int reason);
237 void (*connect_confirmation)(void *token, int reason);
240 being requested by a call to lapb_connect_request (see above). The reason is
245 void (*connect_indication)(void *token, int reason);
248 system. The value of reason is always LAPB_OK.
252 void (*disconnect_confirmation)(void *token, int reason);
255 driver has called lapb_disconnect_request (see above). The reason indicates
[all …]
|
| /Documentation/translations/ |
| D | index.rst | 36 maintain translations aligned as much as they can. For this reason there is
53 adapted to fit a different language. For this reason, when viewing
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 76 max-reason:
83 See include/linux/kmsg_dump.h KMSG_DUMP_* for other kmsg dump reason values.
84 Setting this to 0 (KMSG_DUMP_UNDEF), means the reason filtering will be
|
| /Documentation/admin-guide/ |
| D | abi-obsolete.rst | 7 The description of the interface will document the reason why it is
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 30 # other bells in the system cannot negate. The reason for this issue is
33 # more important reason is that kconfig does not check for dependencies listed
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 35 reason. With the help of gzvm module, the hypervisor would be able to manipulate
61 handled by host VM directly for performance reason. Irqfd is also implemented
|
| /Documentation/arch/x86/ |
| D | iommu.rst | 91 reason and device that caused it is printed on the console.
131 DMAR:[fault reason 05] PTE Write access is not set
133 DMAR:[fault reason 05] PTE Write access is not set
|
| /Documentation/gpu/amdgpu/display/ |
| D | index.rst | 8 reason, our Display Core Driver is divided into two pieces:
|
| /Documentation/trace/rv/ |
| D | monitor_wwnr.rst | 29 This model is broken, the reason is that a task can be running
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 26 when saving or at commit time. However, if for some reason reformatting
158 reason. In almost all cases, a fallible approach should be used, typically
170 While sometimes the reason might look trivial and therefore unneeded,
|
| /Documentation/powerpc/ |
| D | mpc52xx.rst | 40 reason.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 92 pre_patch callback or for any other reason.
99 started for some reason (e.g., if another object failed to patch),
|
| /Documentation/core-api/ |
| D | dma-isa-lpc.rst | 56 thing. The reason for this is that the function isa_virt_to_bus()
90 using claim_dma_lock(). The reason is that some DMA operations are
|
| /Documentation/power/ |
| D | freezing-of-tasks.rst | 63 hibernation operation will be cancelled. For this reason, freezable kernel
106 1. The principal reason is to prevent filesystems from being damaged after
130 3. The third reason is to prevent user space processes and some kernel threads
160 4. Another reason for freezing tasks is to prevent user space processes from
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 101 reason ``SDTX_DETACH_TIMEDOUT`` (see :ref:`events` for details).
117 sent with the cancel reason indicating the specific failure.
149 (``SDTX_EVENT_CANCEL``) with the corresponding cancel reason.
339 failure. The reason for cancellation is given in the event payload detailed
371 * - ``reason``
373 - Reason for cancellation.
|
| /Documentation/mm/ |
| D | page_frags.rst | 37 way of tearing down a page cache. For this reason __page_frag_cache_drain
|
| /Documentation/userspace-api/media/v4l/ |
| D | rw.rst | 41 mapping I/O can be inadequate for some devices we have no reason to
|
| /Documentation/admin-guide/pm/ |
| D | intel_epb.rst | 40 example, SMT siblings or cores in one package). For this reason, updating the
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 67 - Do not reparent a tree without a good reason to do so. Just being on a
69 generally a good reason.
187 Another reason for doing merges of upstream or another subsystem tree is to
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 20 The main application for this is remote attestation and the reason why
|
| /Documentation/devicetree/bindings/thermal/ |
| D | mediatek-thermal.txt | 5 instead it directly controls the AUXADC via AHB bus accesses. For this reason
|
| /Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 59 timestamp and for this reason one can use the IIO core defined
|
| /Documentation/networking/device_drivers/fddi/ |
| D | skfp.rst | 93 Reason:
120 Reason:
|
| /Documentation/hwmon/ |
| D | adm1025.rst | 47 kind of strange since both are useful, and the reason for designing the
|
12345678910>>...14