Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/7] xfs: merge healthmon insert/push helpers
Date: Mon, 31 Aug 2026 08:59:33 +0200	[thread overview]
Message-ID: <20260831065933.GF24602@lst.de> (raw)
In-Reply-To: <178780640668.3528467.13347610952808276371.stgit@frogsfrogsfrogs>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>


  reply	other threads:[~2026-08-31  6:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  5:31 [PATCHSET v2 2/2] xfs: LLM-inspired bug fixes, part 8 Darrick J. Wong
2026-08-27  5:32 ` [PATCH 1/7] xfs: always set xfs_healthmon::first_event when inserting at front of list Darrick J. Wong
2026-08-31  6:54   ` Christoph Hellwig
2026-08-27  5:32 ` [PATCH 2/7] xfs: port healthmon event list to list_head Darrick J. Wong
2026-08-27  9:33   ` Anuj Gupta
2026-08-27 14:47     ` Darrick J. Wong
2026-08-31  6:58       ` Christoph Hellwig
2026-08-31 14:53         ` Darrick J. Wong
2026-08-31  6:58   ` Christoph Hellwig
2026-08-31 15:12     ` Darrick J. Wong
2026-08-27  5:33 ` [PATCH 3/7] xfs: check healthmon outbuffer space correctly Darrick J. Wong
2026-08-31  6:59   ` Christoph Hellwig
2026-08-27  5:33 ` [PATCH 4/7] xfs: merge healthmon insert/push helpers Darrick J. Wong
2026-08-31  6:59   ` Christoph Hellwig [this message]
2026-08-27  5:33 ` [PATCH 5/7] xfs: bump lost_prev_errors if we lose even the healthmon lost event Darrick J. Wong
2026-08-27  5:34 ` [PATCH 6/7] xfs: report nonexistent parents as a filesystem corruption Darrick J. Wong
2026-08-27  5:34 ` [PATCH 7/7] xfs: destroy seen inode bitmap when we fail to add a dirpath Darrick J. Wong

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=20260831065933.GF24602@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --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