Return-Path: <linux-scsi-owner@vger.kernel.org>
Date: 	Mon, 3 Mar 2003 17:11:16 -0800
From: Andrew Morton <akpm@digeo.com>
To: Luben Tuikov <luben@splentec.com>
Cc: hch@infradead.org, patmans@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] scsi-misc-2.5 software enqueue when can_queue reached
Message-Id: <20030303171116.0ca432a0.akpm@digeo.com>
In-Reply-To: <3E639C1E.7060000@splentec.com>
References: <20030228111924.A32018@beaverton.ibm.com>
	<20030302085728.A11407@infradead.org>
	<3E639C1E.7060000@splentec.com>
X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Mar 2003 01:15:02.0477 (UTC) FILETIME=[7B7737D0:01C2E1EB]
Sender: linux-scsi-owner@vger.kernel.org
Precedence: bulk
X-Mailing-List: 	linux-scsi@vger.kernel.org

Luben Tuikov <luben@splentec.com> wrote:
>
> > Linux codingstyle sais the && should be before the line break.
> 
> Actually there's a point to this.
> 

Sorry, but tough luck.

The advantages of everyone using the same coding style outweigh the arguable
marginal benefits of introducing local inconsistencies.

I was a braces-on-a-new-line guy for nearly 20 years, but I knuckled under
and learnt to use Linus-style for this reason.  I'm sure others can manage
this.

-