/openbmc/linux/arch/powerpc/xmon/ |
H A D | ansidecl.h | 2 /* ANSI and traditional C compatibility macros 8 /* ANSI and traditional C compatibility macros 12 Macro ANSI C definition Traditional C definition 28 parentheses. ARGLIST becomes the argument list in traditional C. 31 ANSI C, and the type declarations in traditional C. Arguments should 44 parentheses). In traditional C it is `NAME()'.
|
/openbmc/qemu/docs/system/devices/ |
H A D | ivshmem-flat.rst | 5 making them unsuitable for the use of the traditional ivshmem device modeled as 14 device to be used together with the traditional ivshmem, enabling communication 15 between, for instance, an aarch64 VM (using the traditional ivshmem device and
|
/openbmc/openbmc/poky/documentation/kernel-dev/ |
H A D | intro.rst | 118 development. Alternatively, you can use traditional kernel 128 Using traditional kernel development requires that you have the 131 ":ref:`kernel-dev/common:getting ready for traditional kernel development`" 142 If you are using traditional kernel development, you edit the source 144 ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`"
|
H A D | common.rst | 43 and not through traditional kernel workflow methods. The remainder of 147 Getting Ready for Traditional Kernel Development 150 Getting ready for traditional kernel development using the Yocto Project 156 traditional kernel development flow with the Yocto Project. Completing 158 source as described in the ":ref:`kernel-dev/common:using traditional kernel development to patch t… 286 using traditional kernel development steps. For a continued example, see 287 the ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`" 547 ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`" 822 Using Traditional Kernel Development to Patch the Kernel 826 traditional kernel development (i.e. not using ``devtool`` [all …]
|
/openbmc/u-boot/doc/ |
H A D | README.fdt-overlays | 7 Overlays require slightly different syntax compared to traditional overlays. 24 Building an overlay follows the same process as building a traditional dtb. 99 6. Boot system like you would do with a traditional dtb.
|
/openbmc/u-boot/disk/ |
H A D | Kconfig | 15 - CONFIG_DOS_PARTITION MS Dos partition table, traditional on the 44 traditional on the Intel architecture, USB sticks, etc.
|
/openbmc/openbmc/meta-openembedded/meta-xfce/recipes-panel-plugins/mount/xfce4-mount-plugin/ |
H A D | 0001-check-for-fstab.h-during-configure.patch | 33 …dnl Add -traditional to output variable CC if using the GNU C compiler and ioctl does not work pro…
|
/openbmc/openbmc/poky/meta/recipes-devtools/m4/ |
H A D | m4-1.4.19.inc | 1 SUMMARY = "Traditional Unix macro processor" 3 DESCRIPTION = "GNU m4 is an implementation of the traditional Unix macro processor. It is mostly S…
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-bwc.rst | 30 Traditional (UP-EDF) bandwidth control is something like: 44 (the traditional WCET). This effectively allows u to be smaller, 90 bandwidth group. This represents the traditional work-conserving behavior for 103 any unused bandwidth. It makes the traditional bandwidth control behavior for
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 049 | 61 echo "== 1. Traditional size parameter ==" 82 echo "== 4. Specify size twice (-o and traditional parameter) =="
|
/openbmc/linux/Documentation/sphinx/ |
H A D | kerneldoc-preamble.sty | 109 %% for Traditional Chinese 161 %% for Traditional Chinese 218 Translations of Simplified Chinese (zh\_CN), Traditional Chinese
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/ |
H A D | source-han-sans-tw-fonts_2.004.bb | 3 SUMMARY = "Adobe OpenType Pan-CJK font family for Traditional Chinese"
|
/openbmc/qemu/.gitlab-ci.d/ |
H A D | stages.yml | 2 # - build (for traditional build and test or first stage build)
|
/openbmc/linux/arch/sh/include/asm/ |
H A D | pgtable-2level.h | 8 * traditional two-level paging structure
|
/openbmc/linux/arch/x86/include/asm/ |
H A D | pgtable_32_types.h | 7 * implements both the traditional 2-level x86 page tables and the
|
H A D | pgtable-2level_types.h | 26 * traditional i386 two-level paging structure:
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python3-pyparsing_3.2.1.bb | 3 and executing simple grammars, vs. the traditional lex/yacc approach, or \
|
/openbmc/linux/tools/testing/selftests/net/ |
H A D | test_vxlan_vnifiltering.sh | 195 # VTYPE = vxlan device type. "default = traditional device, metadata = metadata device 333 # create non-vnifiltering traditional vni device 335 log_test $? 0 "Create traditional vxlan device" 506 # check VM connectivity over traditional/non-vxlan filtering vxlan devices 508 log_test $? 0 "VM connectivity over traditional vxlan (ipv4 default rdst)" 511 log_test $? 0 "VM connectivity over traditional vxlan (ipv6 default rdst)"
|
/openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/ |
H A D | common-auth | 8 # traditional Unix authentication mechanisms.
|
/openbmc/openbmc/poky/meta/recipes-support/re2c/ |
H A D | re2c_4.0.2.bb | 2 …pression matching. As a result this allows a much broader range of use than any traditional lexer."
|
/openbmc/linux/Documentation/filesystems/ |
H A D | ubifs.rst | 13 is completely different to any traditional file-system in Linux, like 38 It should be quite obvious why UBIFS is very different to traditional
|
/openbmc/u-boot/include/bedbug/ |
H A D | bedbug.h | 20 #define __P(protos) () /* traditional C preprocessor */
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libio/ |
H A D | libio-stringy-perl_2.111.bb | 3 traditional and object-oriented i/o on things *other* than normal \
|
/openbmc/openbmc/poky/meta/recipes-support/libcap-ng/ |
H A D | libcap-ng.inc | 3 with POSIX capabilities much easier than the traditional libcap library."
|
/openbmc/linux/Documentation/locking/ |
H A D | percpu-rw-semaphore.rst | 8 The problem with traditional read-write semaphores is that when multiple
|