Re: [RFC] scripts: kernel-doc: fix array element capture in pointer-to-func parsing

2021-02-23 Thread Aditya
On 23/2/21 3:03 am, Jonathan Corbet wrote: > Aditya Srivastava writes: > >> Currently, kernel-doc causes an unexpected error when array element (i.e., >> "type (*foo[bar])(args)") is present as pointer parameter in >> pointer-to-function parsing. >> >> For e.g., running kernel-doc -none on

Re: [RFC] scripts: kernel-doc: fix array element capture in pointer-to-func parsing

2021-02-22 Thread Jonathan Corbet
Aditya Srivastava writes: > Currently, kernel-doc causes an unexpected error when array element (i.e., > "type (*foo[bar])(args)") is present as pointer parameter in > pointer-to-function parsing. > > For e.g., running kernel-doc -none on kernel/gcov/gcc_4_7.c causes this > error: > "Use of

Re: [RFC] scripts: kernel-doc: fix array element capture in pointer-to-func parsing

2021-02-19 Thread Lukas Bulwahn
On Wed, Feb 17, 2021 at 3:56 PM Aditya Srivastava wrote: > > Currently, kernel-doc causes an unexpected error when array element (i.e., > "type (*foo[bar])(args)") is present as pointer parameter in > pointer-to-function parsing. > > For e.g., running kernel-doc -none on kernel/gcov/gcc_4_7.c

[RFC] scripts: kernel-doc: fix array element capture in pointer-to-func parsing

2021-02-17 Thread Aditya Srivastava
Currently, kernel-doc causes an unexpected error when array element (i.e., "type (*foo[bar])(args)") is present as pointer parameter in pointer-to-function parsing. For e.g., running kernel-doc -none on kernel/gcov/gcc_4_7.c causes this error: "Use of uninitialized value $param in regexp