Searched refs:comments (Results 1 – 25 of 131) sorted by relevance
123456
| /Linux-v4.19/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 | sphinx.rst | 13 documentation comments, or kernel-doc comments, from source files. Usually these
15 kernel-doc comments have some special structure and formatting, but beyond that
288 the list of the cells in this *table-row*. Exceptions are *comments* ( ``..`` )
|
| /Linux-v4.19/drivers/staging/dgnc/ |
| D | TODO | 1 * remove unnecessary comments
|
| /Linux-v4.19/drivers/staging/netlogic/ |
| D | TODO | 3 * Changing comments in to linux standred format
|
| /Linux-v4.19/fs/befs/ |
| D | TODO | 4 * Convert comments to the Kernel-Doc format.
|
| /Linux-v4.19/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 | 376 8) Respond to review comments
379 Your patch will almost certainly get comments from reviewers on ways in
380 which the patch can be improved. You must respond to those comments;
381 ignoring reviewers is a good way to get ignored in return. Review comments
400 receive comments within a week or so; if that does not happen, make sure
540 provided such comments, you may optionally add a ``Cc:`` tag to the patch.
579 with the submitter's response to my comments.
643 - Any additional comments not suitable for the changelog.
682 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
683 comments. If there are four patches in a patch series the individual
[all …]
|
| D | 4.Coding.rst | 363 specially-formatted comments; these comments can be extracted and formatted
365 a subsystem which has kerneldoc comments, you should maintain them and add
368 comments for the future; indeed, this can be a useful activity for
369 beginning kernel developers. The format of these comments, along with some
374 note that, often, comments are most notable by their absence. Once again,
378 comments explaining the more subtle aspects.
|
| /Linux-v4.19/drivers/staging/rtlwifi/ |
| D | TODO | 8 - address any reviewers comments
|
| /Linux-v4.19/Documentation/translations/it_IT/ |
| D | disclaimer-ita.rst | 12 speakers and is not intended as a fork. So, if you have any comments or
|
| /Linux-v4.19/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-v4.19/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-v4.19/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-v4.19/Documentation/fb/ |
| D | cirrusfb.txt | 59 * Code cleanup, add comments.
|
| /Linux-v4.19/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 34 fs/nfsd/nfsctl.c; most of them have detailed comments.
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| D | about.rst | 14 e2fsprogs-1.44. All comments and corrections are welcome, since there is
|
| /Linux-v4.19/Documentation/netlabel/ |
| D | introduction.txt | 33 names can be found in the 'net/netlabel/' directory as comments in the
|
| /Linux-v4.19/drivers/staging/iio/Documentation/ |
| D | ring.txt | 6 comments in the source code. Note that some drivers allow buffer
|
| /Linux-v4.19/Documentation/input/devices/ |
| D | cs461x.rst | 31 comments about them; but I've found the joystick can be initialized
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-g-jpegcomp.rst | 48 information for in an AVI or so). COM is the same, but it's comments,
|
| /Linux-v4.19/arch/arm/mach-footbridge/ |
| D | Kconfig | 36 If you have any questions or comments about the Compaq Personal
|
| /Linux-v4.19/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 128 * Added structure offset comments.
270 * Added structure offset comments.
536 * 03-27-01 01.01.04 Added structure offset comments.
587 * 03-27-01 01.01.04 Added structure offset comments.
637 * Added structure offset comments.
662 * 03-27-01 01.01.03 Added structure offset comments.
670 * 03-27-01 01.01.02 Added structure offset comments.
|
123456
