linux-kernel - Re: kernel-doc (was Re: + lib-digsigc-kernel-doc-warning-fixes.patch added to -mm tree)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACVxJT-jG6fmtBk39+KgroGx90QBxnYvzezcByRpmVW=G-gVoA@mail.gmail.com>
Date:	Tue, 27 May 2014 11:54:42 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	duanj.fnst@...fujitsu.com, fabf@...net.be
Subject: Re: kernel-doc (was Re: + lib-digsigc-kernel-doc-warning-fixes.patch
 added to -mm tree)

On Mon, May 26, 2014 at 5:02 PM, Theodore Ts'o <tytso@....edu> wrote:
> On Mon, May 26, 2014 at 04:27:04PM +0300, Alexey Dobriyan wrote:
>> On Thu, May 22, 2014 at 10:28 PM,  <akpm@...ux-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.

Yeah, they are outdated like those sites hyperlinking old kernels,
polluting google searches.

The thing is largely redundant.

Just opened random file, random comment:

/**
 * finish_open - finish opening a file
 * @file: file pointer                   <====
 * @dentry: pointer to dentry      <====
 * @open: open callback
 * @opened: state of open
 *

int finish_open(struct file *file, struct dentry *dentry,
                int (*open)(struct inode *, struct file *),
                int *opened)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/