From: "tip-bot2 for Julian Wiedmann" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Julian Wiedmann <jwi@linux.ibm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] wait: use LIST_HEAD_INIT() to initialize wait_queue_head
Date: Mon, 28 Jun 2021 13:58:04 -0000 [thread overview]
Message-ID: <162488868420.395.8032632844768075125.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210601151120.329223-1-jwi@linux.ibm.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 77eccd0dfae353a64a2088d308bed3b373a4220f
Gitweb: https://git.kernel.org/tip/77eccd0dfae353a64a2088d308bed3b373a4220f
Author: Julian Wiedmann <jwi@linux.ibm.com>
AuthorDate: Tue, 01 Jun 2021 17:11:20 +02:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Mon, 28 Jun 2021 15:42:25 +02:00
wait: use LIST_HEAD_INIT() to initialize wait_queue_head
Replace the open-coded initialization with the right macro.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20210601151120.329223-1-jwi@linux.ibm.com
---
include/linux/wait.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/wait.h b/include/linux/wait.h
index fe10e85..99c5f05 100644
--- a/include/linux/wait.h
+++ b/include/linux/wait.h
@@ -56,7 +56,7 @@ struct task_struct;
#define __WAIT_QUEUE_HEAD_INITIALIZER(name) { \
.lock = __SPIN_LOCK_UNLOCKED(name.lock), \
- .head = { &(name).head, &(name).head } }
+ .head = LIST_HEAD_INIT(name.head) }
#define DECLARE_WAIT_QUEUE_HEAD(name) \
struct wait_queue_head name = __WAIT_QUEUE_HEAD_INITIALIZER(name)
prev parent reply other threads:[~2021-06-28 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:11 [PATCH tip/sched/core] wait: use LIST_HEAD_INIT() to initialize wait_queue_head Julian Wiedmann
2021-06-28 13:58 ` tip-bot2 for Julian Wiedmann [this message]
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=162488868420.395.8032632844768075125.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=jwi@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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 NNTP newsgroup(s).