From: Hans de Goede <hdegoede@redhat.com>
To: kernel test robot <lkp@intel.com>, Sebastian Reichel <sre@kernel.org>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
Andrejus Basovas <cpp@gcc.lt>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 08/10] power: supply: axp288_fuel_gauge: Refresh all registers in one go
Date: Fri, 30 Jul 2021 10:48:45 +0200 [thread overview]
Message-ID: <3c016b6e-4f3c-3b23-01b1-c314dc1cf758@redhat.com> (raw)
In-Reply-To: <202107190341.gWNWWfOy-lkp@intel.com>
Hi,
On 7/18/21 9:52 PM, kernel test robot wrote:
> Hi Hans,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on power-supply/for-next]
> [also build test ERROR on v5.14-rc1 next-20210716]
> [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/power-supply-axp288_fuel_gauge-Reduce-number-of-register-accesses-cleanups/20210718-092951
> base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
> config: s390-buildonly-randconfig-r005-20210718 (attached as .config)
> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 5d5b08761f944d5b9822d582378333cc4b36a0a7)
<snip>
>>> drivers/power/supply/axp288_fuel_gauge.c:24:10: fatal error: 'asm/iosf_mbi.h' file not found
> #include <asm/iosf_mbi.h>
> ^~~~~~~~~~~~~~~~
> 12 warnings and 1 error generated.
Ah yes, asm.iosf_mbi.h is a X86 header file. The AXP288 is only used on X86 devices,
so we can easily fix this by adding a "depends on X86" to the Kconfig, I'll submit
a v2 which does this.
Regards,
Hans
next prev parent reply other threads:[~2021-07-30 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 16:44 [PATCH 00/10] power: supply: axp288_fuel_gauge: Reduce number of register accesses + cleanups Hans de Goede
2021-07-17 16:44 ` [PATCH 01/10] power: supply: axp288_fuel_gauge: Fix define alignment Hans de Goede
2021-07-17 16:44 ` [PATCH 02/10] power: supply: axp288_fuel_gauge: Remove debugfs support Hans de Goede
2021-07-17 16:44 ` [PATCH 03/10] power: supply: axp288_fuel_gauge: Silence the chatty IRQ mapping code Hans de Goede
2021-07-17 16:44 ` [PATCH 04/10] power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors Hans de Goede
2021-07-17 16:44 ` [PATCH 05/10] power: supply: axp288_fuel_gauge: Drop retry logic from fuel_gauge_reg_readb() Hans de Goede
2021-07-17 16:44 ` [PATCH 06/10] power: supply: axp288_fuel_gauge: Store struct device pointer in axp288_fg_info Hans de Goede
2021-07-17 16:44 ` [PATCH 07/10] power: supply: axp288_fuel_gauge: Only read PWR_OP_MODE, FG_LOW_CAP_REG regs once Hans de Goede
2021-07-17 16:44 ` [PATCH 08/10] power: supply: axp288_fuel_gauge: Refresh all registers in one go Hans de Goede
2021-07-18 19:52 ` kernel test robot
2021-07-30 8:48 ` Hans de Goede [this message]
2021-07-17 16:44 ` [PATCH 09/10] power: supply: axp288_fuel_gauge: Move the AXP20X_CC_CTRL check together with the other checks Hans de Goede
2021-07-17 16:44 ` [PATCH 10/10] power: supply: axp288_fuel_gauge: Take the P-Unit semaphore only once during probe() 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=3c016b6e-4f3c-3b23-01b1-c314dc1cf758@redhat.com \
--to=hdegoede@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=cpp@gcc.lt \
--cc=kbuild-all@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sre@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).