All of lore.kernel.org
 help / color / mirror / Atom feed
From: Achilles Gaikwad <achillesgaikwad@gmail.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH] fs/xfs/kmem.c: fix coding style, using 'unsigned int' instead of 'unsigned'
Date: Fri, 25 Aug 2017 10:56:59 +0530	[thread overview]
Message-ID: <20170825052659.GA11087@fubar> (raw)

Fixes a warning given by checkpatch.pl to use 'unsigned int'
instead of just 'unsigned'.

WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
+	unsigned nofs_flag = 0;

Signed-off-by: Achilles Gaikwad <achillesgaikwad@gmail.com>
---
 fs/xfs/kmem.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/kmem.c b/fs/xfs/kmem.c
index 393b6849aeb3..a20909087e5e 100644
--- a/fs/xfs/kmem.c
+++ b/fs/xfs/kmem.c
@@ -48,7 +48,7 @@ kmem_alloc(size_t size, xfs_km_flags_t flags)
 void *
 kmem_zalloc_large(size_t size, xfs_km_flags_t flags)
 {
-	unsigned nofs_flag = 0;
+	unsigned int nofs_flag = 0;
 	void	*ptr;
 	gfp_t	lflags;
 
-- 
2.13.5


             reply	other threads:[~2017-08-25  5:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  5:26 Achilles Gaikwad [this message]
2017-08-25  7:45 ` [PATCH] fs/xfs/kmem.c: fix coding style, using 'unsigned int' instead of 'unsigned' Christoph Hellwig

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=20170825052659.GA11087@fubar \
    --to=achillesgaikwad@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.