linux-kernel - Re: [PATCH v2] thermal: Add QPNP PMIC temperature alarm driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1412163388.26751.39.camel@iivanov-dev>
Date:	Wed, 01 Oct 2014 14:36:28 +0300
From:	"Ivan T. Ivanov" <iivanov@...sol.com>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Kiran Padwal <kiran.padwal@...rtplayin.com>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Grant Likely <grant.likely@...aro.org>,
	Zhang Rui <rui.zhang@...el.com>,
	Eduardo Valentin <edubezval@...il.com>,
	linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	David Collins <collinsd@...eaurora.org>
Subject: Re: [PATCH v2] thermal: Add QPNP PMIC temperature alarm driver

On Tue, 2014-09-30 at 12:46 -0700, Stephen Boyd wrote:
> On 09/30/14 00:36, Ivan T. Ivanov wrote:
> > On Tue, 2014-09-30 at 10:00 +0530, Kiran Padwal wrote:
> >>
> >> I have Linaro cross tool chain with version-4.8.3 and I am simply doing "make zImage" without any option.
> > Hm, no warnings with arm-unknown-linux-gnueabi-gcc (GCC) 4.6.3 and
> > arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-4.9-2014.09, but
> > indeed arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-4.8-2014.03.
> >
> > I will say that this is false positive :-). Please update your tool-chain.
> 
> Hopefully you're joking. Once this merges someone will find the warning
> and complain. Telling them to upgrade their compiler isn't going to work.

If it is known to be buggy why not?

> 
> I wonder if checking for rc != 0 instead of rc < 0 would silence the
> warning? 

No. Anyway, will find some way to silence this warning.

Thanks,
Ivan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/