linux-kernel - Re: [PATCH] Documentation: Update filesystems/debugfs.txt

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20150716033704.7a4e1a5b@lwn.net>
Date:	Thu, 16 Jul 2015 03:37:04 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Wang Long <long.wanglong@...wei.com>
Cc:	<gregkh@...uxfoundation.org>, <rostedt@...dmis.org>,
	<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<peifeiyue@...wei.com>, <wanglong@...qinren.net>
Subject: Re: [PATCH] Documentation: Update filesystems/debugfs.txt

On Thu, 16 Jul 2015 06:31:16 +0000
Wang Long <long.wanglong@...wei.com> wrote:

> This patch update the Documentation/filesystems/debugfs.txt
> file. The main work is to add the description of the following
> functions:
>     debugfs_create_atomic_t
>     debugfs_create_u32_array
>     debugfs_create_devm_seqfile
>     debugfs_create_file_size

I'll apply this because it's a definite improvement over what is there
now, but it would be nice to describe these functions a bit more in
detail.  In particular, a name like debugfs_create_devm_seqfile() will
cause at least some developers to think it will clean itself up when the
device goes away, but that does not appear to actually be the case...

>  Copyright 2009 Jonathan Corbet <corbet@....net>
> +Updated by Wang Long <long.wanglong@...wei.com> on 2015/07/16

I think I'll drop that line, though; that's what the source code
management system is for.  Arguably the line it follows doesn't really
need to be there either...

Thanks,

jon
--
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/