From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org
Subject: [PATCH v2] docbook: fix vmalloc missing parameter notation (fwd)
Date: Tue, 29 Apr 2008 20:24:13 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804292023030.18219@shark.he.net> (raw)
OK, so either pine or the linux-mm mailing list software likes to
take the first line of body text if it begins with "From:"
and add that to the mail headers. I don't recall seeing this
problem before...
--
~Randy
---------- Forwarded message ----------
Date: Tue, 29 Apr 2008 20:18:12 -0700 (PDT)
From: Randy.Dunlap <rdunlap@xenotime.net>,
Randy Dunlap <randy.dunlap@oracle.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org
Subject: [PATCH v2] docbook: fix vmalloc missing parameter notation
Fix vmalloc kernel-doc warning:
Warning(linux-2.6.25-git14//mm/vmalloc.c:555): No description found for parameter 'caller'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
mm/vmalloc.c | 1 +
1 file changed, 1 insertion(+)
--- linux-2.6.25-git14.orig/mm/vmalloc.c
+++ linux-2.6.25-git14/mm/vmalloc.c
@@ -545,6 +545,7 @@ void *__vmalloc_area(struct vm_struct *a
* @gfp_mask: flags for the page level allocator
* @prot: protection mask for the allocated pages
* @node: node to use for allocation or -1
+ * @caller: caller's return address
*
* Allocate enough pages to cover @size from the page level
* allocator with @gfp_mask flags. Map them into contiguous
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2008-04-30 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0804292023030.18219@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox