linux-kernel - Re: [PATCH 2/14] bfa: Brocade BFA FC SCSI driver (bfa1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090924165944.6507432a@lxorguk.ukuu.org.uk>
Date:	Thu, 24 Sep 2009 16:59:44 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Daniel Walker <dwalker@...o99.com>
Cc:	Jing Huang <huangj@...cade.com>,
	James.Bottomley@...senPartnership.com, kgudipat@...cade.com,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	rvadivel@...cade.com, vravindr@...cade.com
Subject: Re: [PATCH 2/14] bfa: Brocade BFA FC SCSI driver (bfa1)

> > +       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*.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/