Searched full:appropriate (Results 1 – 25 of 429) sorted by relevance
12345678910>>...18
| /Documentation/admin-guide/ |
| D | kernel-parameters.rst | 106 AX25 Appropriate AX.25 support is enabled.
119 HW Appropriate hardware is enabled.
125 ISDN Appropriate ISDN support is enabled.
127 JOY Appropriate joystick support is enabled.
139 MOUSE Appropriate mouse support is enabled.
142 NET Appropriate network support is enabled.
143 NFS Appropriate NFS support is enabled.
153 PS2 Appropriate PS/2 support is enabled.
159 SCSI Appropriate SCSI support is enabled.
|
| /Documentation/locking/ |
| D | hwspinlock.rst | 28 appropriate user process.
83 appropriate error code on failure (e.g. -EINVAL if the hwspinlock
93 hwspinlock; returns 0 on success, or an appropriate error code on failure
111 Returns 0 when successful and an appropriate error code otherwise (most
126 Returns 0 when successful and an appropriate error code otherwise (most
143 Returns 0 when successful and an appropriate error code otherwise (most
160 Returns 0 when successful and an appropriate error code otherwise (most
176 Returns 0 when successful and an appropriate error code otherwise (most
194 Returns 0 on success and an appropriate error code otherwise (most
210 Returns 0 on success and an appropriate error code otherwise (most
[all …]
|
| /Documentation/staging/ |
| D | rpmsg.rst | 39 expose appropriate user space interfaces, if needed.
61 arrive, the rpmsg core dispatches them to the appropriate driver according
87 Returns 0 on success and an appropriate error value on failure.
111 Returns 0 on success and an appropriate error value on failure.
136 Returns 0 on success and an appropriate error value on failure.
153 Returns 0 on success and an appropriate error value on failure.
174 Returns 0 on success and an appropriate error value on failure.
195 Returns 0 on success and an appropriate error value on failure.
205 appropriate callback handler) by means of an rpmsg_endpoint struct.
261 Returns 0 on success, and an appropriate error value on failure.
|
| D | remoteproc.rst | 44 Returns 0 on success, and an appropriate error value otherwise.
59 Returns 0 on success, and an appropriate error value otherwise.
157 Returns 0 on success and an appropriate error code otherwise.
219 On success, 0 should be returned, and on failure, an appropriate error code.
222 On success, 0 is returned, and on failure, an appropriate error code.
|
| /Documentation/infiniband/ |
| D | user_verbs.rst | 12 libibverbs also requires appropriate device-dependent kernel and
64 To create the appropriate character device files automatically with
75 appropriate MODE or GROUP to the udev rule.
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 77 appropriate by system administrators.
188 appropriate process context structures, populates it with values from
196 task. Therefore unshare() has to take appropriate task_lock()
214 appropriate context structures and then associate them with the
222 structure, if the appropriate bit is set in the flags argument.
250 and duplicated the appropriate structure and the second component
253 These dup_* functions allocated and duplicated the appropriate
274 modify appropriate context pointers, and release the
311 unshares the appropriate structure. Verify that unsharing
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power-twl4030 | 9 "auto" draw power as appropriate for detected
30 "auto" draw power as appropriate for detected
|
| D | sysfs-class-net-phydev | 26 This ID is used to match the device with the appropriate
37 appropriate mode for its data lines to the PHY hardware.
|
| D | sysfs-bus-iio-proximity | 20 The appropriate values to take is dependent on both the
|
| D | sysfs-devices-online | 15 updated as appropriate.
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 79 appropriate number of macroblocks to decode a full
128 this pixel format. The output buffer must contain the appropriate number
169 this pixel format. The output buffer must contain the appropriate number
192 this pixel format. The output buffer must contain the appropriate number
221 Buffers associated with this pixel format must contain the appropriate
273 this pixel format. The output buffer must contain the appropriate number
|
| D | dev-decoder.rst | 262 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
285 * The ``CAPTURE`` format will be updated with an appropriate frame buffer
309 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
334 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT``.
411 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
441 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
524 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
545 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
613 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
627 a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
[all …]
|
| /Documentation/arch/arm/sa1100/ |
| D | serial_uart.rst | 41 In addition to the creation of the appropriate device nodes above, you
50 - don't forget to add 'ttySA0', 'console', or the appropriate tty name
|
| /Documentation/i2c/ |
| D | i2c-address-translators.rst | 15 forwards transactions from upstream to the appropriate downstream port
31 an available alias. Maintaining an appropriate pool of available aliases
87 2. When the attach callback is called pick an appropriate alias,
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 32 socket and a poll notification will be sent to the appropriate
43 appropriate `power[1-*]_alarm` file to indicate that capping has begun, and the
|
| /Documentation/driver-api/phy/ |
| D | samsung-usb2.rst | 27 the appropriate compatible string. In addition, this file contains
105 by modifying appropriate registers.
107 Final change to the driver is adding appropriate compatible value to the
|
| /Documentation/mm/ |
| D | overcommit-accounting.rst | 14 Always overcommit. Appropriate for some scientific
25 allocation as appropriate.
|
| /Documentation/devicetree/bindings/arm/altera/ |
| D | socfpga-sdram-edac.txt | 8 appropriate format for the IRQ controller.
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 45 and are expected to take appropriate and fair corrective action in response to
70 and will result in a response that is deemed necessary and appropriate
|
| /Documentation/arch/s390/ |
| D | config3270.sh | 14 # 3. Issue "telinit q" or reboot, as appropriate.
50 # and add appropriate mknod and mingetty lines to our files
|
| /Documentation/networking/ |
| D | secid.rst | 17 cases, as may be appropriate.
|
| /Documentation/devicetree/bindings/perf/ |
| D | arm,coresight-pmu.yaml | 28 array of phandles to the appropriate CPU node(s)
|
| /Documentation/w1/ |
| D | w1-generic.rst | 39 and two byte address. At this step bus is reset and appropriate device
67 You can call above methods by reading appropriate sysfs files.
132 appropriate family driver. Allows to read/write binary data.
|
| /Documentation/devicetree/ |
| D | dynamic-resolution-notes.rst | 15 appropriate __fixups__ & __local_fixups__ nodes.
|
| /Documentation/networking/device_drivers/ethernet/smsc/ |
| D | smc9.rst | 28 Make will give you the appropriate options for various kernel support.
|
12345678910>>...18