linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian <sebastian.scherbel@fau.de>
To: dsterba@suse.com
Cc: josef@toxicpanda.com, clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@i4.cs.fau.de,
	Sebastian Scherbel <sebastian.scherbel@fau.de>
Subject: [PATCH 0/5] btrfs: code cleanup
Date: Tue, 10 Dec 2019 08:13:52 +0100	[thread overview]
Message-ID: <20191210071357.5323-1-sebastian.scherbel@fau.de> (raw)

From: Sebastian Scherbel <sebastian.scherbel@fau.de>

This patch series changes several instances in btrfs where the coding style
is not in line with the Linux kernel guidelines to improve readability.

Sebastian Scherbel (5):
  fs_btrfs_sysfs: code cleanup
  fs_btrfs_struct-funcs: code cleanup
  fs_btrfs_ref-verify: code cleanup
  fs_btrfs_qgroup: code cleanup
  fs_btrfs_block-group: code cleanup

 fs/btrfs/block-group.c  | 21 ++++++++++------
 fs/btrfs/block-group.h  |  8 +++---
 fs/btrfs/qgroup.c       | 54 +++++++++++++++++++++++------------------
 fs/btrfs/qgroup.h       | 12 ++++-----
 fs/btrfs/ref-verify.c   |  6 ++---
 fs/btrfs/struct-funcs.c |  5 ++--
 fs/btrfs/sysfs.c        | 33 +++++++++++++++++++------
 fs/btrfs/sysfs.h        |  5 ++--
 8 files changed, 89 insertions(+), 55 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-12-10  7:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  7:13 Sebastian [this message]
2019-12-10  7:13 ` [PATCH 1/5] fs_btrfs_sysfs: code cleanup Sebastian
2019-12-10  7:13 ` [PATCH 2/5] fs_btrfs_struct-funcs: " Sebastian
2019-12-10  7:13 ` [PATCH 3/5] fs_btrfs_ref-verify: " Sebastian
2019-12-10  7:13 ` [PATCH 4/5] fs_btrfs_qgroup: " Sebastian
2019-12-10  7:13 ` [PATCH 5/5] fs_btrfs_block-group: " Sebastian
2019-12-10 12:19 ` [PATCH 0/5] btrfs: " David Sterba

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=20191210071357.5323-1-sebastian.scherbel@fau.de \
    --to=sebastian.scherbel@fau.de \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@i4.cs.fau.de \
    /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 NNTP newsgroup(s).