From: Hans de Goede <hdegoede@redhat.com>
To: kernel test robot <lkp@intel.com>,
Lee Jones <lee.jones@linaro.org>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, kbuild-all@lists.01.org,
Christian Hartmann <cornogle@googlemail.com>,
patches@opensource.cirrus.com,
clang-built-linux@googlegroups.com,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH v2 3/5] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI
Date: Sun, 17 Jan 2021 21:20:36 +0100 [thread overview]
Message-ID: <128c932f-d2b6-c9f6-dc67-585244a39d7a@redhat.com> (raw)
In-Reply-To: <202101180352.D075IBWE-lkp@intel.com>
Hi,
On 1/17/21 8:06 PM, kernel test robot wrote:
> Hi Hans,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on lee-mfd/for-mfd-next]
> [also build test ERROR on asoc/for-next v5.11-rc3 next-20210115]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
>
> url: https://github.com/0day-ci/linux/commits/Hans-de-Goede/MFD-ASoC-Add-support-for-Intel-Bay-Trail-boards-with-WM5102-codec/20210117-235249
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
> config: arm-randconfig-r021-20210118 (attached as .config)
> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project bfd75bdf3fd62d4f5e7028d4122f9ffa517f2a09)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install arm cross compiling tool for clang build
> # apt-get install binutils-arm-linux-gnueabi
> # https://github.com/0day-ci/linux/commit/ff3c43e0ca3dd07a3b671ee3be84b9c607dff305
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Hans-de-Goede/MFD-ASoC-Add-support-for-Intel-Bay-Trail-boards-with-WM5102-codec/20210117-235249
> git checkout ff3c43e0ca3dd07a3b671ee3be84b9c607dff305
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> drivers/mfd/arizona-spi.c:194:7: error: assigning to 'int' from incompatible type 'void'
> ret = arizona_spi_acpi_probe(arizona);> ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
UGh, the test-robot gave the same errors for v1 of this patch-set; and I checked,
but I could not find the problem. Since there was some time between v1 and v2
I assumed that I had already fixed this in my local tree, but I now see that
this is caused by a bug in the #else block of the
#ifdef CONFIG_ACPI
#else
#endif
in this patch. I will submit a v3 of this patch-set fixing this.
Regards,
Hans
WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 3/5] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI
Date: Sun, 17 Jan 2021 21:20:36 +0100 [thread overview]
Message-ID: <128c932f-d2b6-c9f6-dc67-585244a39d7a@redhat.com> (raw)
In-Reply-To: <202101180352.D075IBWE-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
Hi,
On 1/17/21 8:06 PM, kernel test robot wrote:
> Hi Hans,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on lee-mfd/for-mfd-next]
> [also build test ERROR on asoc/for-next v5.11-rc3 next-20210115]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
>
> url: https://github.com/0day-ci/linux/commits/Hans-de-Goede/MFD-ASoC-Add-support-for-Intel-Bay-Trail-boards-with-WM5102-codec/20210117-235249
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
> config: arm-randconfig-r021-20210118 (attached as .config)
> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project bfd75bdf3fd62d4f5e7028d4122f9ffa517f2a09)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install arm cross compiling tool for clang build
> # apt-get install binutils-arm-linux-gnueabi
> # https://github.com/0day-ci/linux/commit/ff3c43e0ca3dd07a3b671ee3be84b9c607dff305
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Hans-de-Goede/MFD-ASoC-Add-support-for-Intel-Bay-Trail-boards-with-WM5102-codec/20210117-235249
> git checkout ff3c43e0ca3dd07a3b671ee3be84b9c607dff305
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> drivers/mfd/arizona-spi.c:194:7: error: assigning to 'int' from incompatible type 'void'
> ret = arizona_spi_acpi_probe(arizona);> ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
UGh, the test-robot gave the same errors for v1 of this patch-set; and I checked,
but I could not find the problem. Since there was some time between v1 and v2
I assumed that I had already fixed this in my local tree, but I now see that
this is caused by a bug in the #else block of the
#ifdef CONFIG_ACPI
#else
#endif
in this patch. I will submit a v3 of this patch-set fixing this.
Regards,
Hans
next prev parent reply other threads:[~2021-01-17 20:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 15:47 [PATCH v2 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Hans de Goede
2021-01-17 15:47 ` Hans de Goede
2021-01-17 15:47 ` [PATCH v2 1/5] mfd: arizona: Add MODULE_SOFTDEP("pre: arizona_ldo1") Hans de Goede
2021-01-17 15:47 ` Hans de Goede
2021-01-17 15:47 ` [PATCH v2 2/5] mfd: arizona: Replace arizona_of_get_type() with device_get_match_data() Hans de Goede
2021-01-17 15:47 ` Hans de Goede
2021-01-17 15:47 ` [PATCH v2 3/5] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI Hans de Goede
2021-01-17 15:47 ` Hans de Goede
2021-01-17 19:06 ` kernel test robot
2021-01-17 19:06 ` kernel test robot
2021-01-17 20:20 ` Hans de Goede [this message]
2021-01-17 20:20 ` Hans de Goede
2021-01-17 20:07 ` kernel test robot
2021-01-17 20:07 ` kernel test robot
2021-01-17 15:47 ` [PATCH v2 4/5] ASoC: Intel: Add DMI quirk table to soc_intel_is_byt_cr() Hans de Goede
2021-01-17 15:47 ` Hans de Goede
2021-01-17 15:47 ` [PATCH v2 5/5] ASoC: Intel: bytcr_wm5102: Add machine driver for BYT/WM5102 Hans de Goede
2021-01-17 15:47 ` Hans de Goede
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=128c932f-d2b6-c9f6-dc67-585244a39d7a@redhat.com \
--to=hdegoede@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=clang-built-linux@googlegroups.com \
--cc=cornogle@googlemail.com \
--cc=kbuild-all@lists.01.org \
--cc=lee.jones@linaro.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=lkp@intel.com \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@linux.intel.com \
/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.