mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitor Massaru Iha <vitor@massaru.org>
To: unlisted-recipients:; (no To-header on input)
Cc: willy@infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	skhan@linuxfoundation.org
Subject: [PATCH 2/2] xarray: Add missing blank line after declaration
Date: Tue, 17 Mar 2020 22:43:03 -0300	[thread overview]
Message-ID: <7efa62f727eb176341fc0cdfcd47c890ff424451.1584494902.git.vitor@massaru.org> (raw)
In-Reply-To: <cover.1584494902.git.vitor@massaru.org>

Fix checkpatch warning: "WARNING: Missing a blank line after declarations"
in include/linux/xarray.h:1504

Signed-off-by: Vitor Massaru Iha <vitor@massaru.org>
---
 include/linux/xarray.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/xarray.h b/include/linux/xarray.h
index a7dec1ec0967..61f83aca2326 100644
--- a/include/linux/xarray.h
+++ b/include/linux/xarray.h
@@ -1624,6 +1624,7 @@ static inline unsigned int xas_find_chunk(struct xa_state *xas, bool advance,
 	if (XA_CHUNK_SIZE == BITS_PER_LONG) {
 		if (offset < XA_CHUNK_SIZE) {
 			unsigned long data = *addr & (~0UL << offset);
+
 			if (data)
 				return __ffs(data);
 		}
-- 
2.21.1


  parent reply	other threads:[~2020-03-18  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  1:43 [PATCH 0/2] xarrary: Fix warnings reported by checkpatch Vitor Massaru Iha
2020-03-18  1:43 ` [PATCH 1/2] xarray: Add identifier names for function definition arguments Vitor Massaru Iha
2020-03-18  1:43 ` Vitor Massaru Iha [this message]
2020-03-18  1:55   ` [PATCH 2/2] xarray: Add missing blank line after declaration Matthew Wilcox
2020-03-18  3:01     ` Vitor Massaru Iha

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=7efa62f727eb176341fc0cdfcd47c890ff424451.1584494902.git.vitor@massaru.org \
    --to=vitor@massaru.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=willy@infradead.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
all inboxes | Powered by JetHome®