From: Kent Overstreet <kent.overstreet@linux.dev>
To: Thomas Bertschinger <tahbertschinger@gmail.com>
Cc: linux-bcachefs@vger.kernel.org, bfoster@redhat.com
Subject: Re: [PATCH] bcachefs: create debugfs dir for each btree
Date: Thu, 14 Mar 2024 21:45:37 -0400 [thread overview]
Message-ID: <bfhyadqrf3oqmpn7c5biqoi3r5uzahsdwhnfscq3lhhgpf3f6m@jukn3ki46zgk> (raw)
In-Reply-To: <20240315012955.GA197197@fedora-laptop>
On Thu, Mar 14, 2024 at 07:29:55PM -0600, Thomas Bertschinger wrote:
> On Thu, Mar 14, 2024 at 08:05:57PM -0400, Kent Overstreet wrote:
> > nodes should actually be keys - nodes would be showing the node
> > structure, only cmd_list.rs currently does that (but -formats covers it)
> >
>
> Ah, yup. Should I send a v2, or is that a small enough fix that you can
> just amend it?
yeah I can do it
prev parent reply other threads:[~2024-03-15 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 16:02 [PATCH] bcachefs: create debugfs dir for each btree Thomas Bertschinger
2024-03-15 0:05 ` Kent Overstreet
2024-03-15 1:29 ` Thomas Bertschinger
2024-03-15 1:45 ` Kent Overstreet [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=bfhyadqrf3oqmpn7c5biqoi3r5uzahsdwhnfscq3lhhgpf3f6m@jukn3ki46zgk \
--to=kent.overstreet@linux.dev \
--cc=bfoster@redhat.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=tahbertschinger@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).