From: Richard Yao <ryao@gentoo.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org, linux-scsi@vger.kernel.org,
James Smart <james.smart@emulex.com>
Subject: Re: scsi: lpfc_scsi: Remove unused variables
Date: Thu, 07 Jun 2012 02:21:08 -0400 [thread overview]
Message-ID: <4FD04854.5010304@gentoo.org> (raw)
In-Reply-To: <20120607061255.GB3210@burratino>
On 06/07/12 02:12, Jonathan Nieder wrote:
> Hi Richard,
>
> Richard Yao wrote:
>
>> This is my first time patch submission. The commit message should
>> explain the issue.
>>
>> commit ba8c7a7a629b736fdc1abceaa3ec49f8820aec08
>> Author: Richard Yao <ryao@cs.stonybrook.edu>
>> Date: Thu Jun 7 01:44:31 2012 -0400
>>
>> scsi: lpfc_scsi: Remove unused variables
>>
>> Kernels built with CONFIG_SCSI_LPFC fail to compile due to the use of
>> -Werror=unused-variable. We solve that by removing some unused
>> variables.
> Wouldn't a saner fix be to stop using -Werror=unused-variable, or am I
> missing something subtle?
>
> (Since v3.4-rc1~6^2~48 the makefile seems to use plain -Werror, which
> seems even worse, since it means any random compiler bug that triggers
> a new warning will break the build.)
>
> Thanks and hope that helps,
> Jonathan
Using -Werror enables us to catch potential runtime issues before they
happen. This one is not a runtime issue, but the compiler is right in
stating that these variables serve no purpose. My opinion is that
occasional noise due to -Werror won't be a problem. Also, decisions on
-Werror probably should be made by either the subsystem maintainer or
the branch maintainer.
next prev parent reply other threads:[~2012-06-07 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FD0434B.7090405@gentoo.org>
2012-06-07 6:12 ` scsi: lpfc_scsi: Remove unused variables Jonathan Nieder
2012-06-07 6:21 ` Richard Yao [this message]
2012-06-07 6:42 ` Jonathan Nieder
2012-06-11 14:02 ` James Smart
2012-06-07 6:37 ` Greg KH
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=4FD04854.5010304@gentoo.org \
--to=ryao@gentoo.org \
--cc=james.smart@emulex.com \
--cc=jrnieder@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.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.