From: Dan Murphy <dmurphy@ti.com>
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>
Subject: Re: [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB LED driver
Date: Wed, 30 Oct 2019 15:23:09 -0500 [thread overview]
Message-ID: <f32e2063-3c56-607c-0e74-f75f68e62e16@ti.com> (raw)
In-Reply-To: <075c9330-a9b5-1360-4447-71a4797553a9@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB LED driver
Date: Wed, 30 Oct 2019 15:23:09 -0500 [thread overview]
Message-ID: <f32e2063-3c56-607c-0e74-f75f68e62e16@ti.com> (raw)
In-Reply-To: <075c9330-a9b5-1360-4447-71a4797553a9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
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
next prev parent reply other threads:[~2019-10-30 20:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 18:36 [PATCH v15 00/19] Multicolor Framework Dan Murphy
2019-10-28 18:36 ` [PATCH v15 01/19] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2019-10-28 18:36 ` [PATCH v15 02/19] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy
2019-10-28 18:36 ` [PATCH v15 03/19] " Dan Murphy
2019-10-28 18:36 ` [PATCH v15 04/19] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2019-10-28 19:22 ` Jacek Anaszewski
2019-10-28 19:36 ` Dan Murphy
2019-10-28 20:04 ` Jacek Anaszewski
2019-10-28 18:36 ` [PATCH v15 05/19] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2019-10-28 18:36 ` [PATCH v15 06/19] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2019-10-30 12:07 ` kbuild test robot
2019-10-30 12:07 ` kbuild test robot
2019-10-30 16:41 ` Dan Murphy
2019-10-30 16:41 ` Dan Murphy
2019-10-30 19:57 ` Jacek Anaszewski
2019-10-30 20:23 ` Dan Murphy [this message]
2019-10-30 20:23 ` Dan Murphy
2019-10-30 20:50 ` Jacek Anaszewski
2019-10-30 20:55 ` Dan Murphy
2019-10-30 20:55 ` Dan Murphy
2019-10-30 22:00 ` Jacek Anaszewski
2019-10-30 22:03 ` Jacek Anaszewski
2019-10-30 16:43 ` Dan Murphy
2019-10-30 16:43 ` Dan Murphy
2019-11-25 15:07 ` Pavel Machek
2019-11-25 15:07 ` Pavel Machek
2019-12-04 12:44 ` Dan Murphy
2019-12-04 12:44 ` Dan Murphy
2019-12-05 9:54 ` [kbuild-all] " Rong Chen
2019-12-05 9:54 ` Rong Chen
2020-02-09 22:47 ` [kbuild-all] " Pavel Machek
2020-02-09 22:47 ` Pavel Machek
2019-10-28 18:36 ` [PATCH v15 07/19] dt: bindings: lp55xx: Be consistent in the document with LED acronym Dan Murphy
2019-10-28 18:36 ` [PATCH v15 08/19] dt: bindings: lp55xx: Update binding for Multicolor Framework Dan Murphy
2019-10-28 18:36 ` [PATCH v15 09/19] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2019-10-28 18:36 ` [PATCH v15 10/19] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2019-10-28 18:36 ` [PATCH v15 11/19] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes Dan Murphy
2019-10-28 18:36 ` [PATCH v15 12/19] leds: lp55xx: Convert LED class registration to devm_* Dan Murphy
2019-10-28 18:36 ` [PATCH v15 13/19] leds: lp55xx: Add multicolor framework support to lp55xx Dan Murphy
2019-10-28 18:36 ` [PATCH v15 14/19] leds: lp5523: Update the lp5523 code to add multicolor brightness function Dan Murphy
2019-10-28 18:36 ` [PATCH v15 15/19] leds: lp5521: Add multicolor framework multicolor brightness support Dan Murphy
2019-10-28 18:36 ` [PATCH v15 16/19] leds: lp55xx: Fix checkpatch file permissions issues Dan Murphy
2019-10-28 18:36 ` [PATCH v15 17/19] leds: lp5523: Fix checkpatch issues in the code Dan Murphy
2019-10-28 18:36 ` [PATCH v15 18/19] dt: bindings: Update lp55xx binding to recommended LED naming Dan Murphy
2019-10-28 18:36 ` [PATCH v15 19/19] leds: lp55xx-common: Remove extern from lp55xx-common header Dan Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f32e2063-3c56-607c-0e74-f75f68e62e16@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.