| /linux-3.4.99/scripts/rt-tester/ |
| D | rt-tester.py | 20 comments = 0 variable
111 comments = 1 variable
150 if comments > 1:
154 if comments == 1:
155 comments = 2 variable
|
| /linux-3.4.99/Documentation/ |
| D | kernel-doc-nano-HOWTO.txt | 4 How to format kernel-doc comments
24 kernel-doc comments in Linux kernel source.
39 documented using kernel-doc formatted comments.
41 The opening comment mark "/**" is reserved for kernel-doc comments.
42 Only comments so marked will be considered by the kernel-doc scripts,
45 kernel-doc formatted comments. The closing comment marker for
46 kernel-doc comments can be either "*/" or "**/", but "*/" is
49 Kernel-doc comments should be placed just before the function
93 The kernel-doc function comments describe each parameter to the
96 The kernel-doc data structure comments describe each structure member
[all …]
|
| D | CodingStyle | 69 Outside of comments, documentation and except in Kconfig, spaces are never
155 comments on.
430 Generally, you want your comments to tell WHAT your code does, not HOW.
431 Also, try to avoid putting comments inside a function body: if the
434 small comments to note or warn about something particularly clever (or
435 ugly), but try to avoid excess. Instead, put the comments at the head
443 Linux style for comments is the C89 "/* ... */" style.
444 Don't use C99-style "// ..." comments.
446 The preferred style for long (multi-line) comments is:
450 * comments in the Linux kernel source code.
|
| D | SubmittingPatches | 284 When in doubt, solicit comments on linux-kernel mailing list.
417 provided such comments, you may optionally add a "Cc:" tag to the patch.
450 with the submitter's response to my comments.
492 - Any additional comments not suitable for the changelog.
531 comments (i.e., "v1, v2, v3"), or "RFC" to indicate a request for
532 comments. If there are four patches in a patch series the individual
568 One good use for the additional comments after the "---" marker is for
571 on bigger patches. Other comments relevant only to the moment or the
573 here. A good example of such comments might be "patch changelogs"
|
| /linux-3.4.99/fs/befs/ |
| D | TODO | 4 * Convert comments to the Kernel-Doc format.
|
| /linux-3.4.99/Documentation/arm/SA1100/ |
| D | Victor | 14 For any comments, please feel free to contact me through the above
|
| /linux-3.4.99/Documentation/development-process/ |
| D | 6.Followthrough | 21 A patch of any significance will result in a number of comments from other
50 What all of this comes down to is that, when reviewers send you comments,
53 from happening. When you get review comments on a patch, take the time to
74 One fatal mistake is to ignore review comments in the hope that they will
76 responded to the comments you got the time before, you're likely to find
119 there's a good chance that you will get more comments from a new set of
120 reviewers; these comments need to be answered as in the previous round.
140 may be a new round of comments from developers who had not been aware of
|
| D | 4.Coding | 341 specially-formatted comments; these comments can be extracted and formatted
343 a subsystem which has kerneldoc comments, you should maintain them and add
346 comments for the future; indeed, this can be a useful activity for
347 beginning kernel developers. The format of these comments, along with some
352 note that, often, comments are most notable by their absence. Once again,
356 comments explaining the more subtle aspects.
|
| /linux-3.4.99/Documentation/ko_KR/ |
| D | stable_api_nonsense.txt | 10 a fork. So if you have any comments or updates for this file please
|
| /linux-3.4.99/Documentation/powerpc/ |
| D | zImage_layout.txt | 5 comments or corrections.
|
| /linux-3.4.99/Documentation/serial/ |
| D | riscom8.txt | 26 comments and try to change some of them in case of problems.
|
| /linux-3.4.99/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-3.4.99/Documentation/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-3.4.99/Documentation/fb/ |
| D | cirrusfb.txt | 59 * Code cleanup, add comments.
|
| /linux-3.4.99/drivers/staging/iio/Documentation/ |
| D | ring.txt | 6 comments in the source code. Note that some drivers allow buffer
|
| /linux-3.4.99/arch/arm/mach-footbridge/ |
| D | Kconfig | 36 If you have any questions or comments about the Compaq Personal
|
| /linux-3.4.99/Documentation/netlabel/ |
| D | introduction.txt | 33 names can be found in the 'net/netlabel/' directory as comments in the
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | jfs.txt | 38 Please send bugs, comments, cards and letters to shaggy@linux.vnet.ibm.com.
|
| /linux-3.4.99/drivers/staging/iio/ |
| D | TODO | 7 Major changes not expected except in response to comments
|
| /linux-3.4.99/Documentation/arm/ |
| D | IXP2000 | 62 The following people have contributed patches/comments/etc:
|
| /linux-3.4.99/Documentation/watchdog/ |
| D | pcwd-watchdog.txt | 43 WDIOF_* bitwise-anded into the value. (The comments
|
| /linux-3.4.99/Documentation/input/ |
| D | cs461x.txt | 33 comments about them; but I've found the joystick can be initialized
|
| /linux-3.4.99/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.
|