From: Joe Perches <joe@perches.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, gcc <gcc@gcc.gnu.org>
Subject: Re: [PATCH v3] workqueue: Wrap flush_workqueue() using a macro
Date: Mon, 16 May 2022 00:18:28 -0700 [thread overview]
Message-ID: <eaf82e8001a370d7be779bd15163f7210a968e8b.camel@perches.com> (raw)
In-Reply-To: <1c1b272b-239c-e1d1-84de-47d02feb911e@I-love.SAKURA.ne.jp>
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@intel.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.
> Changes in v2:
> Use "void (flush_workqueue)(struct workqueue_struct *wq)" and remove
> "#undef flush_workqueue", suggested by Joe Perches <joe@perches.com>.
next parent reply other threads:[~2022-05-16 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d34dac10-c12f-8bda-35c4-9cb158781db2@I-love.SAKURA.ne.jp>
[not found] ` <a6288570ed3534b0316723061f5604e3871accef.camel@perches.com>
[not found] ` <6e4ed62e-888b-6e7a-c13d-67656f39ca94@I-love.SAKURA.ne.jp>
[not found] ` <738afe71-2983-05d5-f0fc-d94efbdf7634@I-love.SAKURA.ne.jp>
[not found] ` <YnQKNea6KWFaWNis@slm.duckdns.org>
[not found] ` <a0d6b5e4-b9c8-1a43-570f-4c73b0f6fc0c@I-love.SAKURA.ne.jp>
[not found] ` <Yn0538VavQPv+/Ws@slm.duckdns.org>
[not found] ` <7b2fecdb-59ae-2c54-5a5b-774ef7054d1b@I-love.SAKURA.ne.jp>
[not found] ` <1c1b272b-239c-e1d1-84de-47d02feb911e@I-love.SAKURA.ne.jp>
2022-05-16 7:18 ` Joe Perches [this message]
2022-05-16 8:34 ` Rasmus Villemoes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eaf82e8001a370d7be779bd15163f7210a968e8b.camel@perches.com \
--to=joe@perches.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).