Searched full:couple (Results 1 – 25 of 66) sorted by relevance
123
| /Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 7 - Change a couple of defines containing ncr or NCR by their
12 - Fix a couple of printfs:
80 - A couple of comments fixes.
100 - A couple of tiny fixes ...
134 - Fix a couple of gcc/gcc3 warnings.
|
| D | ChangeLog.sym53c8xx | 10 - + A couple of minor changes.
87 - Remove trailing argument #2 from a couple of #undefs.
109 Remove a couple of unused fields from data structures.
|
| /Documentation/ |
| D | irqflags-tracing.txt | 24 Architectures that want to support this need to do a couple of
29 and then a couple of functional changes are needed as well to implement
|
| D | xz.txt | 106 There are a couple of corner cases where things have been simplified
|
| /Documentation/devicetree/bindings/fpga/ |
| D | xilinx-pr-decoupler.txt | 7 couple / enable the bridges which allows traffic to pass through the
|
| /Documentation/arm/nwfpe/ |
| D | todo.rst | 25 There are a couple of ways to approach the implementation of these. One
27 a couple of papers by S. Gal from IBM's research labs in Haifa, Israel that
|
| /Documentation/admin-guide/ |
| D | lcd-panel-cgram.rst | 9 (';'). Each couple of digits represents a line, with 1-bits for each
|
| /Documentation/media/uapi/v4l/ |
| D | dev-radio.rst | 50 Radio devices may have a couple audio controls (as discussed in
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 22 interval, an optional capping mechanism, and a couple of trip points. The
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 12 consumer, and provide a way to couple the two together.
|
| /Documentation/filesystems/ |
| D | inotify.txt | 78 and ioctl(2) or a couple of new system calls. System calls beat ioctls.
|
| D | relay.txt | 71 a couple simple utility functions and a set of examples are provided.
81 tarball) provides a couple of high-level logging functions to the
465 Finally, there are a couple of utility callbacks that can be used for
|
| D | journalling.rst | 72 Unfortunately there a couple of ways the journal layer can cause a
|
| D | debugfs.txt | 192 There are a couple of other directory-oriented helper functions:
|
| /Documentation/admin-guide/laptops/ |
| D | toshiba_haps.rst | 56 a couple HCI (Hardware Configuration Interface) calls (0x6D and 0xA6) are
|
| /Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 94 a strong indication, for a couple of reasons:
|
| /Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 35 hardware level. A couple of wiki pages by Texas Instruments and Analog
98 resources and initialising a couple of circuits. To do so, it needs to
274 data. The next couple of instructions (line 12 and 14) are used as a
680 These are only a couple of the quirks found in the JZ4740 USB device
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 317 about 10 threads. Have a couple of threads execute execve,
318 a couple _exit and the rest unshare with different combination
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 18 test at least a couple of times in a row for confidence. [This is necessary,
106 and "processors" up to "core" (repeat the test on each level a couple of times
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 134 couple specified by the regulator-coupled-with property.
|
| /Documentation/crypto/ |
| D | async-tx-api.txt | 209 A couple caveats to note when implementing a driver and consumer:
|
| D | devel-algos.rst | 143 There are a couple of specifics to the asynchronous interface.
|
| /Documentation/vm/ |
| D | numa.rst | 9 This question can be answered from a couple of perspectives: the
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 15 To configure a DSA switch a couple of commands need to be executed. In this
|
| /Documentation/networking/ |
| D | msg_zerocopy.rst | 140 every couple of send calls.
|
123