From: Christoph Hellwig <hch@infradead.org>
To: Jeremy Bingham <jbingham@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
brauner@kernel.org, jkoolstra@xs4all.nl, jack@suse.cz,
djwong@kernel.org, hch@infradead.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v1 1/1] minix: consolidate itree* files into one itree.c file
Date: Mon, 5 Oct 2026 01:18:52 -0700 [thread overview]
Message-ID: <asNdbGAe7XGL3iBI@infradead.org> (raw)
In-Reply-To: <29e5bed16cef4904e9649a9b77d42ec10cd33051.1790359547.git.jbingham@gmail.com>
On Mon, Sep 28, 2026 at 01:04:26PM -0700, Jeremy Bingham wrote:
> Consolidate the itree functions by adding fields to the superblock info
> struct to store the number of direct blocks and levels of indirect
> blocks because the different versions of the minix filesystems have
> differing numbers of indirect block pointers and different block pointer
> sizes. This allows consolidating the itree functions into one itree.c
> file instead of a system with version specific itree files with version
> specific definitions and wrapper functions that #include a common
> itree_common.c file that are in turn called by wrapper functions
> elsewhere in the code that call the version specific wrapper functions.
>
> No functional changes are intended for this patch.
>
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> Suggested-by: Darrick J. Wong <djwong@kernel.org>
> Signed-off-by: Jeremy Bingham <jbingham@gmail.com>
Looks good from the high-level perspective:
Reviewed-by: Christoph Hellwig <hch@lst.de>
I assume you've run xfstests and checked nothing regresseѕ?
next prev parent reply other threads:[~2026-10-05 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:04 [PATCH v1 0/1] minix: unify the v1 and v2/v3 itree code paths Jeremy Bingham
2026-09-28 20:04 ` [PATCH v1 1/1] minix: consolidate itree* files into one itree.c file Jeremy Bingham
2026-10-05 8:18 ` Christoph Hellwig [this message]
2026-10-05 19:45 ` Jeremy Bingham
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=asNdbGAe7XGL3iBI@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=jbingham@gmail.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.