linux-kernel - Re: [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB LED 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 30 Oct 2019 20:57:45 +0100
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     Dan Murphy <dmurphy@...com>, kbuild test robot <lkp@...el.com>
Cc:     kbuild-all@...ts.01.org, pavel@....cz, linux-leds@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB
 LED driver

Dan,

On 10/30/19 5:41 PM, Dan Murphy wrote:
> Hello
> 
> On 10/30/19 7:07 AM, kbuild test robot wrote:
>> Hi Dan,
>>
>> I love your patch! Yet something to improve:
>>
>> [auto build test ERROR on j.anaszewski-leds/for-next]
>> [also build test ERROR on v5.4-rc5 next-20191029]
> 
> I went to both these references and I do not see this patchset on either
> of these.

This branch is temporarily created by build bot by applying patch sets
from lists on top of linux-leds for-next branch.

>> [if your patch is applied to the wrong git tree, please drop us a note
>> to help
>> improve the system. BTW, we also suggest to use '--base' option to
>> specify the
>> base tree in git format-patch, please see
>> https://stackoverflow.com/a/37406982]
>>
>> url:   
>> https://github.com/0day-ci/linux/commits/Dan-Murphy/Multicolor-Framework/20191030-144320
>>
> It appears here though
>> base:  
>> https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git
>> for-next
> 
> 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.

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.

You need to patch your driver with the attached one.

-- 
Best regards,
Jacek Anaszewski

View attachment "fix_lp50xx_struct_initialization.patch" of type "text/x-patch" (2738 bytes)