From: David Sterba <dsterba@suse.cz>
To: Phillip Duncan <turtlekernelsanders@gmail.com>
Cc: Josef Bacik <josef@toxicpanda.com>, Linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: tests: fix formatting in btrfs-tests
Date: Tue, 30 May 2023 20:54:11 +0200 [thread overview]
Message-ID: <20230530185411.GD32581@twin.jikos.cz> (raw)
In-Reply-To: <ZHVLLpTHRvifOIHP@flip-desktop>
On Mon, May 29, 2023 at 06:02:38PM -0700, Phillip Duncan wrote:
> 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.
Please don't send such patches, or at least not to btrfs. A more
elaborate answer:
https://btrfs.readthedocs.io/en/latest/dev/Developer-s-FAQ.html#how-not-to-start
next prev parent reply other threads:[~2023-05-30 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 1:02 [PATCH] btrfs: tests: fix formatting in btrfs-tests Phillip Duncan
2023-05-30 18:54 ` David Sterba [this message]
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=20230530185411.GD32581@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Linux-btrfs@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=turtlekernelsanders@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