From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>, Arnd Bergmann <arnd@arndb.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [linux-next:master 7942/12152] arch/arm/mach-pxa/balloon3.c:26:10: fatal error: 'linux/platform_data/pcf857x.h' file not found
Date: Sun, 12 Feb 2023 14:02:21 +0200 [thread overview]
Message-ID: <Y+jVTeDdREp1WMuE@smile.fi.intel.com> (raw)
In-Reply-To: <202302111818.Oiz9M6EM-lkp@intel.com>
On Sat, Feb 11, 2023 at 07:01:54PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 6ba8a227fd19d19779005fb66ad7562608e1df83
> commit: 91a0192e90e9df40d4b63c4ce11126114ed5d79d [7942/12152] gpio: pcf857x: Get rid of legacy platform data
> config: arm-randconfig-r034-20230210 (https://download.01.org/0day-ci/archive/20230211/202302111818.Oiz9M6EM-lkp@intel.com/config)
> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project db0e6591612b53910a1b366863348bdb9d7d2fb1)
> 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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=91a0192e90e9df40d4b63c4ce11126114ed5d79d
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 91a0192e90e9df40d4b63c4ce11126114ed5d79d
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202302111818.Oiz9M6EM-lkp@intel.com/
>
> Note: the linux-next/master HEAD 6ba8a227fd19d19779005fb66ad7562608e1df83 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> >> arch/arm/mach-pxa/balloon3.c:26:10: fatal error: 'linux/platform_data/pcf857x.h' file not found
> #include <linux/platform_data/pcf857x.h>
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
Another tree removes the entire balloon3 support.
I think the best if that tree either provides an immutable branch, or be merged
before the GPIO.
See d6df7df7ae5a ("ARM: pxa: remove unused board files").
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-02-12 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 11:01 kernel test robot
2023-02-12 12:02 ` 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=Y+jVTeDdREp1WMuE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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