| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | dell-smbios-wmi | 33 Documenting class/select/input values is outside of the scope
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 109 Instead, the usual system for documenting Rust code is used: the ``rustdoc``
171 writing these comments is not just a good way of documenting what has been
|
| /openbmc/linux/Documentation/arch/arm/sunxi/ |
| H A D | clocks.rst | 49 A: The linux-sunxi wiki contains a page documenting the clock registers,
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | APL-1.0 | 141 …ted or contributed to by that Subsequent Contributor to contain a file documenting the changes, in…
143 …documenting changes resulting in Subsequent Works by revising Part 1 of each copy of the Supplemen…
147 …f any Licensed Work to the extent Part 1 sets out the requirements for documenting changes to the …
149 (e) An example of a set of requirements for documenting changes and contributions made by Subsequen…
|
| H A D | Artistic-1.0 | 35 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | OGTSL | 90 testcases non-standard names, and clearly documenting the
|
| H A D | NBPL-1.0 | 45 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | Artistic-1.0-cl8 | 36 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | OLDAP-1.1 | 46 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | OLDAP-1.2 | 46 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | OLDAP-1.3 | 46 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | Intel | 40 contain a file documenting the changes Licensee made to create that Covered
|
| H A D | Intel-ACPI | 18 …cause all Covered Code to which Licensee contributes to contain a file documenting the changes Lic…
|
| H A D | OLDAP-1.4 | 46 …s, giving the non-standard executables non-standard names, and clearly documenting the differences…
|
| H A D | Artistic-2.0 | 95 from the Standard Version, including, but not limited to, documenting
|
| /openbmc/linux/arch/sh/drivers/pci/ |
| H A D | pci-dreamcast.c | 57 * FIXME: All of this wants documenting to some degree, in gapspci_init()
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-tip.rst | 504 Comments should be added where the operation is not obvious. Documenting
557 Documenting locking requirements
559 Documenting locking requirements is a good thing, but comments are not
693 Please avoid documenting struct members within the declaration, because
|
| /openbmc/linux/tools/memory-model/scripts/ |
| H A D | README | 18 documenting expected results, comparing the actual results to
|
| /openbmc/bmcweb/ |
| H A D | OWNERS | 60 # patchset, adding your name to the list below, documenting some evidence of
|
| /openbmc/docs/tof/ |
| H A D | contract.md | 56 - Documenting decisions on GitHub.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Led/ |
| H A D | README.md | 108 Describing the Physical LED here just for documenting it and strictly NOT to be
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 118 - Layers should be documenting where they don’t support normal "core"
|
| /openbmc/docs/designs/ |
| H A D | physical-topology.md | 27 Changes to phosphor-dbus-interfaces documenting new Associations have been
|
| /openbmc/linux/Documentation/admin-guide/gpio/ |
| H A D | sysfs.rst | 162 suitable for documenting as part of a board support package.
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | video-interfaces.yaml | 66 Documenting bindings for devices
|