Searched full:guidelines (Results 1 – 25 of 105) sorted by relevance
12345
3 Guidelines for Video4Linux pixel format 4CCs6 Guidelines for Video4Linux 4CC codes defined using v4l2_fourcc() are11 Existing 4CCs may not obey these guidelines.
153 … --- Digital Compression and Coding of Continous-Tone Still Images --- Requirements and Guidelines"283 :title: E.B.U. guidelines for Consumer Flat Panel Displays (FPDs)333 :title: VESA and Industry Standards and Guidelines for Computer Display Monitor Timing (DMT)
7 Transmit path guidelines:83 Probing guidelines:89 Close/stop guidelines:
6 * Consider these guidelines before using in-kernel FPU functions:12 * use with the KERNEL_VXR_* constants. Consider these usage guidelines:20 * If you adhere to these guidelines, an interrupted process context
201 files according to the `License identifier syntax`_ guidelines.215 guidelines in the licensing rules documentation.230 guidelines in the licensing rules documentation.277 guidelines in the licensing rules documentation.325 tag/value pair into a comment according to the placement guidelines in382 source files according to the `License identifier syntax`_ guidelines.
187 guidelines in the licensing rules documentation.202 guidelines in the licensing rules documentation.242 guidelines in the licensing rules documentation.
46 guidelines.48 Following these guidelines and selecting valid configuration options
190 guidelines in the licensing rules documentation.205 guidelines in the licensing rules documentation.245 guidelines in the licensing rules documentation.
19 Style Guidelines52 Also read the :ref:`guidelines for the kernel documentation at large <doc_guide>`.84 main process guidelines and documentation <process_index>` for how things work.
14 coding-guidelines
3 Coding Guidelines186 https://rust-lang.github.io/api-guidelines/naming.html
16 firmware-usage-guidelines
116 Guidelines for console driver writers120 console drivers must follow these guidelines:
222 The guidelines laid out above are just that: guidelines. There will always223 be situations that call out for a different solution, and these guidelines
3 * Correct the coding style according to Linux guidelines; please read the document
5 comment according to the placement guidelines in the licensing rules
5 SPDX tag/value pair into a comment according to the placement guidelines
5 according to the placement guidelines in the licensing rules
19 /* Boards following the design guidelines in the developer's manual,
13 Guidelines for new compatibles for SoC blocks/components.
5 tag/value pair into a comment according to the placement guidelines in
230 guidelines in the licensing rules documentation.245 guidelines in the licensing rules documentation.290 guidelines in the licensing rules documentation.337 tag/value pair into a comment according to the placement guidelines in
8 strongly encouraged that they are named and written according to the guidelines13 It is recommended that you only deviate from these guidelines when:
