mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Jens Axboe <axboe@kernel.dk>,
	"James E.J. Bottomley" <James.Bottomley@SteelEye.com>,
	Alessandro Rubini <rubini@vision.unipv.it>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	Geoff Levand <geoffrey.levand@am.sony.com>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [patch 1/3] ps3: Disk Storage Driver
Date: Wed, 25 Jul 2007 11:09:21 +1000	[thread overview]
Message-ID: <18086.41665.610756.139183@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <46A5E610.7000508@shadowen.org>

Andy Whitcroft writes:

> Ok, this is something we need to decide on.  Currently we only ask for
> consistent spacing on all the mathematic operators.  This is mostly as
> we do see a large number of non-spaced uses in defines and the like.
> 
> I am happy to expand these tests so they are always spaced on both sides
> style if that is the preference.

It depends very much on the context - on the precedence and relative
importance of one operator with respect to other operators and the
statement as a whole.  In general I prefer spaces around binary
operators, but there are situations where not putting spaces around
some operators can enhance the readability of the statement as a
whole.

If checkpatch.pl starts whinging about operators without spaces that
will just be yet another reason not to use it IMHO.

Also, I prefer the style where the ? and : operators have a space
after them but not before them, rather than a space either side.

Paul.

  parent reply	other threads:[~2007-07-25  1:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 16:15 [patch 0/3] PS3 Storage Drivers for 2.6.23, take 5 Geert Uytterhoeven
2007-07-16 16:15 ` [patch 1/3] ps3: Disk Storage Driver Geert Uytterhoeven
2007-07-18 14:32   ` Jan Engelhardt
2007-07-18 15:36     ` Geert Uytterhoeven
2007-07-18 23:36   ` Andrew Morton
2007-07-19  5:33     ` Jens Axboe
2007-07-19  7:15       ` Geert Uytterhoeven
2007-07-19  8:57     ` Geert Uytterhoeven
2007-07-19  9:10       ` Andrew Morton
2007-07-19 13:52         ` [patch 0/4] PS3 storage driver updates (was: Re: [patch 1/3] ps3: Disk Storage Driver) Geert Uytterhoeven
2007-07-19 13:53           ` [patch 1/4] ps3disk: use correct bio vector size Geert Uytterhoeven
2007-07-19 13:54           ` [patch 2/4] ps3disk: updates after final review Geert Uytterhoeven
2007-07-19 13:54           ` [patch 3/4] ps3rom: " Geert Uytterhoeven
2007-07-19 13:55           ` [patch 4/4] ps3flash: " Geert Uytterhoeven
2007-07-19  9:26       ` [patch 1/3] ps3: Disk Storage Driver Cornelia Huck
2007-07-19  9:36         ` Geert Uytterhoeven
2007-07-19 12:00           ` Cornelia Huck
2007-07-19 12:13             ` Geert Uytterhoeven
2007-07-19 12:52               ` Cornelia Huck
2007-07-24 11:44     ` Andy Whitcroft
2007-07-24 12:37       ` Jeff Garzik
2007-07-24 12:52         ` Andreas Schwab
2007-07-24 13:44           ` Jeff Garzik
2007-07-24 16:43         ` Andrew Morton
2007-07-25  1:09       ` Paul Mackerras [this message]
2007-07-25  1:21         ` Andrew Morton
2007-07-16 16:15 ` [patch 2/3] ps3: BD/DVD/CD-ROM " Geert Uytterhoeven
2007-07-18 23:43   ` Andrew Morton
2007-07-19  9:02     ` Geert Uytterhoeven
2007-07-19  9:17       ` Andrew Morton
2007-07-19  9:39         ` Geert Uytterhoeven
2007-07-19  9:41           ` Jens Axboe
2007-07-19  9:47           ` Andrew Morton
2007-07-19 17:56             ` Rene Herman
2007-07-16 16:15 ` [patch 3/3] ps3: FLASH ROM " Geert Uytterhoeven
2007-07-18 23:52   ` Andrew Morton
2007-07-19 11:25     ` Geert Uytterhoeven
2007-07-19  6:40 ` [patch 0/3] PS3 Storage Drivers for 2.6.23, take 5 Alessandro Rubini

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=18086.41665.610756.139183@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=axboe@kernel.dk \
    --cc=geoffrey.levand@am.sony.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rubini@vision.unipv.it \
    /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®