From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 19/23] xfs: factor out a btree block owner check
Date: Thu, 1 Feb 2024 22:23:43 -0800 [thread overview]
Message-ID: <ZbyKbwAhhYXCY1WI@infradead.org> (raw)
In-Reply-To: <170681334249.1604831.389334053004368592.stgit@frogsfrogsfrogs>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-02-02 6:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 19:39 [PATCHSET v29.2 1/8] xfs: move btree geometry to ops struct Darrick J. Wong
2024-02-01 19:39 ` [PATCH 01/23] xfs: consolidate btree block freeing tracepoints Darrick J. Wong
2024-02-02 6:18 ` Christoph Hellwig
2024-02-01 19:40 ` [PATCH 02/23] xfs: consolidate btree block allocation tracepoints Darrick J. Wong
2024-02-02 6:18 ` Christoph Hellwig
2024-02-01 19:40 ` [PATCH 03/23] xfs: set the btree cursor bc_ops in xfs_btree_alloc_cursor Darrick J. Wong
2024-02-01 19:40 ` [PATCH 04/23] xfs: drop XFS_BTREE_CRC_BLOCKS Darrick J. Wong
2024-02-02 6:19 ` Christoph Hellwig
2024-02-01 19:40 ` [PATCH 05/23] xfs: fix imprecise logic in xchk_btree_check_block_owner Darrick J. Wong
2024-02-02 6:22 ` Christoph Hellwig
2024-02-01 19:41 ` [PATCH 06/23] xfs: encode the btree geometry flags in the btree ops structure Darrick J. Wong
2024-02-02 6:23 ` Christoph Hellwig
2024-02-02 16:36 ` Darrick J. Wong
2024-02-01 19:41 ` [PATCH 07/23] xfs: remove bc_ino.flags Darrick J. Wong
2024-02-01 19:41 ` [PATCH 08/23] xfs: consolidate the xfs_alloc_lookup_* helpers Darrick J. Wong
2024-02-01 19:42 ` [PATCH 09/23] xfs: turn the allocbt cursor active field into a btree flag Darrick J. Wong
2024-02-01 19:42 ` [PATCH 10/23] xfs: extern some btree ops structures Darrick J. Wong
2024-02-01 19:42 ` [PATCH 11/23] xfs: initialize btree blocks using btree_ops structure Darrick J. Wong
2024-02-01 19:42 ` [PATCH 12/23] xfs: rename btree block/buffer init functions Darrick J. Wong
2024-02-01 19:43 ` [PATCH 13/23] xfs: btree convert xfs_btree_init_block to xfs_btree_init_buf calls Darrick J. Wong
2024-02-01 19:43 ` [PATCH 14/23] xfs: remove the unnecessary daddr paramter to _init_block Darrick J. Wong
2024-02-01 19:43 ` [PATCH 15/23] xfs: set btree block buffer ops in _init_buf Darrick J. Wong
2024-02-01 19:43 ` [PATCH 16/23] xfs: move lru refs to the btree ops structure Darrick J. Wong
2024-02-01 19:44 ` [PATCH 17/23] xfs: move the btree stats offset into struct btree_ops Darrick J. Wong
2024-02-01 19:44 ` [PATCH 18/23] xfs: factor out a xfs_btree_owner helper Darrick J. Wong
2024-02-01 19:44 ` [PATCH 19/23] xfs: factor out a btree block owner check Darrick J. Wong
2024-02-02 6:23 ` Christoph Hellwig [this message]
2024-02-01 19:44 ` [PATCH 20/23] xfs: store the btree pointer length in struct xfs_btree_ops Darrick J. Wong
2024-02-02 6:24 ` Christoph Hellwig
2024-02-01 19:45 ` [PATCH 21/23] xfs: split out a btree type from the btree ops geometry flags Darrick J. Wong
2024-02-01 19:45 ` [PATCH 22/23] xfs: split the per-btree union in struct xfs_btree_cur Darrick J. Wong
2024-02-01 19:45 ` [PATCH 23/23] xfs: create predicate to determine if cursor is at inode root level Darrick J. Wong
2024-02-02 6:24 ` Christoph Hellwig
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=ZbyKbwAhhYXCY1WI@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.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