All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joe Perches <joe@perches.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jarod Wilson <jarod@redhat.com>
Subject: Re: drivers: Probable misuses of ||
Date: Mon, 7 May 2012 17:34:01 +0100	[thread overview]
Message-ID: <20120507163400.GL17002@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336407634.18931.5.camel@joe2Laptop>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Mon, May 07, 2012 at 09:20:34AM -0700, Joe Perches wrote:
> On Mon, 2012-05-07 at 09:36 +0100, Mark Brown wrote:

> > with no analysis 

> You did elide the "Likely the || should be &&" preface.

By analysis I meant something like "...because X".

> > Compare this with the reports from people like Julia Lawall, for example
> > - they tend to be very clear.  Even simply adding "...as with || they
> > will always be true" would've helped.

> I think it's a pretty basic logic error that most all
> lkml readers should be able to identify most of the time.

"Can spot" and "will spot" are two different things; speaking as someone
on the receiving end of lots of mails it does make a big difference.
Cues in the human written text which show someone thought about the
problem help a lot with catching attention - the more effort it takes to
understand a mail the more likely it is to get skipped, especially if
there's no patch.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-07 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 23:00 drivers: Probable misuses of || Joe Perches
2012-05-04 21:54 ` Joe Perches
2012-05-04 22:02   ` Mark Brown
2012-05-04 22:09     ` Joe Perches
2012-05-04 22:13       ` Mark Brown
2012-05-05 16:00         ` Guenter Roeck
2012-05-07  8:36           ` Mark Brown
2012-05-07 16:20             ` Joe Perches
2012-05-07 16:34               ` Mark Brown [this message]
2012-05-04 22:56   ` Alan Cox
2012-05-04 23:13     ` Joe Perches
2012-05-04 22:45 ` richard -rw- weinberger
2012-05-07 10:45 ` Mauro Carvalho Chehab
2012-05-07 15:22   ` [PATCH] re: drivers: Probable misuses of || - it913x.c Malcolm Priestley
2012-05-07 11:04 ` drivers: Probable misuses of || Mauro Carvalho Chehab

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=20120507163400.GL17002@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=JBottomley@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=guenter.roeck@ericsson.com \
    --cc=jarod@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.