From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Vincent Stehlé" <v-stehle@ti.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] regmap: debugfs: Fix compilation warning
Date: Tue, 22 Jan 2013 15:41:23 +0900 [thread overview]
Message-ID: <20130122064121.GC1766@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1358779015-25735-1-git-send-email-v-stehle@ti.com>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Mon, Jan 21, 2013 at 03:36:55PM +0100, Vincent Stehlé wrote:
> This fixes the following compilation warning:
> - unsigned int i, ret;
> + unsigned int i, ret = 0;
This sort of fix is not a good idea, you're just shutting the warning up
without any sort of analysis explaining why it's generated in error. If
it's generating a spurious error that's a compiler bug.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2013-01-22 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1358779015-25735-1-git-send-email-v-stehle@ti.com>
2013-01-22 6:41 ` Mark Brown [this message]
2013-01-22 10:07 ` [PATCH] regmap: debugfs: Fix compilation warning Vincent Stehlé
2013-01-23 15:58 ` Mark Brown
2013-01-24 10:12 ` Vincent Stehlé
2013-01-26 10:02 ` Mark Brown
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=20130122064121.GC1766@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=v-stehle@ti.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 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.