mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Paul Drynoff" <pauldrynoff@gmail.com>
Cc: "Linus Torvalds" <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmalloc man page before 2.6.17
Date: Fri, 26 May 2006 10:17:11 +0300	[thread overview]
Message-ID: <84144f020605260017i4682c409vc4a004d016c31270@mail.gmail.com> (raw)
In-Reply-To: <36e6b2150605260007h1601aa04v31c6c698c6e4d1b9@mail.gmail.com>

Hi Paul,

On 5/26/06, Paul Drynoff <pauldrynoff@gmail.com> wrote:
> Currently I with my colleague dispute about quality of code
> Linux vs other. And he fairly point me that linux kernel even
> have no manual entry for "kmalloc".
>
> So please consider include this or similar patch before 2.6.17.
> With this patch
> scripts/kernel-doc -man -function kmalloc mm/slob.c  | nroff -man | less
> create man page for "kmalloc"

Duplicating the comment in mm/slob.c seems pointless. I think we could
move the comment to include/linux/slab.h from mm/slab.c assuming the
kerneldoc script picks it up from there.

                                                   Pekka

  reply	other threads:[~2006-05-26  7:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26  7:07 Paul Drynoff
2006-05-26  7:17 ` Pekka Enberg [this message]
2006-05-26  7:58   ` Paul Drynoff
2006-05-26  8:03     ` Pekka J Enberg
2006-05-26  8:20       ` Paul Drynoff
2006-05-26  9:42         ` Andrey Panin
2006-05-26  9:48         ` Jesper Juhl
2006-05-26 10:44           ` Paul Drynoff
2006-05-26 13:23             ` Paulo Marques
2006-05-26 14:17             ` Christoph Lameter
2006-05-26 14:55               ` Paul Drynoff
2006-05-26 15:03                 ` Christoph Lameter
2006-05-26 19:55             ` Luca
2006-05-27 10:28             ` Martin Waitz
2006-05-26 10:47           ` Paul Drynoff

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=84144f020605260017i4682c409vc4a004d016c31270@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pauldrynoff@gmail.com \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®