public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Anand Kumar Santhanam <AnandKumar.Santhanam@pmcs.com>
Cc: linux-scsi@vger.kernel.org, Harry Yang <Harry.Yang@pmcs.com>,
	Vishwanath Maram <Vishwanath.Maram@pmcs.com>,
	sakthivel.sk@hcl.com, Rich Bono <Rich.Bono@pmcs.com>,
	Sangeetha Gnanasekaran <Sangeetha.Gnanasekaran@pmcs.com>
Subject: Re: [PATCH V4 2/12] pm80xx: Added SPCv/ve specific ids, variables and modify for SPC
Date: Mon, 06 May 2013 11:27:30 -0700	[thread overview]
Message-ID: <1367864850.1868.33.camel@dabdike> (raw)
In-Reply-To: <E5DEE6F468524847995699AD11E80885017C76B6@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>

On Mon, 2013-05-06 at 09:48 -0700, Anand Kumar Santhanam wrote:
> Hi James,
> 
> I have resubmitted the patchset after fixing the array out of bounds
> issue. Pls pull the same.
> 
> I guess I did not make myself clear with my earlier mail. I compiled my
> earlier patchset using the 
> Kernel Makefile and I did not get the array out of bounds warning even I
> had -Wall -O2 flags enabled.
> So I was just wondering whether you are using any special settings such
> that you are able to see the 
> warning.

Oh, OK, that's not what I read in the email, so sorry for being brusque.
What -Wall actually does is highly gcc version dependent.  What I did
was simply a standard kernel compile (no extra flags), but with
gcc-4.7.2

James



      reply	other threads:[~2013-05-06 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 18:25 [PATCH V4 2/12] pm80xx: Added SPCv/ve specific ids, variables and modify for SPC Anand
2013-05-02 22:12 ` James Bottomley
2013-05-03  2:26   ` Anand Kumar Santhanam
2013-05-03  5:59     ` James Bottomley
2013-05-06 16:48       ` Anand Kumar Santhanam
2013-05-06 18:27         ` James Bottomley [this message]

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=1367864850.1868.33.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=AnandKumar.Santhanam@pmcs.com \
    --cc=Harry.Yang@pmcs.com \
    --cc=Rich.Bono@pmcs.com \
    --cc=Sangeetha.Gnanasekaran@pmcs.com \
    --cc=Vishwanath.Maram@pmcs.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sakthivel.sk@hcl.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