From: "Theodore Ts'o" <tytso@mit.edu>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
duanj.fnst@cn.fujitsu.com, fabf@skynet.be
Subject: Re: kernel-doc (was Re: + lib-digsigc-kernel-doc-warning-fixes.patch added to -mm tree)
Date: Mon, 26 May 2014 10:02:44 -0400 [thread overview]
Message-ID: <20140526140244.GC22284@thunk.org> (raw)
In-Reply-To: <CACVxJT82k0YO7eo8ECu3Rq__vu8L6TE2rhwVGoGLk_7nj+SYFg@mail.gmail.com>
On Mon, May 26, 2014 at 04:27:04PM +0300, Alexey Dobriyan wrote:
> On Thu, May 22, 2014 at 10:28 PM, <akpm@linux-foundation.org> wrote:
> > * digsig_verify() - digital signature verification with public key
> > * @keyring: keyring to search key in
> > * @sig: digital signature
> > - * @sigen: length of the signature
> > + * @siglen: length of the signature
> > * @data: data
> > * @datalen: length of the data
>
> Does anyone use kernel-doc generated documentation?
> I'm serious.
The kernel-doc generated documentation is available on the web, and I
suspect a number of people find it when they run Google Searches.
The danger of course is that they might get documentation which is out
of sync with the upstream kernel (or whatever kernel they are
developing against), but I know I've found it useful on occasion.
- Ted
next prev parent reply other threads:[~2014-05-26 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 13:27 kernel-doc (was Re: + lib-digsigc-kernel-doc-warning-fixes.patch added to -mm tree) Alexey Dobriyan
2014-05-26 14:02 ` Theodore Ts'o [this message]
2014-05-27 8:54 ` Alexey Dobriyan
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=20140526140244.GC22284@thunk.org \
--to=tytso@mit.edu \
--cc=adobriyan@gmail.com \
--cc=duanj.fnst@cn.fujitsu.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.