| /freebsd/contrib/llvm-project/clang/include/clang/StaticAnalyzer/Checkers/ |
| H A D | Checkers.td | 147 Documentation<HasDocumentation>;
154 Documentation<HasDocumentation>,
209 Documentation<HasDocumentation>,
221 Documentation<HasDocumentation>;
226 Documentation<HasDocumentation>;
230 Documentation<HasDocumentation>;
234 Documentation<HasDocumentation>;
238 Documentation<HasDocumentation>;
242 Documentation<NotDocumented>,
248 Documentation<HasDocumentation>;
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | Attr.td | 9 // The documentation is organized by category. Attributes can have category-
10 // specific documentation that is collated within the larger document.
27 currently missing documentation.
32 // in the documentation. This category should be used only when we _want_
38 // documentation. Otherwise, the documentation will specify the attribute has
43 // Specifies the documentation to be associated with the given category.
44 class Documentation {
60 // Specifies that the attribute is explicitly omitted from the documentation,
62 def InternalOnly : Documentation {
67 // documentation.
[all …]
|
| H A D | DiagnosticCommentKinds.td | 10 let CategoryName = "Documentation Issue" in {
17 InGroup<Documentation>, DefaultIgnore;
21 InGroup<Documentation>, DefaultIgnore;
51 InGroup<Documentation>, DefaultIgnore;
55 InGroup<Documentation>, DefaultIgnore;
68 InGroup<Documentation>, DefaultIgnore;
77 InGroup<Documentation>, DefaultIgnore;
84 InGroup<Documentation>, DefaultIgnore;
90 InGroup<Documentation>, DefaultIgnore;
96 InGroup<Documentation>, DefaultIgnore;
[all …]
|
| H A D | AttrDocs.td | 1 //==--- AttrDocs.td - Attribute documentation ----------------------------===//
9 // To test that the documentation builds cleanly, you must run clang-tblgen to
51 def SectionDocs : Documentation {
60 def CodeModelDocs : Documentation {
69 def UsedDocs : Documentation {
90 documentation for further information.
94 def RetainDocs : Documentation {
118 def InitPriorityDocs : Documentation {
148 def InitSegDocs : Documentation {
158 documentation on MSDN for more information.
[all …]
|
| /freebsd/usr.sbin/bsdinstall/scripts/ |
| H A D | docsinstall | 14 # documentation and/or other materials provided with the distribution.
53 msg_bndoc_desc="Bengali Documentation"
55 msg_dadoc_desc="Danish Documentation"
56 msg_dedoc_desc="German Documentation"
57 …documentation set from\nthe $OSNAME Documentation Project: Handbook, FAQ, and articles.\n\nPlease …
58 msg_eldoc_desc="Greek Documentation"
59 msg_endoc_desc="English Documentation (recommended)"
60 msg_esdoc_desc="Spanish Documentation"
61 msg_frdoc_desc="French Documentation"
62 msg_freebsd_documentation_installation="$OSNAME Documentation Installation"
[all …]
|
| /freebsd/crypto/krb5/doc/html/_sources/ |
| H A D | about.rst.txt | 1 Contributing to the MIT Kerberos Documentation
4 We are looking for documentation writers and editors who could contribute
5 towards improving the MIT KC documentation content. If you are an experienced
13 this documentation has a "FEEDBACK" link to the krb5-bugs@mit.edu email
20 Starting with release 1.11, the Kerberos documentation set is
21 unified in a central form. Man pages, HTML documentation, and PDF
23 developer documentation incorporates Doxygen markup from the source
27 Previous versions of Kerberos 5 attempted to maintain separate documentation
29 documentation disjoint from the source code implementing that API
30 resulted in the documentation becoming stale, and over time the documentation
[all …]
|
| H A D | build_this.rst.txt | 1 How to build this documentation from the source
20 documentation without the Doxygen reference by running, from the doc
52 To generate documentation in HTML format, run ``make html`` in the
59 Documentation generated this way will use symbolic names for paths
70 Building for an OS package or site documentation
73 To generate documentation specific to a build of MIT krb5 as you have
80 Documentation generated this way will use concrete paths (like
|
| /freebsd/crypto/krb5/doc/ |
| H A D | about.rst | 1 Contributing to the MIT Kerberos Documentation
4 We are looking for documentation writers and editors who could contribute
5 towards improving the MIT KC documentation content. If you are an experienced
13 this documentation has a "FEEDBACK" link to the krb5-bugs@mit.edu email
20 Starting with release 1.11, the Kerberos documentation set is
21 unified in a central form. Man pages, HTML documentation, and PDF
23 developer documentation incorporates Doxygen markup from the source
27 Previous versions of Kerberos 5 attempted to maintain separate documentation
29 documentation disjoint from the source code implementing that API
30 resulted in the documentation becoming stale, and over time the documentation
[all …]
|
| H A D | notice.rst | 13 documentation and/or other materials provided with the distribution.
40 Documentation components of this software distribution are licensed
118 distribute this software and its documentation for any purpose and
121 this permission notice appear in supporting documentation, and that
149 documentation.
173 documentation and/or other materials provided with the distribution.
197 obtaining a copy of this software and associated documentation files
230 the documentation and/or other materials provided with the
310 copy of this software and associated documentation files (the
330 Kerberos V5 includes documentation and software developed at the
[all …]
|
| H A D | build_this.rst | 1 How to build this documentation from the source
20 documentation without the Doxygen reference by running, from the doc
52 To generate documentation in HTML format, run ``make html`` in the
59 Documentation generated this way will use symbolic names for paths
70 Building for an OS package or site documentation
73 To generate documentation specific to a build of MIT krb5 as you have
80 Documentation generated this way will use concrete paths (like
|
| /freebsd/crypto/krb5/doc/html/ |
| H A D | about.html | 9 <title>Contributing to the MIT Kerberos Documentation — MIT Kerberos Documentation</title>
22 …<link rel="prev" title="How to build this documentation from the source" href="build_this.html" />
28 <h1><a href="index.html">MIT Kerberos Documentation</a></h1>
34 <a href="build_this.html" title="How to build this documentation from the source"
42 …b5-bugs@mit.edu?subject=Documentation__Contributing to the MIT Kerberos Documentation">feedback</a>
55 <section id="contributing-to-the-mit-kerberos-documentation">
56 …ontributing to the MIT Kerberos Documentation<a class="headerlink" href="#contributing-to-the-mit-…
57 <p>We are looking for documentation writers and editors who could contribute
58 towards improving the MIT KC documentation content. If you are an experienced
65 this documentation has a “FEEDBACK” link to the <a class="reference external" href="mailto:krb5-bug…
[all …]
|
| H A D | build_this.html | 9 … <title>How to build this documentation from the source — MIT Kerberos Documentation</title>
21 <link rel="next" title="Contributing to the MIT Kerberos Documentation" href="about.html" />
28 <h1><a href="index.html">MIT Kerberos Documentation</a></h1>
36 <a href="about.html" title="Contributing to the MIT Kerberos Documentation"
42 …<a href="mailto:krb5-bugs@mit.edu?subject=Documentation__How to build this documentation from the …
55 <section id="how-to-build-this-documentation-from-the-source">
56 <h1>How to build this documentation from the source<a class="headerlink" href="#how-to-build-this-d…
71 documentation without the Doxygen reference by running, from the doc
99 <p>To generate documentation in HTML format, run <code class="docutils literal notranslate"><span c…
105 <p>Documentation generated this way will use symbolic names for paths
[all …]
|
| H A D | index.html | 9 <title>MIT Kerberos Documentation (1.21.3) — MIT Kerberos Documentation</title>
27 <h1><a href="#">MIT Kerberos Documentation</a></h1>
39 …<a href="mailto:krb5-bugs@mit.edu?subject=Documentation__MIT Kerberos Documentation (1.21.3)">feed…
52 <section id="mit-kerberos-documentation-release">
53 <h1>MIT Kerberos Documentation (1.21.3)<a class="headerlink" href="#mit-kerberos-documentation-rele…
64 …a class="reference internal" href="build_this.html">How to build this documentation from the sourc…
65 …lass="reference internal" href="about.html">Contributing to the MIT Kerberos Documentation</a></li>
81 <li><a class="reference internal" href="#">MIT Kerberos Documentation (1.21.3)</a></li>
95 …a class="reference internal" href="build_this.html">How to build this documentation from the sourc…
96 …lass="reference internal" href="about.html">Contributing to the MIT Kerberos Documentation</a></li>
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/Tooling/Syntax/ |
| H A D | Nodes.td | 21 let documentation = [{
36 let documentation = [{
47 let documentation = [{
58 let documentation = [{
63 let documentation = [{
75 let documentation = [{
83 let documentation = [{
95 let documentation = [{
106 let documentation = [{
114 let documentation = [{
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mmc/ |
| H A D | sdhci-st.txt | 4 Documentation/devicetree/bindings/mmc/mmc.txt and the properties
14 See: Documentation/devicetree/bindings/resource-names.txt
16 See: Documentation/devicetree/bindings/clock/clock-bindings.txt
23 See: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
36 See: Documentation/devicetree/bindings/mmc/mmc.txt.
39 See: Documentation/devicetree/bindings/mmc/mmc.txt.
43 See: Documentation/devicetree/bindings/mmc/mmc.txt.
46 See: Documentation/devicetree/bindings/reset/reset.txt
52 See: Documentation/devicetree/bindings/mmc/mmc.txt.
55 See: Documentation/devicetree/bindings/mmc/mmc.txt.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | motorola-cpcap.txt | 19 - Documentation/devicetree/bindings/power/supply/cpcap-battery.yaml
20 - Documentation/devicetree/bindings/power/supply/cpcap-charger.yaml
21 - Documentation/devicetree/bindings/regulator/cpcap-regulator.txt
22 - Documentation/devicetree/bindings/phy/phy-cpcap-usb.txt
23 - Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
24 - Documentation/devicetree/bindings/rtc/cpcap-rtc.txt
25 - Documentation/devicetree/bindings/leds/leds-cpcap.txt
26 - Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml
|
| /freebsd/sys/contrib/device-tree/Bindings/ |
| H A D | submitting-patches.rst | 11 Documentation/process/submitting-patches.rst applies.
13 1) The Documentation/ and include/dt-bindings/ portion of the patch should
24 use "Documentation" or "doc" because that is implied. All bindings are
33 See Documentation/devicetree/bindings/writing-schema.rst for more details
46 5) The Documentation/ portion of the patch should come in the series before
51 in Documentation/devicetree/bindings. This rule applies even if
55 ("checkpatch: add DT compatible string documentation checks"). ]
58 driver, the documentation should also include a compatible
85 0) Please see Documentation/devicetree/bindings/ABI.rst for details
|
| /freebsd/sys/contrib/device-tree/Bindings/power/ |
| H A D | wakeup-source.txt | 24 1. "gpio-key,wakeup" Documentation/devicetree/bindings/input/gpio-keys{,-polled}.txt
25 2. "has-tpo" Documentation/devicetree/bindings/rtc/rtc-opal.txt
26 3. "linux,wakeup" Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt
27 Documentation/devicetree/bindings/mfd/tc3589x.txt
28 Documentation/devicetree/bindings/input/touchscreen/ti,ads7843.yaml
29 4. "linux,keypad-wakeup" Documentation/devicetree/bindings/input/qcom,pm8921-keypad.yaml
30 5. "linux,input-wakeup" Documentation/devicetree/bindings/input/samsung,s3c6410-keypad.yaml
31 6. "nvidia,wakeup-source" Documentation/devicetree/bindings/input/nvidia,tegra20-kbc.txt
|
| /freebsd/sys/contrib/device-tree/Bindings/sound/ |
| H A D | adi,adau1977.txt | 4 https://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1977.pdf
5 https://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1978.pdf
6 https://www.analog.com/media/en/technical-documentation/data-sheets/ADAU1979.pdf
17 Documentation/devicetree/bindings/regulator/regulator.txt
21 Documentation/devicetree/bindings/gpio/gpio.txt
24 Documentation/devicetree/bindings/regulator/regulator.txt
33 Documentation/devicetree/bindings/spi/spi-bus.txt
|
| /freebsd/contrib/libcbor/ |
| H A D | Doxyfile | 3 # This file describes the settings to be used by the documentation system
41 # project for which the documentation is generated. This name is used in the
48 # could be handy for archiving the generated documentation or if some version
60 # in the documentation. The maximum height of the logo should not exceed 55
67 # into which the generated documentation will be written. If a relative path is
104 # documentation generated by doxygen is written. Doxygen will use this
120 # documentation (similar to Javadoc). Set to NO to disable this.
153 # inherited members of a class in the documentation of that class as if those
180 # path mentioned in the documentation of a class, which tells the reader which
237 # documentation block
[all...] |
| /freebsd/contrib/bearssl/ |
| H A D | Doxyfile | 3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # in the documentation. The maximum height of the logo should not exceed 55
57 # into which the generated documentation will be written. If a relative path is
82 # documentation generated by doxygen is written. Doxygen will use this
98 # documentation (similar to Javadoc). Set to NO to disable this.
131 # inherited members of a class in the documentation of that class as if those
158 # path mentioned in the documentation of a class, which tells the reader which
203 # documentation from any documented member that it re-implements.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | leds-aat1290.txt | 23 node - see Documentation/devicetree/bindings/leds/common.txt.
26 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
27 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
30 - flash-max-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
35 - function : see Documentation/devicetree/bindings/leds/common.txt
36 - color : see Documentation/devicetree/bindings/leds/common.txt
37 - label : see Documentation/devicetree/bindings/leds/common.txt (deprecated)
|
| /freebsd/sys/contrib/openzfs/contrib/pyzfs/docs/source/ |
| H A D | conf.py | 4 # pyzfs documentation build configuration file, created by
21 # documentation root, use os.path.abspath to make it absolute, like shown here.
26 # If your documentation needs a minimal Sphinx version, state it here.
64 # The language for content autogenerated by Sphinx. Refer to documentation
111 # The theme to use for HTML and HTML Help pages. See the documentation for
117 # documentation.
124 # "<project> v<release> documentation".
146 # directly to the root of the documentation.
227 (master_doc, 'pyzfs.tex', u'pyzfs Documentation',
257 (master_doc, 'pyzfs', u'pyzfs Documentation',
[all …]
|
| /freebsd/contrib/ldns/ |
| H A D | libdns.doxygen.in | 3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # in the documentation. The maximum height of the logo should not exceed 55
57 # into which the generated documentation will be written. If a relative path is
82 # documentation generated by doxygen is written. Doxygen will use this
97 # documentation generated by doxygen is written. Doxygen will use this
106 # documentation (similar to Javadoc). Set to NO to disable this.
139 # inherited members of a class in the documentation of that class as if those
166 # path mentioned in the documentation of a class, which tells the reader which
[all …]
|
| /freebsd/contrib/unbound/doc/ |
| H A D | unbound.doxygen | 3 # This file describes the settings to be used by the documentation system
41 # project for which the documentation is generated. This name is used in the
48 # could be handy for archiving the generated documentation or if some version
60 # in the documentation. The maximum height of the logo should not exceed 55
67 # into which the generated documentation will be written. If a relative path is
104 # documentation generated by doxygen is written. Doxygen will use this
120 # documentation (similar to Javadoc). Set to NO to disable this.
153 # inherited members of a class in the documentation of that class as if those
180 # path mentioned in the documentation of a class, which tells the reader which
237 # documentation blocks is shown as doxygen documentation.
[all …]
|