[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1466894.mfHmYdoaGJ@wuerfel>
Date: Thu, 04 Feb 2016 16:10:32 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Andrzej Hajda <a.hajda@...sung.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
open list <linux-kernel@...r.kernel.org>,
Bob Peterson <rpeterso@...hat.com>
Subject: Re: [PATCH v3] err.h: allow IS_ERR_VALUE to handle properly more types
On Thursday 04 February 2016 16:00:09 Arnd Bergmann wrote:
> With the IS_ERR_VALUE() macro I sent, I don't see the warning on any gcc
> version. I have now also checked that the behavior on x86 gcc-.4.9 is the
> same that I see on ARM (I don't have a large collection of x86 gcc versions
> though): same warning with linux-next, no warning with my version or after
> reverting your patch.
>
Sorry, scratch that: I don't get this warning at all on x86 with gcc-4.9,
with any version of err.h.
Arnd
Powered by blists - more mailing lists