Searched refs:style (Results 1 – 13 of 13) sorted by relevance
2 <style type="text/css" id="style2">4 </style>34 <path d="M2 1 0 0l2-1v2" style="stroke:none" id="path12"/>42 …<path class="st1" id="rect30" style="fill:url(#linearGradient226)" d="M0 459.587h153.071v36.85H0z"…46 …<path class="st1" id="rect37" style="fill:url(#linearGradient228)" d="M0 459.587h153.071v36.85H0z"…49 …<path class="st1" id="rect44" style="fill:url(#linearGradient230)" d="M0 459.587h153.071v36.85H0z"…53 …<path class="st1" id="rect51" style="fill:url(#linearGradient232)" d="M0 459.587h153.071v36.85H0z"…56 …<path class="st1" id="rect56" style="fill:url(#linearGradient234)" d="M0 459.587h153.071v36.85H0z"…59 …<path class="st1" id="rect61" style="fill:url(#linearGradient236)" d="M0 459.587h153.071v36.85H0z"…62 …<path class="st1" id="rect66" style="fill:url(#linearGradient238)" d="M0 459.587h153.071v36.85H0z"…[all …]
1 …s:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" style="fill:none;fill-ru…2 <style type="text/css" id="style9">4 </style>6 …" refX="-7.04" orient="auto" markerUnits="strokeWidth" overflow="visible" style="fill:#000;fill-op…15 …" refX="-6.68" orient="auto" markerUnits="strokeWidth" overflow="visible" style="fill:#eb94e0;fill…19 <path d="M2 1 0 0l2-1v2" style="stroke:none" id="path11"/>111 …<path d="M0 588.19h144.72" id="path176" style="marker-end:url(#mrkr4-107);stroke:#00b0f0;stroke-li…
1 …s:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" style="fill:none;fill-ru…2 <style type="text/css" id="style740">4 </style>6 …" refX="-7.04" orient="auto" markerUnits="strokeWidth" overflow="visible" style="fill:#000;fill-op…10 <path d="M2 1 0 0l2-1v2" style="stroke:none" id="path742"/>
32 uint64_t style : 8; member105 uint64_t style : 8;
16 # The config files must export variables in the shell style
44 To filter packets in style of *tshark*, use the ``-f`` flag.
12 This document specifies the preferred style for source files in the DPDK source tree.13 … coding guidelines and the FreeBSD 7.2 Kernel Developer's Manual (see man style(9)), but was heavi…20 * The code style should be consistent within each individual file.21 * In the case of creating new files, the style should be consistent within each file in a given dir…161 Additional style guidance for the use of conditional compilation macros:238 …, the project uses the form uintXX_t (from stdint.h) instead of older BSD-style integer identifier…448 As with all style guidelines, code should match style already in use in an existing file.638 * Old-style (K&R) function declaration should not be used, use ANSI function declarations instead a…
195 Here are some guidelines in relation to the style of the documentation:593 * Use ``@`` style Doxygen commands instead of ``\`` style commands.623 * Doxygen supports Markdown style syntax such as bold, italics, fixed width text and lists.
624 it as static. This is a coding style choice.
262 '-Wold-style-definition',
30 a static configuration the developer may need a fixed MAC address style.
38 * Added peek style API for ``rte_ring``.
404 * C99-style flexible arrays were replaced with standard pointers in RSS