From: Matthew Wilcox <willy@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Waiman Long <longman@redhat.com>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs changes for 6.11
Date: Thu, 18 Jul 2024 22:27:18 +0100 [thread overview]
Message-ID: <ZpmItplPA5_zmAmC@casper.infradead.org> (raw)
In-Reply-To: <5ypgzehnp2b3z2e5qfu2ezdtyk4dc4gnlvme54hm77aypl3flj@xlpjs7dbmkwu>
On Thu, Jul 18, 2024 at 05:20:54PM -0400, Kent Overstreet wrote:
> From: Kent Overstreet <kent.overstreet@linux.dev>
> Date: Thu, 18 Jul 2024 17:17:10 -0400
> Subject: [PATCH] lockdep: Add comments for lockdep_set_no{validate,track}_class()
>
> Cc: Waiman Long <longman@redhat.com>
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
>
> diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h
> index b76f1bcd2f7f..bdfbdb210fd7 100644
> --- a/include/linux/lockdep.h
> +++ b/include/linux/lockdep.h
> @@ -178,9 +178,22 @@ static inline void lockdep_init_map(struct lockdep_map *lock, const char *name,
> (lock)->dep_map.wait_type_outer, \
> (lock)->dep_map.lock_type)
>
> +/**
> + * lockdep_set_novalidate_class: disable checking of lock ordering on a given
> + * lock
> + *
> + * Lockdep will still record that this lock has been taken, and print held
> + * instances when dumping locks
> + */
Might want to run this through kernel-doc. I'm pretty sure it wants
macro comments to be formatted like function comments. ie:
/**
* lockdep_set_novalidate_class - Disable lock order checks on this lock.
* @lock: The lock to disable order checks for.
*
* Lockdep will still record that this lock has been taken, and print held
* instances when dumping locks.
*/
> #define lockdep_set_novalidate_class(lock) \
> lockdep_set_class_and_name(lock, &__lockdep_no_validate__, #lock)
next prev parent reply other threads:[~2024-07-18 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 1:26 [GIT PULL] bcachefs changes for 6.11 Kent Overstreet
2024-07-15 7:59 ` Stephen Rothwell
2024-07-17 18:53 ` Linus Torvalds
2024-07-18 21:20 ` Kent Overstreet
2024-07-18 21:27 ` Matthew Wilcox [this message]
2024-07-18 21:57 ` Waiman Long
2024-07-18 21:48 ` Waiman Long
2024-07-18 22:06 ` Linus Torvalds
2024-07-18 22:24 ` Kent Overstreet
2024-07-18 22:26 ` Linus Torvalds
2024-07-19 14:30 ` Theodore Ts'o
2024-07-20 15:48 ` mounts failing with -EBUSY on device mapper (was: Re: [GIT PULL] bcachefs changes for 6.11) Kent Overstreet
2024-07-22 11:45 ` Theodore Ts'o
2024-07-19 1:04 ` [GIT PULL] bcachefs changes for 6.11 pr-tracker-bot
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=ZpmItplPA5_zmAmC@casper.infradead.org \
--to=willy@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.