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
On Wed, May 29, 2024 at 6:34 AM Stephen Rothwell <[email protected]> wrote:
> 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.
Fixed, thanks.
Could you please remove Bob Peterson <[email protected]> from the
recipients of these notifications as that address no longer exists?
Thanks,
Andreas
Hi Andreas,
On Wed, 29 May 2024 15:40:13 +0200 Andreas Gruenbacher <[email protected]> wrote:
>
> Could you please remove Bob Peterson <[email protected]> from the
> recipients of these notifications as that address no longer exists?
Done. Who should actually be the contacts for this tree, I currently
have only Steven Whitehouse listed.
--
Cheers,
Stephen Rothwell
On Fri, May 31, 2024 at 2:00 AM Stephen Rothwell <[email protected]> wrote:
> Hi Andreas,
>
> On Wed, 29 May 2024 15:40:13 +0200 Andreas Gruenbacher <[email protected]> wrote:
> >
> > Could you please remove Bob Peterson <[email protected]> from the
> > recipients of these notifications as that address no longer exists?
>
> Done. Who should actually be the contacts for this tree, I currently
> have only Steven Whitehouse listed.
Could you please add me, as I'm the maintainer. Steven almost isn't
active in the development of gfs2 at all anymore, but still very much
on the management side, so it probably makes sense to keep him in the
list as well.
Thanks,
Andreas
Hi Andreas,
On Mon, 10 Jun 2024 14:53:28 +0200 Andreas Gruenbacher <[email protected]> wrote:
>
> On Fri, May 31, 2024 at 2:00 AM Stephen Rothwell <[email protected]> wrote:
> >
> > Done. Who should actually be the contacts for this tree, I currently
> > have only Steven Whitehouse listed.
>
> Could you please add me, as I'm the maintainer. Steven almost isn't
> active in the development of gfs2 at all anymore, but still very much
> on the management side, so it probably makes sense to keep him in the
> list as well.
Done.
--
Cheers,
Stephen Rothwell