From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 3/3] regmap: spi-avmm: Use swabXX_array() helpers
Date: Thu, 1 Sep 2022 00:19:22 +0300 [thread overview]
Message-ID: <Yw/QWshWH9L/+Hwp@smile.fi.intel.com> (raw)
In-Reply-To: <202209010444.n3YAkNP1-lkp@intel.com>
On Thu, Sep 01, 2022 at 04:12:01AM +0800, kernel test robot wrote:
...
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/base/
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
Indeed, I compiled only first two patches on x86.
> >> drivers/base/regmap/regmap-spi-avmm.c:171:15: error: incompatible pointer types passing 'char *' to parameter of type 'u32 *' (aka 'unsigned int *') [-Werror,-Wincompatible-pointer-types]
> swab32_array(buf, len / 4);
> ^~~
> include/linux/swab.h:32:38: note: passing argument to parameter 'buf' here
> static inline void swab32_array(u32 *buf, unsigned int words)
> ^
> 6 warnings and 1 error generated.
While error message is valid, I believe the warnings are not related to the
patch in question and were before it.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-08-31 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220831145407.78166-3-andriy.shevchenko@linux.intel.com>
2022-08-31 20:12 ` [PATCH v1 3/3] regmap: spi-avmm: Use swabXX_array() helpers kernel test robot
2022-08-31 21:19 ` Andy Shevchenko [this message]
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=Yw/QWshWH9L/+Hwp@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=rafael@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