The patch titled Subject: CodingStyle: add networking specific block comment style has been removed from the -mm tree. Its filename was codingstyle-add-networking-specific-block-comment-style.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Joe Perches <joe@xxxxxxxxxxx> Subject: CodingStyle: add networking specific block comment style The block comment style in net/ and drivers/net is non-standard. Document it. Signed-off-by: Joe Perches <joe@xxxxxxxxxxx> Cc: "Allan, Bruce W" <bruce.w.allan@xxxxxxxxx> Cc: Andy Whitcroft <apw@xxxxxxxxxxxxx> Cc: David Miller <davem@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/CodingStyle | 10 ++++++++++ 1 file changed, 10 insertions(+) diff -puN Documentation/CodingStyle~codingstyle-add-networking-specific-block-comment-style Documentation/CodingStyle --- a/Documentation/CodingStyle~codingstyle-add-networking-specific-block-comment-style +++ a/Documentation/CodingStyle @@ -454,6 +454,16 @@ The preferred style for long (multi-line * with beginning and ending almost-blank lines. */ +For files in net/ and drivers/net/ the preferred style for long (multi-line) +comments is a little different. + + /* The preferred comment style for files in net/ and drivers/net + * looks like this. + * + * It is nearly the same as the generally preferred comment style, + * but there is no initial almost-blank line. + */ + It's also important to comment data, whether they are basic types or derived types. To this end, use just one data declaration per line (no commas for multiple data declarations). This leaves you room for a small comment on each _ Patches currently in -mm which might be from joe@xxxxxxxxxxx are origin.patch linux-next.patch kstrto-add-documentation.patch simple_strto-annotate-function-as-obsolete.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html