linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Wiedmann <jwi@linux.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: Julian Wiedmann <jwi@linux.ibm.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH wq/for-next 2/2] workqueue: clean up for_each_pwq()'s documentation
Date: Wed,  2 Jun 2021 13:16:55 +0200	[thread overview]
Message-ID: <20210602111655.3808580-2-jwi@linux.ibm.com> (raw)
In-Reply-To: <20210602111655.3808580-1-jwi@linux.ibm.com>

The if/else clause was removed with commit 5a6446626d7e
("workqueue: Convert for_each_wq to use built-in list check").

Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
---
 kernel/workqueue.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 8a700ccfa313..104e3ef04e33 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -418,9 +418,6 @@ static void show_pwq(struct pool_workqueue *pwq);
  * This must be called either with wq->mutex held or RCU read locked.
  * If the pwq needs to be used beyond the locking in effect, the caller is
  * responsible for guaranteeing that the pwq stays online.
- *
- * The if/else clause exists only for the lockdep assertion and can be
- * ignored.
  */
 #define for_each_pwq(pwq, wq)						\
 	list_for_each_entry_rcu((pwq), &(wq)->pwqs, pwqs_node,		\
-- 
2.25.1


  reply	other threads:[~2021-06-02 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 11:16 [PATCH wq/for-next 1/2] workqueue: replace open-coded work_pending() Julian Wiedmann
2021-06-02 11:16 ` Julian Wiedmann [this message]
2021-06-04 14:53   ` [PATCH wq/for-next 2/2] workqueue: clean up for_each_pwq()'s documentation Tejun Heo
2021-06-03  2:20 ` [PATCH wq/for-next 1/2] workqueue: replace open-coded work_pending() Lai Jiangshan
2021-06-04 14:53 ` Tejun Heo

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=20210602111655.3808580-2-jwi@linux.ibm.com \
    --to=jwi@linux.ibm.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --subject='Re: [PATCH wq/for-next 2/2] workqueue: clean up for_each_pwq()'\''s documentation' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox