| /linux/Documentation/process/ |
| H A D | maintainer-tip.rst | 518 Use C++ style, tail comments when documenting structs in headers to
548 Comments should be added where the operation is not obvious. Documenting
601 Documenting locking requirements
603 Documenting locking requirements is a good thing, but comments are not
737 Please avoid documenting struct members within the declaration, because
|
| /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
|
| /linux/Documentation/ABI/testing/ |
| H A D | dell-smbios-wmi | 33 Documenting class/select/input values is outside of the scope
|
| /linux/Documentation/arch/arm/sunxi/ |
| H A D | clocks.rst | 49 A: The linux-sunxi wiki contains a page documenting the clock registers,
|
| /linux/arch/sh/drivers/pci/ |
| H A D | pci-dreamcast.c | 57 * FIXME: All of this wants documenting to some degree, in gapspci_init()
|
| /linux/tools/memory-model/scripts/ |
| H A D | README | 18 documenting expected results, comparing the actual results to
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | sysfs.rst | 166 suitable for documenting as part of a board support package.
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | video-interfaces.yaml | 66 Documenting bindings for devices
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | fallback-mechanisms.rst | 35 this are worth itemizing and documenting as it justifies the need for the
|
| /linux/Documentation/networking/device_drivers/wifi/intel/ |
| H A D | ipw2100.rst | 70 upon receipt and review of test data documenting that the antennas and
|
| H A D | ipw2200.rst | 84 upon receipt and review of test data documenting that the antennas and
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | specs.rst | 65 sub-property documenting the defined object.
|
| /linux/Documentation/ |
| H A D | conf.py | 181 # The version info for the project you're documenting, acts as replacement for
|
| /linux/Documentation/filesystems/ |
| H A D | ramfs-rootfs-initramfs.rst | 161 documenting the above file format.
|
| /linux/include/media/ |
| H A D | v4l2-common.h | 332 * It doesn't make much sense on documenting them, as what we really want is
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 235 documenting the system architecture. This node would serve to detail the
|
| /linux/LICENSES/dual/ |
| H A D | MPL-1.1 | 186 file documenting the changes You made to create that Covered Code and
|
| /linux/Documentation/doc-guide/ |
| H A D | kernel-doc.rst | 276 #) When documenting nested structs or unions, if the struct/union ``foo``
|
| /linux/Documentation/gpu/ |
| H A D | drm-kms.rst | 492 * It must be standardized, documenting:
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig-language.rst | 718 in documenting basic Kconfig syntax a more precise definition of Kconfig
|
| /linux/drivers/s390/scsi/ |
| H A D | zfcp_dbf.c | 150 * @tag: tag documenting the source
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | commands.h | 389 * See comments documenting "BSM" (bootstrap state machine).
436 * See comments documenting "BSM" (bootstrap state machine).
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 1740 it is for now. The main author of this text hopes documenting the state of the
|
| /linux/drivers/net/wireless/intel/iwlwifi/dvm/ |
| H A D | commands.h | 324 * See comments documenting "BSM" (bootstrap state machine).
|
| /linux/tools/testing/selftests/net/ |
| H A D | fcnal-test.sh | 3163 # bound server, but it does not - hence this is more documenting
|