From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: cleanup error tags v3
Date: Fri, 19 Sep 2025 18:15:54 +0200 [thread overview]
Message-ID: <175829855464.1207654.11248308313339579475.b4-ty@kernel.org> (raw)
In-Reply-To: <20250918143454.447290-1-hch@lst.de>
On Thu, 18 Sep 2025 07:34:32 -0700, Christoph Hellwig wrote:
> while adding error injection to new code I'm writing I got really annoyed
> with all the places error tags had to be added. This series cleans the
> error tags so that only the definition and one table have to be updated.
> I've also cleaned up a lot of the surroundings while at it.
>
> Changes since v2:
> - improve comments in xfs_errortag.h, mostly based on text supplied
> by Darrick
> Changes since v1:
> - add a big fat comment and a idef/undef pair for the ERRTAGS magic
>
> [...]
Applied to for-next, thanks!
[1/5] xfs: remove xfs_errortag_get
commit: d5409ebf46bb0735ba26c64d7a9c80dde3f94eb6
[2/5] xfs: remove xfs_errortag_set
commit: 991dcadaddcced38c5d2da656862d94a1fc9e6e5
[3/5] xfs: remove the expr argument to XFS_TEST_ERROR
commit: 807df3227d7674d7957c576551d552acf15bb96f
[4/5] xfs: remove pointless externs in xfs_error.h
commit: b55dd72798115015908f4a17a1f8d70e8e974ab4
[5/5] xfs: centralize error tag definitions
commit: 71fa062196ae3abab790c91f1bdf09dcdc6fb1fe
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2025-09-19 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 14:34 cleanup error tags v3 Christoph Hellwig
2025-09-18 14:34 ` [PATCH 1/5] xfs: remove xfs_errortag_get Christoph Hellwig
2025-09-18 14:34 ` [PATCH 2/5] xfs: remove xfs_errortag_set Christoph Hellwig
2025-09-18 14:34 ` [PATCH 3/5] xfs: remove the expr argument to XFS_TEST_ERROR Christoph Hellwig
2025-09-18 14:34 ` [PATCH 4/5] xfs: remove pointless externs in xfs_error.h Christoph Hellwig
2025-09-18 14:34 ` [PATCH 5/5] xfs: centralize error tag definitions Christoph Hellwig
2025-09-19 16:15 ` Carlos Maiolino [this message]
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=175829855464.1207654.11248308313339579475.b4-ty@kernel.org \
--to=cem@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