All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul McQuade <paulmcquad@gmail.com>
To: Paul McQuade <paulmcquad@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: [PATCH] MM: Failslab.c use tabs where possible
Date: Tue, 30 Sep 2014 22:32:42 +0100	[thread overview]
Message-ID: <542B217A.3090002@gmail.com> (raw)



WARNING: multiple messages have this Message-ID (diff)
From: Paul McQuade <paulmcquad@gmail.com>
To: Paul McQuade <paulmcquad@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: [PATCH] MM: Failslab.c use tabs where possible
Date: Tue, 30 Sep 2014 22:32:42 +0100	[thread overview]
Message-ID: <542B217A.3090002@gmail.com> (raw)

>From e2cfaa7895f51147addf3e08c0556a76ed6e234e Mon Sep 17 00:00:00 2001
From: Paul McQuade <paulmcquad@gmail.com>
Date: Tue, 30 Sep 2014 22:28:08 +0100
Subject: [PATCH] MM: Failslab.c use tabs where possible

Removed code indent error

Signed-off-by: Paul McQuade <paulmcquad@gmail.com>
---
 mm/failslab.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/failslab.c b/mm/failslab.c
index fefaaba..2064225 100644
--- a/mm/failslab.c
+++ b/mm/failslab.c
@@ -16,7 +16,7 @@ bool should_failslab(size_t size, gfp_t gfpflags, unsigned long cache_flags)
     if (gfpflags & __GFP_NOFAIL)
         return false;
 
-        if (failslab.ignore_gfp_wait && (gfpflags & __GFP_WAIT))
+    if (failslab.ignore_gfp_wait && (gfpflags & __GFP_WAIT))
         return false;
 
     if (failslab.cache_filter && !(cache_flags & SLAB_FAILSLAB))
-- 
1.9.1


             reply	other threads:[~2014-09-30 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 21:32 Paul McQuade [this message]
2014-09-30 21:32 ` [PATCH] MM: Failslab.c use tabs where possible Paul McQuade

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=542B217A.3090002@gmail.com \
    --to=paulmcquad@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.