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;
Subject: Re: [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB
 LED driver
To:     Jacek Anaszewski <jacek.anaszewski@gmail.com>,
        kbuild test robot <lkp@intel.com>
CC:     <kbuild-all@lists.01.org>, <pavel@ucw.cz>,
        <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>
References: <20191028183629.11779-7-dmurphy@ti.com>
 <201910302027.2hNdR993%lkp@intel.com>
 <bb3473ba-ddfc-2b51-4a75-c23c5bf3bc62@ti.com>
 <075c9330-a9b5-1360-4447-71a4797553a9@gmail.com>
From:   Dan Murphy <dmurphy@ti.com>
Message-ID: <f32e2063-3c56-607c-0e74-f75f68e62e16@ti.com>
Date:   Wed, 30 Oct 2019 15:23:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <075c9330-a9b5-1360-4447-71a4797553a9@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Jacek


>> Does not appear here
>>
>> Finally not sure why the MIPS compiler is complaining about this but the
>> ARM and x86 is not
> Compilation breaks also for ARM.

Thanks for the information.

I am not seeing this issue or even a warning when using the ARM 8.3 
toolchain even in a clean build.

arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 
8.3-2019.03 (arm-rel-8.36)) 8.3.0

So is a bug in this toolchain?

> This is not architecture specific but language specific thing.
>
> If you enter this error message got Google you will get an answer
> to why this happens in the first result.

I did Google the issue and got the answer I guess I just question to why 
I am not seeing the error because for me the patchset builds fine no errors.

And why is this only reported on the MIPS arch.? Not saying that it is 
not an issue in the code just wondering how it gets there.

>
> You need to patch your driver with the attached one.
>
I will try to reproduce the error and then apply the changes.

Dan