From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] kernel-doc: drop __must_check and various "inline" qualifiers
Date: Mon, 9 Oct 2006 15:00:18 +0200 [thread overview]
Message-ID: <200610091500.24131.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20061008200851.47eb99da.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Drop __inline, __always_inline, noinline, and __must_check in the
> produced kernel-doc output, similar to other pseudo directives.
The inline status of a function is not of much help for a developer, that's
right. But I would like to see the the __must_check in the documentation.
This it what makes a difference, the inline stuff is extraneous.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-09 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 3:08 [PATCH] kernel-doc: drop __must_check and various "inline" qualifiers Randy Dunlap
2006-10-09 13:00 ` Rolf Eike Beer [this message]
2006-10-09 15:15 ` [PATCH v2] kernel-doc: drop " Randy Dunlap
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=200610091500.24131.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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