From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: type verification is expensive
Date: Thu, 25 Feb 2021 10:03:37 +0100 [thread overview]
Message-ID: <YDdn6f+6S/wCJDF+@infradead.org> (raw)
In-Reply-To: <20210223054748.3292734-2-david@fromorbit.com>
Any reason to not just mark them static inline and move them to
xfs_types.h?
next prev parent reply other threads:[~2021-02-25 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 5:47 [PATCH 0/3] xfs: 64kb directory block verification hurts Dave Chinner
2021-02-23 5:47 ` [PATCH 1/3] xfs: type verification is expensive Dave Chinner
2021-02-24 21:46 ` Darrick J. Wong
2021-02-25 9:03 ` Christoph Hellwig [this message]
2021-02-25 22:04 ` Dave Chinner
2021-02-23 5:47 ` [PATCH 2/3] xfs: No need for inode number error injection in __xfs_dir3_data_check Dave Chinner
2021-02-24 21:47 ` Darrick J. Wong
2021-02-25 9:06 ` Christoph Hellwig
2021-02-23 5:47 ` [PATCH 3/3] xfs: reduce debug overhead of dir leaf/node checks Dave Chinner
2021-02-24 21:50 ` Darrick J. Wong
2021-02-25 9:09 ` 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=YDdn6f+6S/wCJDF+@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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;
as well as URLs for NNTP newsgroup(s).