Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Vineet Gupta <vineet.gupta1@synopsys.com>
To:     Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
        "linux-snps-arc@lists.infradead.org" 
        <linux-snps-arc@lists.infradead.org>
CC:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "Alexey Brodkin" <alexey.brodkin@synopsys.com>
Subject: Re: [PATCH] ARC: fix __ffs return value to avoid build warnings
Thread-Topic: [PATCH] ARC: fix __ffs return value to avoid build warnings
Thread-Index: AQHUkvqJxXSvGyNzLkuvtcEIj0Ff0w==
Date:   Thu, 13 Dec 2018 18:23:18 +0000
Message-ID: <C2D7FE5348E1B147BCA15975FBA23075014641F6E3@US01WEMBX2.internal.synopsys.com>
References: <20181213154257.23033-1-Eugeniy.Paltsev@synopsys.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 12/13/18 7:43 AM, Eugeniy Paltsev wrote:=0A=
> Change __ffs return value from 'int' to 'unsigned long' as it=0A=
> is done in other implementations (like asm-generic, x86, etc...)=0A=
> to avoid build-time warnings in places where type is strictly=0A=
> checked.=0A=
>=0A=
> As __ffs may return values in [0-31] interval changing return=0A=
> type to unsigned is valid.=0A=
>=0A=
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>=0A=
=0A=
Can you please paste a couple of lines of offending output !=0A=
=0A=
-Vineet=0A=