From: Joe Perches <joe@perches.com>
To: Kautuk Consul <consul.kautuk@gmail.com>
Cc: davem@davemloft.net,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 19/20 v3] sparc/mm/fault_32.c: Port OOM changes to do_sparc_fault
Date: Mon, 26 Mar 2012 09:32:09 -0700 [thread overview]
Message-ID: <1332779529.6160.96.camel@joe2Laptop> (raw)
In-Reply-To: <CAFPAmTSyYJkATAD32WqHZY_PdWGjitEq4vgqCZeqjo+V24dh3Q@mail.gmail.com>
On Mon, 2012-03-26 at 12:20 -0400, Kautuk Consul wrote:
> > David meant that the indentation should be aligned
> > immediately after the open parenthesis:
> >
> > + unsigned int flags = (FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_KILLABLE |
> > + (write ? FAULT_FLAG_WRITE : 0));
> >
> > though perhaps this is clearer as:
> >
> > unsigned int flags = FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_KILLABLE;
> >
> > if (write)
> > flags |= FAULT_FLAG_WRITE;
> >
> > or even separate sets.
> >
> > if (write)
> > flags = foo;
> > else
> > flags = bar;
>
> This is how it is in the patch file(immediately after the paramthesis).
> I have now attached both sparc patches to this email.
>
> you must be having the same problem in viewing the patch file
> as me due to the email client itself inserting invalid spaces here and there.
Nope. That's not it.
> by the way, what tab-spaces are you using when you open it in vim ?
I use vim as an editor as infrequently as possible.
Your original patch used 6 tabs and 2 spaces.
Tab size in kernel style is always 8.
Again, make sure your tab indentation is set to 8.
next prev parent reply other threads:[~2012-03-26 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:32 Kautuk Consul
2012-03-26 16:16 ` Joe Perches
2012-03-26 16:20 ` Kautuk Consul
2012-03-26 16:32 ` Joe Perches [this message]
2012-03-26 16:55 ` Kautuk Consul
2012-03-26 17:03 ` Joe Perches
2012-03-26 17:05 ` Kautuk Consul
2012-03-26 16:36 ` Sam Ravnborg
2012-03-26 20:09 ` David Miller
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=1332779529.6160.96.camel@joe2Laptop \
--to=joe@perches.com \
--cc=a.p.zijlstra@chello.nl \
--cc=consul.kautuk@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.gortmaker@windriver.com \
--cc=sparclinux@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
all inboxes | Powered by JetHome®