[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c6f00f4-e8c2-3ffd-fead-cbc2b6e8f88a@prevas.dk>
Date:   Mon, 16 May 2022 10:34:40 +0200
From:   Rasmus Villemoes <rasmus.villemoes@...vas.dk>
To:     Joe Perches <joe@...ches.com>,
        Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
        Tejun Heo <tj@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, gcc <gcc@....gnu.org>
Subject: Re: [PATCH v3] workqueue: Wrap flush_workqueue() using a macro
On 16/05/2022 09.18, Joe Perches wrote:
> On Mon, 2022-05-16 at 14:00 +0900, Tetsuo Handa wrote:
> []
>> Changes in v3:
>>   Revert suggested change in v2, for kernel test robot <lkp@...el.com> found
>>
>>     warning: Function parameter or member 'flush_workqueue' not described in 'void'
>>     warning: expecting prototype for flush_workqueue(). Prototype was for void() instead
>>
>>   when built with W=1 option.
> 
> Odd, perhaps that not a valid error message and is a defect
> in gcc's parsing of function definitions.
Nah, gcc isn't buggy in such a fundamental part of parsing C. It's not a
warning from gcc, nor from sparse (or smatch).
It's from the perl script scripts/kernel-doc .
Rasmus
Powered by blists - more mailing lists
 
