From: Richard Hartmann <richih.mailinglist@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Benjamin Gilbert <bgilbert@cs.cmu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/19] crypto: proc - Fix checkpatch errors
Date: Fri, 19 Feb 2010 11:10:47 +0100 [thread overview]
Message-ID: <2d460de71002190210qb9d5685n2fca0e7eff011b04@mail.gmail.com> (raw)
In-Reply-To: <m1d402t2qp.fsf@fess.ebiederm.org>
On Fri, Feb 19, 2010 at 02:48, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Why did you replaced a tab with spaces here??
The first tab is indentation, displaying the logical nesting level.
The second tab including the whitespaces after it was formatting.
Although the official tab width in the linux kernel is 8 chars, not
all code adheres to this rule. Maintaining a clear separation between
indentation and formatting, i.e. using tabs as initially intended, helps
to keep everyone happy, no matter what tab width they use.
If this change is actually controversial, I have no problem removing
this part from the patch. However, it is my _strong_ feeling, that it is
beneficial to keep it.
If there is any wider interest in this topic, I am more than willing to
take this up on the main list in a separate thread. Unless it has
already been discussed, of course.
Thanks for looking at the patch,
Richard
next prev parent reply other threads:[~2010-02-19 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 0:22 Richard Hartmann
2010-02-19 1:48 ` Eric W. Biederman
2010-02-19 10:10 ` Richard Hartmann [this message]
2010-02-19 12:17 ` Herbert Xu
2010-02-19 16:35 ` Richard Hartmann
2010-02-20 0:46 ` Herbert Xu
2010-02-20 1:59 ` Richard Hartmann
2010-02-20 2:48 ` Herbert Xu
2010-02-20 10:26 ` Richard Hartmann
2010-02-20 13:12 ` Herbert Xu
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=2d460de71002190210qb9d5685n2fca0e7eff011b04@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=bgilbert@cs.cmu.edu \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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
all inboxes | Powered by JetHome®