Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs_db: improve the fsmap man page entry
Date: Tue, 1 Sep 2026 10:08:50 +0200	[thread overview]
Message-ID: <20260901080850.GA22531@lst.de> (raw)
In-Reply-To: <20260831144604.GE6072@frogsfrogsfrogs>

On Mon, Aug 31, 2026 at 07:46:04AM -0700, Darrick J. Wong wrote:
> On Mon, Aug 31, 2026 at 10:11:52AM +0300, Christoph Hellwig wrote:
> > Improve documentation of the flags and optional arguments, and fix up
> > messed up formatting.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> I wonder if it's worth documenting that fsmap -l shows external
> log device mappings?

That would be a bad idea, because it doesn't actually support that
option (in for-next at least).

  reply	other threads:[~2026-09-01  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  7:11 [PATCH] xfs_db: improve the fsmap man page entry Christoph Hellwig
2026-08-31 14:46 ` Darrick J. Wong
2026-09-01  8:08   ` Christoph Hellwig [this message]
2026-09-01 14:06     ` 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=20260901080850.GA22531@lst.de \
    --to=hch@lst.de \
    --cc=aalbersh@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