From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Vincent Stehlé" <v-stehle@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: debugfs: Fix compilation warning
Date: Sat, 26 Jan 2013 18:02:06 +0800 [thread overview]
Message-ID: <20130126100205.GJ30594@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <51010908.5090105@ti.com>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Thu, Jan 24, 2013 at 11:12:24AM +0100, Vincent Stehlé wrote:
> If you mean "am I sure the loop iterates at least once", then yes, as
> we have an explicit check just before the concerned list_for_each_entry():
So, I hadn't realised this was triggered by a new compiler version -
Arnd just tried the same bodge. I've committed a workaround for the
compiler which avoids the problems that setting 0 will have and allows
the flow analyis to run where it can.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-26 10:02 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 ` [PATCH] regmap: debugfs: Fix compilation warning Mark Brown
2013-01-22 10:07 ` Vincent Stehlé
2013-01-23 15:58 ` Mark Brown
2013-01-24 10:12 ` Vincent Stehlé
2013-01-26 10:02 ` Mark Brown [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=20130126100205.GJ30594@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox