From: Philippe Loctaux <phil@philippeloctaux.com>
To: clm@fb.com
Cc: jbacik@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Philippe Loctaux <phil@philippeloctaux.com>
Subject: [PATCH] Btrfs: check-integrity: fixed a comment block coding style issue
Date: Sun, 21 Feb 2016 23:33:52 +0100 [thread overview]
Message-ID: <1456094032-12447-1-git-send-email-phil@philippeloctaux.com> (raw)
Makes the comment block start with /* on a separate line, and end
with */ on a separate line as well.
Signed-off-by: Philippe Loctaux <phil@philippeloctaux.com>
---
fs/btrfs/check-integrity.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/check-integrity.c b/fs/btrfs/check-integrity.c
index 861d472..92436c7 100644
--- a/fs/btrfs/check-integrity.c
+++ b/fs/btrfs/check-integrity.c
@@ -226,8 +226,10 @@ struct btrfsic_block_data_ctx {
void *mem_to_free;
};
-/* This structure is used to implement recursion without occupying
- * any stack space, refer to btrfsic_process_metablock() */
+/*
+ * This structure is used to implement recursion without occupying
+ * any stack space, refer to btrfsic_process_metablock()
+ */
struct btrfsic_stack_frame {
u32 magic;
u32 nr;
--
2.7.1
reply other threads:[~2016-02-21 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1456094032-12447-1-git-send-email-phil@philippeloctaux.com \
--to=phil@philippeloctaux.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).