Searched full:guidelines (Results 1 – 25 of 127) sorted by relevance
123456
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 Probing guidelines17 Close/stop guidelines34 Transmit path guidelines
5 BPF ABI Recommended Conventions and Guidelines v1.09 conventions and guidelines for producing portable BPF program binaries.
106 * See `Xe ASSERTs`_ for general usage guidelines.141 * See `Xe ASSERTs`_ for general usage guidelines.165 * See `Xe ASSERTs`_ for general usage guidelines.
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
4 :Original: Documentation/rust/coding-guidelines.rst178 https://rust-lang.github.io/api-guidelines/naming.html
20 coding-guidelines
188 guidelines in the licensing rules documentation.203 guidelines in the licensing rules documentation.243 guidelines in the licensing rules documentation.
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
218 The guidelines laid out above are just that: guidelines. There will always219 be situations that call out for a different solution, and these guidelines
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.
4 Misc DRM driver uAPI- and feature implementation guidelines
16 firmware-usage-guidelines
23 researcher-guidelines
116 Guidelines for console driver writers120 console drivers must follow these guidelines:
5 pair into a comment according to the placement guidelines in the
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 * Correct the coding style according to Linux guidelines; please read the document
21 A priority ranging from 0 to 255 according to the following guidelines::
13 Guidelines for new compatibles for SoC blocks/components.