From: Souptick Joarder <jrdr.linux@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Patrick Rudolph <patrick.rudolph@9elements.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>,
Marcello Sylvester Bauer <sylv@sylv.io>,
Naresh Solanki <Naresh.Solanki@9elements.com>
Subject: Re: [linux-next:master 7168/8914] drivers/regulator/max597x-regulator.c:24:10: fatal error: linux/mfd/max597x.h: No such file or directory
Date: Wed, 27 Jul 2022 07:11:28 +0530 [thread overview]
Message-ID: <CAFqt6zYZsYqsiACNM=ZRira0VpyXgTrzAZEvdFxGUTrrFUtQ0w@mail.gmail.com> (raw)
In-Reply-To: <202207090537.PERTk8TN-lkp@intel.com>
On Sat, Jul 9, 2022 at 3:11 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: f2528c29385819a84480cacef4886b049761e2c5
> commit: 38493f008deb435577361d4c4cdd69f7bb30f4b9 [7168/8914] regulator: max597x: Add support for max597x regulator
> config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220709/202207090537.PERTk8TN-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=38493f008deb435577361d4c4cdd69f7bb30f4b9
> 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 38493f008deb435577361d4c4cdd69f7bb30f4b9
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> Note: the linux-next/master HEAD f2528c29385819a84480cacef4886b049761e2c5 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> >> drivers/regulator/max597x-regulator.c:24:10: fatal error: linux/mfd/max597x.h: No such file or directory
> 24 | #include <linux/mfd/max597x.h>
> | ^~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
Looking into linux-next : 20220726
As part of [1] ->
[2] - not yet merged.
[3] - got merged into linux-next.
It leads to the above error.
[1] - https://www.spinics.net/lists/kernel/msg4429237.html
[2] - https://www.spinics.net/lists/kernel/msg4429235.html
[3] - https://www.spinics.net/lists/kernel/msg4429231.html
Why ? Is there any reason behind it ?
>
>
> vim +24 drivers/regulator/max597x-regulator.c
>
> 23
> > 24 #include <linux/mfd/max597x.h>
> 25
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
prev parent reply other threads:[~2022-07-27 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 21:40 kernel test robot
2022-07-27 1:41 ` Souptick Joarder [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='CAFqt6zYZsYqsiACNM=ZRira0VpyXgTrzAZEvdFxGUTrrFUtQ0w@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=Naresh.Solanki@9elements.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=patrick.rudolph@9elements.com \
--cc=sylv@sylv.io \
/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