public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Matthew Brost <matthew.brost@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the workqueues tree
Date: Wed, 21 Aug 2024 13:45:31 +1000	[thread overview]
Message-ID: <20240821134531.1da04ae7@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

Hi all,

After merging the workqueues tree, today's linux-next build (htmldocs)
produced this warning:

include/linux/workqueue.h:547: warning: Excess function parameter '...' description in 'alloc_ordered_workqueue_lockdep_map'

Presumably introduced by commit

  9b59a85a84dc ("workqueue: Don't call va_start / va_end twice")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-08-21  3:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  3:45 Stephen Rothwell [this message]
2024-08-21 16:39 ` [PATCH wq/for-6.12] workqueue: Fix another htmldocs build warning Tejun Heo
2024-08-22  3:24   ` Matthew Brost
  -- strict thread matches above, loose matches on Subject: below --
2024-08-14  4:18 linux-next: build warning after merge of the workqueues tree Stephen Rothwell
2024-02-16  3:00 Stephen Rothwell
2024-02-16  4:46 ` Tejun Heo
2024-02-09  3:24 Stephen Rothwell
2024-02-09  3:45 ` Waiman Long
2024-01-30  2:37 Stephen Rothwell
2024-04-21 23:48 ` Stephen Rothwell
2024-04-22 19:59   ` Tejun Heo
2024-04-22 20:13   ` Tejun Heo
2023-01-13  3:31 Stephen Rothwell
2023-01-13 16:31 ` Tejun Heo
2023-01-13 16:47   ` Valentin Schneider
2023-01-13 16:48     ` Valentin Schneider
2023-01-13 17:16       ` Tejun Heo
2013-03-19  3:58 Stephen Rothwell

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=20240821134531.1da04ae7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --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