Searched refs:comments (Results 1 – 25 of 144) sorted by relevance
123456
| /Linux-v5.10/Documentation/doc-guide/ |
| D | kernel-doc.rst | 1 Writing kernel-doc comments
5 comments in the kernel-doc format to describe the functions, types
12 comments. Please stick to the style described here.
14 The kernel-doc structure is extracted from the comments, and proper
24 to be used by modules should also have kernel-doc comments.
33 How to format kernel-doc comments
36 The opening comment mark ``/**`` is used for kernel-doc comments. The
37 ``kernel-doc`` tool will extract comments marked this way. The rest of
41 The function and type kernel-doc comments should be placed just before
44 overview kernel-doc comments may be placed anywhere at the top indentation
[all …]
|
| D | contributing.rst | 50 problems in kerneldoc comments in C code. While the documentation
66 comments that look like this::
85 [PATCH] PM / devfreq: Fix two malformed kerneldoc comments
87 Two kerneldoc comments in devfreq.c fail to adhere to the required format,
140 Languishing kerneldoc comments
143 Developers are encouraged to write kerneldoc comments for their code, but
144 many of those comments are never pulled into the docs build. That makes
147 the documentation to bring those comments in can help the community derive
151 overlooked comments.
155 kerneldoc comments for internal use; those should not be pulled into the
|
| D | maintainer-profile.rst | 16 found in the source as kerneldoc comments; those are usually (but not
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | .yamllint | 21 comments:
24 comments-indentation: disable
|
| /Linux-v5.10/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-v5.10/drivers/staging/netlogic/ |
| D | TODO | 3 * Changing comments into linux standard format
|
| /Linux-v5.10/fs/befs/ |
| D | TODO | 4 * Convert comments to the Kernel-Doc format.
|
| /Linux-v5.10/Documentation/process/ |
| D | 6.Followthrough.rst | 25 A patch of any significance will result in a number of comments from other
54 What all of this comes down to is that, when reviewers send you comments,
57 from happening. When you get review comments on a patch, take the time to
78 One fatal mistake is to ignore review comments in the hope that they will
80 responded to the comments you got the time before, you're likely to find
124 there's a good chance that you will get more comments from a new set of
125 reviewers; these comments need to be answered as in the previous round.
145 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 | 316 Respond to review comments
319 Your patch will almost certainly get comments from reviewers on ways in
321 respond to those comments; ignoring reviewers is a good way to get ignored in
322 return. You can simply reply to their emails to answer their comments. Review
323 comments or questions that do not lead to a code change should almost certainly
344 receive comments within a week or so; if that does not happen, make sure
440 provided such comments, you may optionally add a ``Cc:`` tag to the patch.
509 with the submitter's response to my comments.
580 - Any additional comments not suitable for the changelog.
619 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
[all …]
|
| D | 4.Coding.rst | 364 specially-formatted comments; these comments can be extracted and formatted
366 a subsystem which has kerneldoc comments, you should maintain them and add
369 comments for the future; indeed, this can be a useful activity for
370 beginning kernel developers. The format of these comments, along with some
375 note that, often, comments are most notable by their absence. Once again,
379 comments explaining the more subtle aspects.
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | target.rst | 13 This section is blank because no kerneldoc comments have been added to
|
| /Linux-v5.10/arch/mips/vdso/ |
| D | Kconfig | 8 # the comments on that file.
|
| /Linux-v5.10/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-v5.10/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-h6-orangepi-lite2.dts | 53 * See the comments for CLDO2.
|
| /Linux-v5.10/arch/arm/nwfpe/ |
| D | fpa11.inl | 5 Direct questions, comments to Scott Bambrough <scottb@netwinder.org>
|
| D | fpmodule.inl | 5 Direct questions, comments to Scott Bambrough <scottb@netwinder.org>
|
| /Linux-v5.10/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-v5.10/Documentation/fb/ |
| D | cirrusfb.rst | 58 * Code cleanup, add comments.
|
| /Linux-v5.10/Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 33 fs/nfsd/nfsctl.c; most of them have detailed comments.
|
| /Linux-v5.10/Documentation/filesystems/ext4/ |
| D | about.rst | 14 e2fsprogs-1.44. All comments and corrections are welcome, since there is
|
| /Linux-v5.10/Documentation/netlabel/ |
| D | introduction.rst | 38 names can be found in the 'net/netlabel/' directory as comments in the
|
| /Linux-v5.10/arch/arm/mach-footbridge/ |
| D | Kconfig | 37 If you have any questions or comments about the Compaq Personal
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-jpegcomp.rst | 48 information for in an AVI or so). COM is the same, but it's comments,
|
123456
