| /openbmc/phosphor-power/phosphor-regulators/config_files/ |
| H A D | Rainier.json | 2 "comments": [ array
8 "comments": ["Rule to set PMBus PAGE to 0"], array
16 "comments": ["Rule to set PMBus PAGE to 1"], array
24 "comments": ["Rule to set output voltage of a PMBus regulator"], array
28 "comments": [ array
42 "comments": [ array
53 "comments": [ array
64 "comments": [ array
71 "comments": [ array
79 "comments": [ array
[all …]
|
| H A D | BlueRidge.json | 2 "comments": [ array
8 "comments": ["Rule to set PMBus PAGE to 0"], array
16 "comments": ["Rule to set PMBus PAGE to 1"], array
24 "comments": ["Rule to set output voltage of a PMBus regulator"], array
28 "comments": [ array
42 "comments": [ array
53 "comments": [ array
64 "comments": [ array
71 "comments": [ array
79 "comments": [ array
[all …]
|
| H A D | Bonnell.json | 2 "comments": [ array
8 "comments": ["Rule to set PMBus PAGE to 0"], array
16 "comments": ["Rule to set PMBus PAGE to 1"], array
24 "comments": ["Rule to set output voltage of a PMBus regulator"], array
28 "comments": [ array
42 "comments": [ array
53 "comments": [ array
64 "comments": [ array
71 "comments": [ array
79 "comments": [ array
[all …]
|
| H A D | Everest.json | 2 "comments": [ array
8 "comments": ["Rule to set PMBus PAGE to 0"], array
16 "comments": ["Rule to set PMBus PAGE to 1"], array
24 "comments": ["Rule to set output voltage of a PMBus regulator"], array
28 "comments": [ array
42 "comments": [ array
53 "comments": [ array
64 "comments": [ array
71 "comments": [ array
79 "comments": [ array
[all …]
|
| H A D | Fuji.json | 2 "comments": ["phosphor-regulators configuration file for IBM Fuji systems"], array
6 "comments": ["Rule to set PMBus PAGE to 0"], array
14 "comments": ["Rule to set PMBus PAGE to 1"], array
22 "comments": ["Rule to set output voltage of a PMBus regulator"], array
26 "comments": [ array
40 "comments": [ array
51 "comments": [ array
62 "comments": [ array
69 "comments": [ array
77 "comments": [ array
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/examples/ |
| H A D | config.json | 2 "comments": ["Config file for a FooBar one-chassis system"], array
6 "comments": ["Sets output voltage for a PMBus regulator rail"], array
18 "comments": ["Reads sensors from a PMBus regulator rail"], array
22 "comments": ["Read output voltage from READ_VOUT."], array
31 "comments": ["Read output current from READ_IOUT."], array
40 "comments": ["Read temperature from READ_TEMPERATURE_1."], array
53 "comments": ["Chassis number 1 containing CPUs and memory"], array
58 "comments": ["IR35221 regulator producing the Vdd rail"], array
68 "comments": ["Vdd rail"], array
82 "comments": ["IR35221 regulator producing the Vio rail"], array
[all …]
|
| /openbmc/entity-manager/scripts/ |
| H A D | autojson.py | 11 # Trying to parse JSON comments and then being able to re-insert them into
15 # - Single-line style comments (//) can be on a new line or at the end of
18 # - Multi-line style comments (/* */) use the must be free-standing.
20 # - Comments will get inserted back into the file in the line they came
24 # - No attempts to re-indent multi-line comments will be made.
27 # prettier before using this script and planning to move multi-line comments
38 self.comments: List[Tuple[bool, int, str]] = []
40 # Extract out the comments from a JSON-like string and save them away.
52 self.comments.append((do_append, idx, single.group(0)))
69 self.comments.append(
[all …]
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 18 .. note:: Conventions on comments and documentation are not checked by
42 Comments chapter
45 "Normal" comments (i.e. ``//``, rather than code documentation which starts
47 comments are, even though they will not be rendered. This improves consistency,
49 comments more easily. For instance:
56 Furthermore, just like documentation, comments are capitalized at the beginning
58 includes ``// SAFETY:``, ``// TODO:`` and other "tagged" comments, e.g.:
64 Comments should not be used for documentation purposes: comments are intended
67 sometimes it is useful to use both comments and documentation at the same time.
69 For the latter case, comments can be inserted in the middle; that is, closer to
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/schema/ |
| H A D | config_schema.json | 8 "comments": { "$ref": "#/definitions/comments" }, object
18 "comments": { "$ref": "#/definitions/comments" }, object
32 "comments": { object
46 "comments": { "$ref": "#/definitions/comments" }, object
336 "comments": { "$ref": "#/definitions/comments" }, object
359 "comments": { "$ref": "#/definitions/comments" }, object
421 "comments": { "$ref": "#/definitions/comments" }, object
432 "comments": { "$ref": "#/definitions/comments" }, object
444 "comments": { "$ref": "#/definitions/comments" }, object
456 "comments": { "$ref": "#/definitions/comments" }, object
[all …]
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A D | kernel-doc.rst | 1 .. title:: Kernel-doc comments
4 Writing kernel-doc comments
8 comments in the kernel-doc format to describe the functions, types
15 comments. Please stick to the style described here.
20 The kernel-doc structure is extracted from the comments, and proper
30 to be used by modules should also have kernel-doc comments.
39 How to format kernel-doc comments
42 The opening comment mark ``/**`` is used for kernel-doc comments. The
43 ``kernel-doc`` tool will extract comments marked this way. The rest of
47 The function and type kernel-doc comments should be placed just before
[all …]
|
| H A D | contributing.rst | 50 problems in kerneldoc comments in C code. While the documentation
66 comments that look like this::
86 [PATCH] PM / devfreq: Fix two malformed kerneldoc comments
88 Two kerneldoc comments in devfreq.c fail to adhere to the required format,
141 Languishing kerneldoc comments
144 Developers are encouraged to write kerneldoc comments for their code, but
145 many of those comments are never pulled into the docs build. That makes
148 the documentation to bring those comments in can help the community derive
152 overlooked comments.
156 kerneldoc comments for internal use; those should not be pulled into the
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | include-repetition.out | 12 include comments.json
14 include comments.json
15 module comments.json
21 include comments.json
22 include comments.json
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | README.md | 146 ### Comments subsection
148 The JSON data format does not support comments. However, an optional `comments`
150 configuration. It is suggested that the value of this `comments` attribute be an
151 array of strings for comments containing line breaks. All `comments` objects are
154 **_Note: Only 1 `comments` object can exist at any given 'layer' of the
162 "comments": [
170 "comments": "Use GPIO for presence detection",
177 "comments": "Also use the tach for presence detection",
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | README.md | 168 ### Comments subsection
170 The JSON data format does not support comments. However, an optional `comments`
172 configuration. It is suggested that the value of this `comments` attribute be an
173 array of strings for comments containing line breaks. All `comments` objects are
176 **_Note: Only 1 `comments` object can exist at any given 'layer' of the
183 "comments": [
190 "comments": "Monitor this fan",
199 "comments": "Only trust these fan sensors when all are not zero",
207 "comments": "Log errors and power off the system",
|
| /openbmc/qemu/qga/ |
| H A D | commands-posix-ssh.c | 247 .value = (char *)"algo key2 comments"
251 .value = (char *)"algo key1 comments",
331 test_authorized_keys_equal("algo key2 comments"); in test_add_keys()
340 test_authorized_keys_equal("algo key2 comments\n" in test_add_keys()
341 "algo key1 comments"); in test_add_keys()
356 test_authorized_keys_equal("algo key1 comments\n" in test_add_reset_keys()
357 "algo key2 comments"); in test_add_reset_keys()
365 test_authorized_keys_equal("algo key2 comments"); in test_add_reset_keys()
382 "algo key1 comments\n" in test_remove_keys()
384 "algo key1 comments\n" in test_remove_keys()
[all …]
|
| /openbmc/linux/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/ |
| H A D | pwrseq.h | 43 /* comments here */ \
69 /* comments here */ \
86 /* comments here */ \
107 /* comments here */ \
121 /* comments here */ \
148 /* comments here */ \
168 /* comments here */ \
179 /* comments here */ \
187 /* comments here */ \
231 /* comments here */ \
[all …]
|
| /openbmc/openbmc/meta-asrock/meta-romed8hm3/recipes-phosphor/power/phosphor-power/ |
| H A D | config.json | 2 "comments": [ "Config file for ASRock Rack ROMED8HM3" ], array
5 "comments": [ "Chassis number 1 containing CPUs and memory" ], array
10 "comments": [ "ISL96147 regulator producing the VDDCR_CPU rail" ], array
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | validate-regulators-config_tests.cpp | 44 "comments": [ "Config file for a FooBar one-chassis system" ],
48 "comments": [ "Sets output voltage for a PMBus regulator rail" ],
59 "comments": [ "Reads sensors from a PMBus regulator rail" ],
63 "comments": [ "Read output voltage from READ_VOUT." ],
73 "comments": [ "Detects presence of regulators associated with CPU3" ],
85 "comments": [ "Detects and logs redundant phase faults" ],
104 "comments": [ "Chassis number 1 containing CPUs and memory" ],
109 "comments": [ "IR35221 regulator producing the Vdd rail" ],
119 "comments": [ "Vdd rail" ],
266 // Valid: Comments property not specified in TEST()
[all …]
|
| /openbmc/phosphor-fan-presence/monitor/example/ |
| H A D | config.json | 2 "comments": "List of fans with the attributes used to monitor them.", string
5 "comments": [ array
43 "comments": [ array
91 "comments": [ array
131 "comments": [ array
156 "comments": [ array
|
| /openbmc/openbmc-test-automation/tools/ |
| H A D | robot_custom_rules.py | 17 table section if it is a section of comments.
18 e.g "*** Comments ***"
30 r" )?keywords?|variables?|comments?)$",
|
| /openbmc/openbmc-tools/tof-voters/libvoters/subcmd/ |
| H A D | analyze-reviews.py | 70 if "comments" not in patch_set:
73 for comment in patch_set["comments"]:
104 user["comments"] += 1
108 if review["comments"] < 3:
110 print(" ", user, review["comments"])
|
| /openbmc/phosphor-fan-presence/presence/example/ |
| H A D | config.json | 3 "comments": [ array
24 "comments": [ array
42 "comments": [ array
71 "comments": [ array
|
| /openbmc/openbmc/poky/meta/recipes-devtools/flex/flex/ |
| H A D | check-funcs.patch | 1 Subject: build: Move dnl comments out of AC_CHECK_FUNCS
3 Due to a bug, autoheader (2.69) will treat M4 dnl comments in a quoted
15 As a workaround, let's move comments out of AC_CHECK_FUNCS.
49 +dnl Autoheader (<= 2.69) bug: "dnl" comments in a quoted argument of
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-tip.rst | 466 Sentences in comments start with an uppercase letter.
468 Single line comments::
472 Multi-line comments::
478 * Larger multi-line comments should be split into paragraphs.
481 No tail comments:
483 Please refrain from using tail comments. Tail comments disturb the
491 Use freestanding comments instead::
504 Comments should be added where the operation is not obvious. Documenting
516 Instead, comments should explain the non-obvious details and document
533 Function documentation comments:
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | config_file_parser.cpp | 60 // Optional comments property; value not stored in parseAction()
61 if (element.contains("comments")) in parseAction()
201 // Optional comments property; value not stored in parseChassis()
202 if (element.contains("comments")) in parseChassis()
316 // Optional comments property; value not stored in parseConfiguration()
317 if (element.contains("comments")) in parseConfiguration()
347 // Optional comments property; value not stored in parseDevice()
348 if (element.contains("comments")) in parseDevice()
784 // Optional comments property; value not stored in parsePhaseFaultDetection()
785 if (element.contains("comments")) in parsePhaseFaultDetection()
[all …]
|