mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Jing Huang <huangj@brocade.com>,
	James.Bottomley@HansenPartnership.com, kgudipat@brocade.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	rvadivel@brocade.com, vravindr@brocade.com
Subject: Re: [PATCH 2/14] bfa: Brocade BFA FC SCSI driver (bfa1)
Date: Thu, 24 Sep 2009 16:59:44 +0100	[thread overview]
Message-ID: <20090924165944.6507432a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1253807042.20648.188.camel@desktop>

> > +       return (*(union bfi_addr_u *) &addr);
> > +}
> 
> Have you run checkpatch on this code? It produces many errors due to
> your "return" usage for one.. The usual style of return is not to use
> parentheses since it's really not a function ..

checkpatch is just a helper tool - and stuff like that using
brackets to make it clearer is just a trivial matter of style.

> Checkpatch produces many other errors in your code .. If you haven't
> already evaluated those errors

It would be rather more useful if instead of parroting checkpatch results
(which people can generate themselves) you concentrated on analysis the
actual code and structure for any flaws and design details.

Trivia like coding style (unless particularly bad) are something for the
maintainer just to say "fix those odd bits up and I'll merge it" at the
*end*.


  reply	other threads:[~2009-09-24 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24  0:49 Jing Huang
2009-09-24 15:44 ` Daniel Walker
2009-09-24 15:59   ` Alan Cox [this message]
2009-09-24 16:15     ` Daniel Walker
2009-09-24 17:38   ` Jing Huang
2009-09-24 17:55     ` Daniel Walker
2009-09-24 18:08       ` Jing Huang
2009-09-24 22:28         ` James Bottomley
2009-09-24 22:33           ` Jing Huang

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=20090924165944.6507432a@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dwalker@fifo99.com \
    --cc=huangj@brocade.com \
    --cc=kgudipat@brocade.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rvadivel@brocade.com \
    --cc=vravindr@brocade.com \
    /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®