Date: Mon, 07 May 2012 11:52:28 -0400 (EDT)
Message-Id: <20120507.115228.1171858914064928263.davem@davemloft.net> (sfid-20120507_175349_146923_ABC71B70)
To: andrei.emeltchenko.news@gmail.com
Cc: dh.herrmann@googlemail.com, gustavo@padovan.org,
	linville@tuxdriver.com, linux-bluetooth@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix coding style
From: David Miller <davem@davemloft.net>
In-Reply-To: <20120507081411.GA19002@aemeltch-MOBL1>
References: <CANq1E4TTfDxZPsOqqWUT7PqTKUr8nCTC-wo=iGe_pxoUmnecgQ@mail.gmail.com>
	<20120506.145304.1998242927519675381.davem@davemloft.net>
	<20120507081411.GA19002@aemeltch-MOBL1>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Sender: linux-wireless-owner@vger.kernel.org

From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
Date: Mon, 7 May 2012 11:14:13 +0300

> If you think that Documentation/CodingStyle is a crap why don't you send a
> patch to fix it?

The same reason I don't go try and fix broken networking RFCs.

Documents are never are the final verdict on anything, there will
always be areas where such documents are wrong and common sense should
prevail.

If you take them %100 of the time on face value, and use them as an
opportunity to turn your brain completely off, that's your problem.

And it's amusing that you ask me to fix the document.  You're
unwillingness to go look at other core areas of the kernel and see
what they do there is just an evasive act rather than an attempt to
understand the point I'm trying to make.