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>,
	Ole Wiedemann <ole.wiedemann@fau.de>
Subject: [PATCH 2/5] fs_btrfs_struct-funcs: code cleanup
Date: Tue, 10 Dec 2019 08:13:54 +0100	[thread overview]
Message-ID: <20191210071357.5323-3-sebastian.scherbel@fau.de> (raw)
In-Reply-To: <20191210071357.5323-1-sebastian.scherbel@fau.de>

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

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

1. missing blank lines after decleration are added
2. tabs are used for indentations where possible

Signed-off-by: Sebastian Scherbel <sebastian.scherbel@fau.de>
Co-developed-by: Ole Wiedemann <ole.wiedemann@fau.de>
Signed-off-by: Ole Wiedemann <ole.wiedemann@fau.de>
---
 fs/btrfs/struct-funcs.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/fs/btrfs/struct-funcs.c b/fs/btrfs/struct-funcs.c
index 73f7987143df..4f63e69c5387 100644
--- a/fs/btrfs/struct-funcs.c
+++ b/fs/btrfs/struct-funcs.c
@@ -9,12 +9,12 @@
 
 static inline u8 get_unaligned_le8(const void *p)
 {
-       return *(u8 *)p;
+	return *(u8 *)p;
 }
 
 static inline void put_unaligned_le8(u8 val, void *p)
 {
-       *(u8 *)p = val;
+	*(u8 *)p = val;
 }
 
 /*
@@ -173,6 +173,7 @@ void btrfs_node_key(const struct extent_buffer *eb,
 		    struct btrfs_disk_key *disk_key, int nr)
 {
 	unsigned long ptr = btrfs_node_key_ptr_offset(nr);
+
 	read_eb_member(eb, (struct btrfs_key_ptr *)ptr,
 		       struct btrfs_key_ptr, key, disk_key);
 }
-- 
2.20.1


  parent 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 [PATCH 0/5] btrfs: code cleanup Sebastian
2019-12-10  7:13 ` [PATCH 1/5] fs_btrfs_sysfs: " Sebastian
2019-12-10  7:13 ` Sebastian [this message]
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-3-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 \
    --cc=ole.wiedemann@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).