[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180515144244.GA32583@lst.de>
Date: Tue, 15 May 2018 16:42:44 +0200
From: Christoph Hellwig <hch@....de>
To: David Howells <dhowells@...hat.com>
Cc: Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-rtc@...r.kernel.org, Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
jfs-discussion@...ts.sourceforge.net,
linux-afs@...ts.infradead.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
Jiri Slaby <jslaby@...e.com>, linux-ext4@...r.kernel.org,
Alexey Dobriyan <adobriyan@...il.com>,
megaraidlinux.pdl@...adcom.com, drbd-dev@...ts.linbit.com
Subject: Re: [PATCH 04/40] proc: introduce proc_create_seq{,_data}
On Mon, Apr 30, 2018 at 02:19:25PM +0100, David Howells wrote:
> Christoph Hellwig <hch@....de> wrote:
>
> > +
> > +struct proc_dir_entry *proc_create_seq_data(const char *name, umode_t mode,
> > + struct proc_dir_entry *parent, const struct seq_operations *ops,
> > + void *data)
> > +{
> > ...
> > +EXPORT_SYMBOL(proc_create_seq_data);
>
> Please add documentation comments to exported functions when you add them.
None of the base functions are document, and we really want people to not
use procfs for new code anyway. But if I get some consensus from the
maintainers and the list I can throw in another patch to document
all proc_create* variants.
Powered by blists - more mailing lists