Searched refs:comments (Results 1 – 25 of 158) sorted by relevance
1234567
| /Linux-v6.6/Documentation/rust/ |
| D | coding-guidelines.rst | 18 .. note:: Conventions on comments and documentation are not checked by
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
70 the line of documentation to be commented. For any other case, comments are
[all …]
|
| /Linux-v6.6/Documentation/doc-guide/ |
| 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 …]
|
| 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
|
| /Linux-v6.6/scripts/ |
| D | get_feat.pl | 114 my $comments = "";
158 $comments .= "$1\n";
202 $data{$name}->{comments} = $comments;
313 my $com = $data{$feat}->{comments};
|
| /Linux-v6.6/Documentation/devicetree/bindings/ |
| D | .yamllint | 26 comments:
29 comments-indentation: disable
|
| /Linux-v6.6/Documentation/translations/zh_CN/doc-guide/ |
| D | contributing.rst | 70 [PATCH] PM / devfreq: Fix two malformed kerneldoc comments
72 Two kerneldoc comments in devfreq.c fail to adhere to the required format,
|
| /Linux-v6.6/Documentation/process/ |
| 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::
516 Instead, comments should explain the non-obvious details and document
533 Function documentation comments:
536 and not free form comments::
[all …]
|
| D | 6.Followthrough.rst | 25 A patch of any significance will result in a number of comments from other
61 What all of this comes down to is that, when reviewers send you comments,
64 from happening. When you get review comments on a patch, take the time to
85 One fatal mistake is to ignore review comments in the hope that they will
87 responded to the comments you got the time before, you're likely to find
131 there's a good chance that you will get more comments from a new set of
132 reviewers; these comments need to be answered as in the previous round.
152 may be a new round of comments from developers who had not been aware of
|
| D | code-of-conduct.rst | 33 * Trolling, insulting/derogatory comments, and personal or political attacks
49 comments, commits, code, wiki edits, issues, and other contributions that are
|
| D | submitting-patches.rst | 312 Respond to review comments
315 Your patch will almost certainly get comments from reviewers on ways in
317 respond to those comments; ignoring reviewers is a good way to get ignored in
318 return. You can simply reply to their emails to answer their comments. Review
319 comments or questions that do not lead to a code change should almost certainly
369 receive comments within a week or so; if that does not happen, make sure
483 provided such comments, you may optionally add a ``Cc:`` tag to the patch.
556 with the submitter's response to my comments.
632 - Any additional comments not suitable for the changelog.
671 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
[all …]
|
| D | maintainer-kvm-x86.rst | 118 Except for a handful of special snowflakes, do not use kernel-doc comments for
125 Write comments using imperative mood and avoid pronouns. Use comments to
128 speak for itself. If the code itself is inscrutable, comments will not help.
138 not in comments. Instead, if necessary (see below), copy-paste the relevant
143 APM in comments. With few exceptions, KVM *must* honor architectural behavior,
253 modify comments. When possible and relevant, testing on both Intel and AMD is
|
| /Linux-v6.6/rust/ |
| D | bindgen_parameters | 22 --no-doc-comments
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | target.rst | 13 This section is blank because no kerneldoc comments have been added to
|
| /Linux-v6.6/tools/bpf/bpftool/Documentation/ |
| D | Makefile | 27 RST2MAN_OPTS += --verbose --strip-comments
|
| /Linux-v6.6/Documentation/translations/ko_KR/ |
| D | stable_api_nonsense.txt | 10 a fork. So if you have any comments or updates for this file please
|
| /Linux-v6.6/Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 148 The libbpf API is documented via comments above definitions in
149 header files. These comments can be rendered by doxygen and sphinx
151 convention in which these comments should be formatted.
|
| /Linux-v6.6/Documentation/gpu/ |
| D | introduction.rst | 59 concepts. Documentation should be put into the code itself as kerneldoc comments
64 have formal kerneldoc comments. Use normal C comments if you feel like a comment
67 anything entirely private with ``/* private: */`` comments as per the
|
| /Linux-v6.6/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-h6-orangepi-lite2.dts | 53 * See the comments for CLDO2.
|
| /Linux-v6.6/Documentation/translations/ja_JP/ |
| D | stable_api_nonsense.txt | 11 fork. So if you have any comments or updates of this file, please try
|
| D | SubmitChecklist | 11 fork. So if you have any comments or updates of this file, please try
|
| /Linux-v6.6/arch/arm/nwfpe/ |
| D | fpa11.inl | 5 Direct questions, comments to Scott Bambrough <scottb@netwinder.org>
|
| /Linux-v6.6/Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 33 fs/nfsd/nfsctl.c; most of them have detailed comments.
|
| /Linux-v6.6/Documentation/fb/ |
| D | cirrusfb.rst | 58 * Code cleanup, add comments.
|
| /Linux-v6.6/Documentation/filesystems/ext4/ |
| D | about.rst | 14 e2fsprogs-1.44. All comments and corrections are welcome, since there is
|
| /Linux-v6.6/drivers/staging/qlge/ |
| D | TODO | 29 * remove duplicate and useless comments
|
1234567
