From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH RFC 0/2] btrfs-progs: boilerplate code for printing devices.
Date: Mon, 3 Jul 2023 15:55:41 +0800 [thread overview]
Message-ID: <cover.1688367941.git.anand.jain@oracle.com> (raw)
This is a set of boilerplate code to print the whole list of devices
wherever in the code, for example:
#include "kernel-shared/print-tree.h"
btrfs_print_devlist(NULL);
This code has been helping me to debug and fix certain bugs for some time.
The code is a port from its kernel version and has been roughly optimized
but not cleaned. However, I am sending it out to see if it can be integrated.
Otherwise, I am fine with maintaining it externally and keeping it updated
when needed. Thx.
Anand Jain (2):
btrfs-progs: print device list volumes-c api
btrfs-progs: print device list
kernel-shared/print-tree.c | 71 ++++++++++++++++++++++++++++++++++++++
kernel-shared/print-tree.h | 1 +
kernel-shared/volumes.c | 5 +++
kernel-shared/volumes.h | 2 +-
4 files changed, 78 insertions(+), 1 deletion(-)
--
2.31.1
next reply other threads:[~2023-07-03 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:55 Anand Jain [this message]
2023-07-03 7:55 ` [PATCH RFC 1/2] btrfs-progs: print device list volumes-c api Anand Jain
2023-07-03 7:55 ` [PATCH RFC 2/2] btrfs-progs: print device list Anand Jain
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=cover.1688367941.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@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