Am 20.07.2016 um 02:09 schrieb Mauro Carvalho Chehab :
> Em Tue, 19 Jul 2016 17:16:35 -0600
> Jonathan Corbet escreveu:
>
>> On Sun, 17 Jul 2016 10:01:54 -0300
>> Mauro Carvalho Chehab wrote:
>>
>>> 3) When there's an asterisk inside the source code, for example, to
>>> document a pointer, or
Am 20.07.2016 um 00:58 schrieb Jonathan Corbet :
> On Tue, 19 Jul 2016 12:00:24 +0200
> Markus Heiser wrote:
>
>> I recommend to consider to switch to the python version of the parser.
>> I know, that there is a natural shyness about a reimplementation in python
>> and thats why I offer to supp
Em Tue, 19 Jul 2016 17:30:24 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab 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/Do
Em Tue, 19 Jul 2016 17:01:33 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 2) For functions, kernel-doc is now an all or nothing. If not all
> > functions are declared, it outputs this warning:
> >
> > ./include/media/media-devnod
Em Tue, 19 Jul 2016 17:16:35 -0600
Jonathan Corbet escreveu:
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 3) When there's an asterisk inside the source code, for example, to
> > document a pointer, or when something else fails when parsing a
> > header file, kernel-
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab 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 func
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 3) When there's an asterisk inside the source code, for example, to
> document a pointer, or when something else fails when parsing a
> header file, kernel-doc handler just outputs:
> /devel/v4l/patchwork/Documentation/media/
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 2) For functions, kernel-doc is now an all or nothing. If not all
> functions are declared, it outputs this warning:
>
> ./include/media/media-devnode.h:1: warning: no structured comments
>
> And give up. No functions are e
On Tue, 19 Jul 2016 12:00:24 +0200
Markus Heiser wrote:
> I recommend to consider to switch to the python version of the parser.
> I know, that there is a natural shyness about a reimplementation in python
> and thats why I offer to support it for a long time period .. it would
> be a joy for me
Am 18.07.2016 um 13:54 schrieb Mauro Carvalho Chehab :
> Em Sun, 17 Jul 2016 20:37:19 -0600
> Jonathan Corbet escreveu:
>
>> [Back home and trying to get going on stuff for real. I'll look at the
>> issues listed in this message one at a time.]
>>
>> On Sun, 17 Jul 2016 10:01:54 -0300
>> Maur
Em Sun, 17 Jul 2016 20:37:19 -0600
Jonathan Corbet escreveu:
> [Back home and trying to get going on stuff for real. I'll look at the
> issues listed in this message one at a time.]
>
> On Sun, 17 Jul 2016 10:01:54 -0300
> Mauro Carvalho Chehab wrote:
>
> > 1) We now need to include each head
[Back home and trying to get going on stuff for real. I'll look at the
issues listed in this message one at a time.]
On Sun, 17 Jul 2016 10:01:54 -0300
Mauro Carvalho Chehab wrote:
> 1) We now need to include each header file with documentation twice,
> one to get the enums, structs, typedefs,
I'm now converting the kAPI media doc to RST file, and I'm seeing several
issues with kernel-doc conversion:
1) We now need to include each header file with documentation twice,
one to get the enums, structs, typedefs, ... and another one for the
functions:
.. kernel-doc:: include/media/m
13 matches
Mail list logo
