From: Phillip Duncan <turtlekernelsanders@gmail.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs: tests: fix formatting in btrfs-tests
Date: Mon, 29 May 2023 18:02:38 -0700 [thread overview]
Message-ID: <ZHVLLpTHRvifOIHP@flip-desktop> (raw)
checkpatch.pl had a couple of formatting suggestions:
- #38: Don't use multiple blank lines
- #42: Missing a blank line after declarations
- #282: Alignment should match open parenthesis
Fixed these format suggestions, checkpatch.pl is a little cleaner now.
Signed-off-by: Phillip Duncan <turtlekernelsanders@gmail.com>
---
fs/btrfs/tests/btrfs-tests.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/tests/btrfs-tests.c b/fs/btrfs/tests/btrfs-tests.c
index ca09cf9afce8..1653456560c2 100644
--- a/fs/btrfs/tests/btrfs-tests.c
+++ b/fs/btrfs/tests/btrfs-tests.c
@@ -35,10 +35,10 @@ static const struct super_operations btrfs_test_super_ops = {
.destroy_inode = btrfs_test_destroy_inode,
};
-
static int btrfs_test_init_fs_context(struct fs_context *fc)
{
struct pseudo_fs_context *ctx = init_pseudo(fc, BTRFS_TEST_MAGIC);
+
if (!ctx)
return -ENOMEM;
ctx->ops = &btrfs_test_super_ops;
@@ -278,8 +278,7 @@ int btrfs_run_sanity_tests(void)
ret = btrfs_test_free_space_cache(sectorsize, nodesize);
if (ret)
goto out;
- ret = btrfs_test_extent_buffer_operations(sectorsize,
- nodesize);
+ ret = btrfs_test_extent_buffer_operations(sectorsize, nodesize);
if (ret)
goto out;
ret = btrfs_test_extent_io(sectorsize, nodesize);
--
2.34.1
next reply other threads:[~2023-05-30 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 1:02 Phillip Duncan [this message]
2023-05-30 18:54 ` [PATCH] btrfs: tests: fix formatting in btrfs-tests David Sterba
2023-05-30 19:14 ` Phillip Duncan
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=ZHVLLpTHRvifOIHP@flip-desktop \
--to=turtlekernelsanders@gmail.com \
--cc=Linux-btrfs@vger.kernel.org \
--cc=josef@toxicpanda.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