From: Waiman Long <longman@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [REPOST PATCH] locking/lockdep: Remove lockdep_init_map_crosslock.
Date: Fri, 10 Jun 2022 19:04:32 -0400 [thread overview]
Message-ID: <f8f612f1-0d32-4275-88e7-d1beb9b03b93@redhat.com> (raw)
In-Reply-To: <YqITgY+2aPITu96z@linutronix.de>
On 6/9/22 11:36, Sebastian Andrzej Siewior wrote:
> The cross-release bits have been removed, lockdep_init_map_crosslock() is
> a leftover.
>
> Remove lockdep_init_map_crosslock.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Reviewed-by: Waiman Long <longman@redhat.com>
> Link: https://lore.kernel.org/r/20220311164457.46461-1-bigeasy@linutronix.de
> ---
> include/linux/lockdep.h | 1 -
> 1 file changed, 1 deletion(-)
>
> --- a/include/linux/lockdep.h
> +++ b/include/linux/lockdep.h
> @@ -431,7 +431,6 @@ enum xhlock_context_t {
> XHLOCK_CTX_NR,
> };
>
> -#define lockdep_init_map_crosslock(m, n, k, s) do {} while (0)
> /*
> * To initialize a lockdep_map statically use this macro.
> * Note that _name must not be NULL.
>
Acked-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2022-06-10 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:36 Sebastian Andrzej Siewior
2022-06-10 23:04 ` Waiman Long [this message]
2023-01-12 8:53 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2022-05-11 11:26 Sebastian Andrzej Siewior
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=f8f612f1-0d32-4275-88e7-d1beb9b03b93@redhat.com \
--to=longman@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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
all inboxes | Powered by JetHome®