From: Josef Bacik <josef@toxicpanda.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: use btrfs_is_testing() everywhere
Date: Fri, 19 Apr 2024 14:55:59 -0400 [thread overview]
Message-ID: <20240419185559.GA2726825@perftesting> (raw)
In-Reply-To: <20240417232452.20839-1-dsterba@suse.com>
On Thu, Apr 18, 2024 at 01:24:52AM +0200, David Sterba wrote:
> There are open coded tests of BTRFS_FS_STATE_DUMMY_FS_INFO and we have a
> wrapper for that that's a compile-time constant when self-tests are not
> built in. As this is only for development we can save some bytes and
> conditions on release configs by using the helper in the remaining
> cases.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
prev parent reply other threads:[~2024-04-19 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 23:24 [PATCH] btrfs: use btrfs_is_testing() everywhere David Sterba
2024-04-19 18:55 ` Josef Bacik [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=20240419185559.GA2726825@perftesting \
--to=josef@toxicpanda.com \
--cc=dsterba@suse.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