From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Whitehouse <swhiteho@redhat•com>,
Bob Peterson <rpeterso@redhat•com>
Cc: Andreas Gruenbacher <agruenba@redhat•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the gfs2 tree
Date: Wed, 29 May 2024 14:24:55 +1000 [thread overview]
Message-ID: <20240529142455.1c68e65a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
Hi all,
After merging the gfs2 tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/filesystems/gfs2-glocks.rst:64: ERROR: Malformed table.
Text in column margin in table line 7.
============= =============================================================
Field Purpose
============= =============================================================
go_sync Called before remote state change (e.g. to sync dirty data)
go_xmote_bh Called after remote state change (e.g. to refill cache)
go_inval Called if remote state change requires invalidating the cache
go_instantiate Called when a glock has been acquired
go_held Called every time a glock holder is acquired
go_dump Called to print content of object for debugfs file, or on
error to dump glock to the log.
go_callback Called if the DLM sends a callback to drop this lock
go_unlocked Called when a glock is unlocked (dlm_unlock())
go_type The type of the glock, ``LM_TYPE_*``
go_flags GLOF_ASPACE is set, if the glock has an address space
associated with it
============= =============================================================
Documentation/filesystems/gfs2-glocks.rst:96: ERROR: Malformed table.
Text in column margin in table line 7.
============= ====================== =============================
Operation GLF_LOCK bit lock held gl_lockref.lock spinlock held
============= ====================== =============================
go_sync Yes No
go_xmote_bh Yes No
go_inval Yes No
go_instantiate No No
go_held No No
go_dump Sometimes Yes
go_callback Sometimes (N/A) Yes
go_unlocked Yes No
============= ====================== =============================
Introduced by commit
ded323aef6d5 ("gfs2: Update glocks documentation")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-29 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 4:24 Stephen Rothwell [this message]
2024-05-29 13:40 ` linux-next: build warnings after merge of the gfs2 tree Andreas Gruenbacher
2024-05-31 0:00 ` Stephen Rothwell
2024-06-10 12:53 ` Andreas Gruenbacher
2024-06-10 22:12 ` 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=20240529142455.1c68e65a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=agruenba@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rpeterso@redhat$(echo .)com \
--cc=swhiteho@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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