public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jing Huang <huangj@Brocade.COM>
Cc: Daniel Walker <dwalker@fifo99.com>,
	Krishna Gudipati <kgudipat@Brocade.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Ramkumar Vadivelu <rvadivel@Brocade.COM>,
	Vinodh Ravindran <vravindr@Brocade.COM>
Subject: RE: [PATCH 2/14] bfa: Brocade BFA FC SCSI driver (bfa1)
Date: Thu, 24 Sep 2009 22:28:51 +0000	[thread overview]
Message-ID: <1253831331.5183.264.camel@mulgrave.site> (raw)
In-Reply-To: <B0A7AF226B49A14897036E9B3A68CFFECB1AB0F79B@HQ-EXCH-7.corp.brocade.com>

On Thu, 2009-09-24 at 11:08 -0700, Jing Huang wrote:
> > > Hi Daniel,
> > >
> > > I did run checkpatch.pl and it didn't report any ERROR or WARNING. Do
> > you use any specific flags?
> > 
> > No nothing special .. I run it in the following way,
> > 
> > ./scripts/checkpatch.pl this-is-the-test.patch
> > 
> > or
> > 
> > cat this-is-the-test.patch | ./scripts/checkpatch.pl -
> > 
> > how did you run it? Usually it will report something like the following
> > if it finds nothing,
> > 
> > total: 0 errors, 0 warnings, XXX lines checked
> > 
> > Your patch has no obvious style problems and is ready for submission.
> > 
> > 
> > 
> > Daniel
> 
> Thanks. I found the problem. I tried the latest checkpatch in 2.6.31
> and it generates a lot of ERRORs about putting parentheses for return.
> I have been using an older version of checkpatch for patch submission
> all the time, and therefore I didn't see any problem. I will fix them
> and resubmit the patch.

Actually, could you send an incremental diff ... I'll put this in the
tree because it's about time it got wider testing in linux-next.

James



  reply	other threads:[~2009-09-24 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24  0:49 [PATCH 2/14] bfa: Brocade BFA FC SCSI driver (bfa1) Jing Huang
2009-09-24 15:44 ` Daniel Walker
2009-09-24 15:59   ` Alan Cox
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 [this message]
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=1253831331.5183.264.camel@mulgrave.site \
    --to=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