From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrey Albershteyn <aalbersh@redhat.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs_logprint: print log data to the screen in host-endian order
Date: Wed, 7 Jan 2026 09:22:08 -0800 [thread overview]
Message-ID: <20260107172208.GC15551@frogsfrogsfrogs> (raw)
In-Reply-To: <aV35idJuT2MZdpv_@infradead.org>
On Tue, Jan 06, 2026 at 10:13:29PM -0800, Christoph Hellwig wrote:
> On Tue, Jan 06, 2026 at 10:53:37AM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Don't make support have to byteswap u32 values when they're digging
> > through broken logs on x86 systems. Also make it more obvious which
> > column is the offset and which are the byte(s).
>
> I like the new output style. But this might break existing setups
> (or old users :)). So maybe make this conditional on a command line
> option instead?
Ok.
--D
prev parent reply other threads:[~2026-01-07 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 18:53 [PATCH] xfs_logprint: print log data to the screen in host-endian order Darrick J. Wong
2026-01-07 6:13 ` Christoph Hellwig
2026-01-07 17:22 ` Darrick J. Wong [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=20260107172208.GC15551@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=hch@infradead.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