Em Tue, 19 Jul 2016 17:30:24 -0600 Jonathan Corbet <corbet@xxxxxxx> escreveu: > On Sun, 17 Jul 2016 10:01:54 -0300 > Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx> wrote: > > > 4) There are now several errors when parsing functions. Those seems to > > happen when an argument is a function pointer, like: > > > > /devel/v4l/patchwork/Documentation/media/kapi/v4l2-core.rst:757: WARNING: Error when parsing function declaration. > > If the function has no return type: > > Error in declarator or parameters and qualifiers > > Invalid definition: Expected identifier in nested name, got keyword: int [error at 3] > > int v4l2_ctrl_add_handler (struct v4l2_ctrl_handler * hdl, struct v4l2_ctrl_handler * add, bool (*filter) (const struct v4l2_ctrl *ctrl) > > ---^ > > So I've been trying to reproduce this one, without success; it seems to > work for me. As it should; the parsing code really should not have > changed at all. Is there some particular context in which this happens > for you? You could pull from my tree and see it yourself: git://linuxtv.org/media_tree.git docs-next What I'm noticing is a series of problems when parsing some function declarations. The number of warnings varies, depending on the Sphinx version. Basically, on all versions, it doesn't recognize arguments like: bool (*filter) (const struct v4l2_ctrl *ctrl) (this comes from kernel-doc) Sphinx itself doesn't even recognize arguments with "enum" on versions 1.3.x or older. With enums, it will still add it to the book. Just the cross-reference at the index won't appear. Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
