Home
last modified time | relevance | path

Searched refs:DOC (Results 1 – 25 of 25) sorted by relevance

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DDOC3 …DOC software") are copyrighted by Douglas C. Schmidt and his research group at Washington Universi…
5 …DOC software in commercial and/or binary software releases and are under no obligation to redistri…
7 …DOC Group at the Institute for Software Integrated Systems (ISIS) and the Center for Distributed O…
9 DOC software is provided with no support and without any obligation on the part of Washington Unive…
H A DAbstyles3 See the file APREAMBL.DOC for a detailed documentation.
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/
H A DACE-TAO-CIAO8 (henceforth referred to as "DOC software") are copyrighted by
11 University, Copyright (c) 1993-2018, all rights reserved. Since DOC
14 DOC software source code and object code produced from the source, as
17 built using DOC software that you release. No copyright statement
21 You can use DOC software in commercial and/or binary software releases
23 that is built using DOC software. Note, however, that you may not
24 misappropriate the DOC software code, such as copyrighting it yourself
25 or claiming authorship of the DOC software code, in a way that will
26 prevent DOC software from being distributed freely using an
28 using DOC software in your software, though we encourage you to let
[all …]
/openbmc/u-boot/scripts/
H A Dfill_scrapyard.py41 DOC='doc/README.scrapyard' variable
137 for line in open(DOC):
144 tmp[3] = get_last_modify_commit(DOC, line_num)
162 os.rename(tmpfile.filename, DOC)
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/emacs/files/
H A Duse-emacs-native-tools-for-cross-compiling.patch37 ## since not all pieces are used on all platforms. But DOC depends
38 ## on all of $lisp, and emacs depends on DOC, so it is ok to use $lisp here.
40 - lisp.mk $(etc)/DOC $(lisp) \
41 +emacs$(EXEEXT): lisp.mk $(etc)/DOC $(lisp) \
46 $(etc)/DOC: $(libsrc)/make-docfile$(EXEEXT) $(doc_obj)
48 $(AM_V_at)rm -f $(etc)/DOC
51 $(SOME_MACHINE_OBJECTS) $(doc_obj) > $(etc)/DOC
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/7zip/
H A D7zip_24.09.bb4 LIC_FILES_CHKSUM = "file://DOC/copying.txt;md5=4fbd65380cdd255951079008b364516c \
5 file://DOC/unRarLicense.txt;md5=9c87ddde469ef94aed153b0951d088de \
6 file://DOC/License.txt;md5=44483e232b64ffca25fe001f3d6418d0"
/openbmc/linux/Documentation/translations/zh_CN/core-api/
H A Didr.rst66 IDR同步的相关内容请见include/linux/idr.h文件中的“DOC: idr sync”。
71 IDA的用法的相关内容请见lib/idr.c文件中的“DOC: IDA description”。
H A Dgeneric-radix-tree.rst16 “DOC: Generic radix trees/sparse arrays”。
/openbmc/linux/Documentation/translations/zh_CN/doc-guide/
H A Dkernel-doc.rst383 这是通过使用带有节标题的 ``DOC:`` 节关键字来实现的。
388 * DOC: Theory of Operation
399 ``DOC:`` 后面的标题用作源文件中的标题，但也用作提取文档注释的标识符。因此，
464 包含 *source* 中由 *title* 标题标识的 ``DOC:`` 文档段落。 *title* 中允许
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libcanberra/files/
H A D0001-remove-dropped-templates.patch31 - @echo ' DOC Rebuilding template files'
50 @echo ' DOC Building XML'
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Dregistry.hpp46 struct DOC struct
199 DOC doc;
/openbmc/linux/Documentation/translations/zh_CN/mm/
H A Dksm.rst26 概述内容请见mm/ksm.c文档中的“DOC: Overview”
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pmdk/
H A Dpmdk_2.1.0.bb24 EXTRA_OEMAKE = "BUILD_EXAMPLES='n' DOC='n' HOST_SYS='${HOST_SYS}' EXTRA_CFLAGS='${SELECTED_OPTIMIZA…
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/libts/
H A D0001-Remove-TEE-driver-external-component.patch177 - DOC "Linux FF-A TEE driver include directory"
215 - DOC "Linux FF-A TEE driver include directory"
/openbmc/u-boot/board/freescale/mx6memcal/
H A DREADME45 [1] - NXP DDR Stress Test Tool - https://community.nxp.com/docs/DOC-105652
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/libyui/libyui/
H A D0001-Use-relative-install-paths-for-CMake.patch30 - FOREACH( p "DOC" LIB INCLUDE CMAKE PKGCONFIG BUILDTOOLS )
/openbmc/linux/Documentation/doc-guide/
H A Dkernel-doc.rst425 This is done by using a ``DOC:`` section keyword with a section title.
430 * DOC: Theory of Operation
441 The title following ``DOC:`` acts as a heading within the source file, but also
512 Include documentation for the ``DOC:`` paragraph identified by *title* in
/openbmc/linux/Documentation/translations/it_IT/doc-guide/
H A Dkernel-doc.rst453 Questo s'ottiene utilizzando la parola chiave ``DOC:`` a cui viene associato
460 * DOC: Theory of Operation
471 Il titolo che segue ``DOC:`` funziona da intestazione all'interno del file
537 Include la documentazione del paragrafo ``DOC:`` identificato dal titolo
/openbmc/linux/Documentation/mm/
H A Dksm.rst18 :DOC: Overview
/openbmc/docs/
H A Dyocto-development.md105 NXP wrote a few examples of [useful](https://community.nxp.com/docs/DOC-94953)
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dcmake.bbclass114 find_program( CMAKE_AR ${OECMAKE_AR} DOC "Archiver" REQUIRED )
/openbmc/linux/drivers/mtd/maps/
H A DKconfig378 up to five memory devices (eg, SRAM, flash, DOC) described by an
/openbmc/linux/Documentation/driver-api/
H A Dmtdnand.rst875 * data bytes. Applies for DOC and AG-AND Renesas HW Reed Solomon generators */
/openbmc/u-boot/
H A DREADME2199 34 common/cmd_doc.c before loading a Image from a DOC device
2207 38 common/cmd_doc.c reading Image header from DOC device OK
2210 -40 common/cmd_doc.c Error reading Image from DOC device
/openbmc/linux/
H A Dopengrok0.0.log[all...]