From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S966040AbcBDPKp (ORCPT <rfc822;w@1wt.eu>);
	Thu, 4 Feb 2016 10:10:45 -0500
Received: from mout.kundenserver.de ([212.227.126.134]:53318 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S965655AbcBDPKn (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 4 Feb 2016 10:10:43 -0500
From: Arnd Bergmann <arnd@arndb.de>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        Marek Szyprowski <m.szyprowski@samsung.com>,
        open list <linux-kernel@vger.kernel.org>,
        Bob Peterson <rpeterso@redhat.com>
Subject: Re: [PATCH v3] err.h: allow IS_ERR_VALUE to handle properly more types
Date: Thu, 04 Feb 2016 16:10:32 +0100
Message-ID: <1466894.mfHmYdoaGJ@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <2230609.SaGfiizDHl@wuerfel>
References: <20160202163350.f7d42f4b97f48756f3900e9a@linux-foundation.org> <56B363E3.9050007@samsung.com> <2230609.SaGfiizDHl@wuerfel>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:k46YUmuwrC8RU8fjcJ1RbEbbUOBDdIta/UoIy8AGJN8zfGRmow0
 JmlebYVXEw5cWpiHUk7O02NavAcxO1S8I7dIi0A82e9lMzsIj2pbVX0IjXEzFrfgEGsSC5F
 TonocY1XV5+PxymiRpjIs2iJtrh3THqHzfmaQPEC8NxMHgeDOUzf/FFZc9aWY3aODAJx6+q
 rI0p/rFjWj3m2eETNMcoA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:UX/kIfzTbak=:DChzUMi/VAWM/fh4kE24xf
 9SDvE3+8NLWGJJdGYDn0bEnjvMYjCArmIUUye6x8i3ibFAhyEEH39up+pjXaLY7XA1sNDv07x
 KzLN0BjAG8/c5XcjfE/DTw20Xo5PuhNaLGElNll0V+T0NcmFE+/UfbJnMHtkP8cH1aBXk1mJa
 zOVxnax7gKBXOZOFzngQHiHPzLpA2ubYm7K4FI8M8azJLpUmjIwQaPuVsjVLaULAk8CIBqRl7
 QAYtuEc29ZGeoXYoOfqje3f6DscRt/+hR4mnVqj8ryFvq1ODYQ4R7boLAfqBui44Z/vhHEFTp
 r0BkhN8N2m0vLNX0BDL6vTQyjr5BpGkiZ+P6lN9wGUx6TZ9pNHx73Jw14Guw+YqNNX39anBT2
 vrQ7nuHjLad37Y4IyHl/yNtBK3hmx2spvFjMdXOK4CxZOwZnB0jimOj+zNI2tAdswD0X1tES+
 +RCDUvk+SCOFsSPFwhnnVGpO0jxMHTyZqkKPkD1xpLaCJdUB0Z7N93ViVjWuQh2/hJVHT89XS
 7VBE13az+NM9GcxhhGtmBgAEfkj8y1eIY53aCbdc+QpR+BEx+nENLZEb+mK8UdjvG2nR6azkV
 oSy7eskKqC+JtohLOyvT8RCkhzGF7QzOympaD0Ae2pW8juNH4IzqJwEv0jj7d9ecJbLR8oGeY
 EGTPOKtjzKTRTp6Ia4CFztiJPgEIVsUj03dCmzmSISH4GNq4IuAZUetM1zDlaLRbeTHkwmjQo
 1HIWHyISNerr1lpL
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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