From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Carlos Maiolino <cmaiolino@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] libxfs: remove the unused fs_topology_t typedef
Date: Fri, 12 Jan 2024 17:48:17 +0100 [thread overview]
Message-ID: <20240112164817.GC16766@lst.de> (raw)
In-Reply-To: <20240112164450.GU722975@frogsfrogsfrogs>
On Fri, Jan 12, 2024 at 08:44:50AM -0800, Darrick J. Wong wrote:
> Dumb nit: the ampersand in the comment can go away too ^
It'll go away in the next patch.
next prev parent reply other threads:[~2024-01-12 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 4:47 fix log sector size detection Christoph Hellwig
2024-01-12 4:47 ` [PATCH 1/4] libxfs: remove the unused fs_topology_t typedef Christoph Hellwig
2024-01-12 16:44 ` Darrick J. Wong
2024-01-12 16:48 ` Christoph Hellwig [this message]
2024-01-12 16:54 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 2/4] libxfs: refactor the fs_topology structure Christoph Hellwig
2024-01-12 16:52 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 3/4] libxfs: also query log device topology in get_topology Christoph Hellwig
2024-01-12 16:52 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 4/4] mkfs: use a sensible log sector size default Christoph Hellwig
2024-01-12 16:53 ` 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=20240112164817.GC16766@lst.de \
--to=hch@lst.de \
--cc=cmaiolino@redhat.com \
--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