From: kernel test robot <lkp@intel.com>
To: Rob Herring <robh@kernel.org>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/2] cdx: Enable COMPILE_TEST
Date: Sat, 9 Dec 2023 10:39:12 +0800 [thread overview]
Message-ID: <202312091016.deeonCay-lkp@intel.com> (raw)
In-Reply-To: <20231207163128.2707993-1-robh@kernel.org>
Hi Rob,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7-rc4 next-20231208]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Rob-Herring/cdx-Explicitly-include-correct-DT-includes-again/20231208-003335
base: linus/master
patch link: https://lore.kernel.org/r/20231207163128.2707993-1-robh%40kernel.org
patch subject: [PATCH 1/2] cdx: Enable COMPILE_TEST
config: m68k-kismet-CONFIG_REMOTEPROC-CONFIG_CDX_CONTROLLER-0-0 (https://download.01.org/0day-ci/archive/20231209/202312091016.deeonCay-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20231209/202312091016.deeonCay-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312091016.deeonCay-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for REMOTEPROC when selected by CDX_CONTROLLER
WARNING: unmet direct dependencies detected for REMOTEPROC
Depends on [n]: HAS_DMA [=n]
Selected by [y]:
- CDX_CONTROLLER [=y] && CDX_BUS [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-09 2:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:31 [PATCH 1/2] cdx: Enable COMPILE_TEST Rob Herring
2023-12-07 16:31 ` [PATCH 2/2] cdx: Explicitly include correct DT includes, again Rob Herring
2023-12-12 4:40 ` Agarwal, Nikhil
2023-12-09 2:39 ` kernel test robot [this message]
2023-12-12 4:40 ` [PATCH 1/2] cdx: Enable COMPILE_TEST Agarwal, Nikhil
2023-12-12 14:26 ` Rob Herring
2023-12-18 4:39 ` Agarwal, Nikhil
2023-12-15 16:09 ` Greg Kroah-Hartman
2023-12-15 16:10 ` Greg Kroah-Hartman
2023-12-21 6:42 ` Gangurde, Abhijit
2023-12-21 8:07 ` Greg Kroah-Hartman
2023-12-21 8:40 ` Gangurde, Abhijit
2023-12-21 8:46 ` Greg Kroah-Hartman
2023-12-18 4:40 ` Agarwal, Nikhil
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=202312091016.deeonCay-lkp@intel.com \
--to=lkp@intel.com \
--cc=fazilyildiran@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=robh@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 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.