| /f-stack/app/redis-5.0.5/tests/unit/type/ |
| H A D | incr.tcl | 27 test {INCR fails against key with spaces (left)} { 33 test {INCR fails against key with spaces (right)} { 39 test {INCR fails against key with spaces (both)} { 103 test {INCRBYFLOAT fails against key with spaces (left)} { 110 test {INCRBYFLOAT fails against key with spaces (right)} { 117 test {INCRBYFLOAT fails against key with spaces (both)} {
|
| H A D | hash.tcl | 301 test {HINCRBY fails against hash value with spaces (left)} { 311 test {HINCRBY fails against hash value with spaces (right)} { 373 test {HINCRBYFLOAT fails against hash value with spaces (left)} { 383 test {HINCRBYFLOAT fails against hash value with spaces (right)} {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/ti/ |
| H A D | ti,dra7-dss.txt | 12 - reg: address and length of the register spaces for 'dss' 23 - reg: address and length of the register spaces for 'pll1_clkctrl', 60 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| H A D | ti,omap5-dss.txt | 64 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll' 86 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| H A D | ti,omap4-dss.txt | 83 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll' 105 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
|
| H A D | ti,omap3-dss.txt | 77 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
|
| /f-stack/freebsd/netinet/ |
| H A D | accf_http.c | 203 int i, cc, spaces, inspaces; in soparsehttpvers() local 210 inspaces = spaces = 0; in soparsehttpvers() 219 spaces++; in soparsehttpvers() 228 if (spaces != 2) { in soparsehttpvers()
|
| /f-stack/freebsd/contrib/openzfs/ |
| H A D | CODE_OF_CONDUCT.md | 2 applies to spaces associated with the OpenZFS project, including GitHub.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | marvell,pxa910.txt | 13 "mpmu", "apmu", "apbc", "apbcp". So four reg spaces need to be defined.
|
| H A D | marvell,pxa168.txt | 13 "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/can/ |
| H A D | ti_hecc.txt | 9 - reg: addresses and lengths of the register spaces for 'hecc', 'hecc-ram'
|
| /f-stack/app/redis-5.0.5/tests/unit/ |
| H A D | introspection.tcl | 32 test {CLIENT SETNAME does not accept spaces} {
|
| /f-stack/freebsd/contrib/openzfs/config/ |
| H A D | zfs-meta.m4 | 12 dnl # - KEY is separated from VALUE by a colon and one or more spaces/tabs. 14 dnl # - Leading spaces are ignored.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/usb/ |
| H A D | da8xx-usb.txt | 33 - reg: offset and length of the following register spaces: CPPI DMA Controller,
|
| H A D | am33xx-usb.txt | 57 - reg: offset and length of the following register spaces: USBSS, USB
|
| /f-stack/tools/libxo/doc/ |
| H A D | format-strings.rst | 31 is a padding field containing three spaces of padding, the second is a
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | documentation.rst | 301 * Standard RST indentation is 3 spaces. 302 Code can be indented 4 spaces, especially if it is copied from source files. 305 Convert tabs in embedded code to 4 or 8 spaces. 394 * Fixed width, literal blocks of texts should be indented at least 3 spaces and prefixed with ``::`… 630 * Place the ``@params`` description on separate line and indent it by 2 spaces. 688 Note: postfix comments should be aligned with spaces not tabs in accordance
|
| H A D | coding_style.rst | 238 * Try to make the structure readable by aligning the member names using spaces as shown below. 374 * Indentation is a hard tab, that is, a tab character, not a sequence of spaces, 378 Global whitespace rule in DPDK, use tabs for indentation, spaces for alignment. 380 * Do not put any spaces before a tab for indentation. 384 …Alternatively, the line continuation may use additional spaces to line up to an appropriately poin… 465 * Do not use spaces after function names. 467 * No spaces after ``(`` or ``[`` or preceding the ``]`` or ``)`` characters. 479 * Unary operators do not require spaces, binary operators do.
|
| /f-stack/freebsd/x86/conf/ |
| H A D | NOTES | 42 options SC_CUT_SPACES2TABS # convert leading spaces into tabs
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | interlaken-lac.txt | 26 memory mapped 4KB spaces. The LA commands are then translated into the 30 There are two 4KiB spaces defined within the LAC global register memory map.
|
| /f-stack/dpdk/doc/guides/windows_gsg/ |
| H A D | build_dpdk.rst | 54 Install to a folder without spaces in its name, like ``C:\MinGW``.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/remoteproc/ |
| H A D | ti,omap-remoteproc.yaml | 55 other peripheral device address spaces. This property usually 111 Required names for each of the address spaces defined in
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | secure.txt | 3 ARM CPUs with TrustZone support have two distinct address spaces,
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fsi/ |
| H A D | fsi.txt | 94 Engines are identified by their address under the slaves' address spaces. We
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pci/ |
| H A D | host-generic-pci.yaml | 69 that cover all config, MMIO and I/O spaces in a [mostly] ECAM
|