From: kernel test robot <lkp@intel.com>
To: Wentong Wu <wentong.wu@intel.com>,
gregkh@linuxfoundation.org, tomas.winkler@intel.com,
hdegoede@redhat.com
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, andriy.shevchenko@linux.intel.com,
sakari.ailus@linux.intel.com, alexander.usyskin@intel.com,
zhifeng.wang@intel.com, linux-kernel@vger.kernel.org,
Wentong Wu <wentong.wu@intel.com>
Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device
Date: Wed, 29 Nov 2023 06:50:22 +0800 [thread overview]
Message-ID: <202311290342.lucjHsTH-lkp@intel.com> (raw)
In-Reply-To: <1701174846-16316-3-git-send-email-wentong.wu@intel.com>
Hi Wentong,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.7-rc3 next-20231128]
[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/Wentong-Wu/mei-Add-transport-driver-for-IVSC-device/20231128-203609
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/1701174846-16316-3-git-send-email-wentong.wu%40intel.com
patch subject: [PATCH 2/2] mei: Add MEI hardware support for IVSC device
config: x86_64-kismet-CONFIG_INTEL_MEI_VSC_HW-CONFIG_INTEL_MEI_VSC-0-0 (https://download.01.org/0day-ci/archive/20231129/202311290342.lucjHsTH-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20231129/202311290342.lucjHsTH-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/202311290342.lucjHsTH-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for INTEL_MEI_VSC_HW when selected by INTEL_MEI_VSC
WARNING: unmet direct dependencies detected for INTEL_MEI_VSC_HW
Depends on [n]: ACPI [=y] && SPI [=y] && (GPIOLIB [=n] || COMPILE_TEST [=n])
Selected by [y]:
- INTEL_MEI_VSC [=y] && INTEL_MEI [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-28 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:34 [PATCH 0/2] mei: Add support for IVSC device Wentong Wu
2023-11-28 12:34 ` [PATCH 1/2] mei: Add transport driver " Wentong Wu
2023-12-06 7:40 ` Winkler, Tomas
2023-11-28 12:34 ` [PATCH 2/2] mei: Add MEI hardware support " Wentong Wu
2023-11-28 22:50 ` kernel test robot [this message]
2023-11-29 9:26 ` Sakari Ailus
2023-11-29 10:21 ` Andy Shevchenko
2023-11-29 10:26 ` Sakari Ailus
2023-11-29 14:11 ` Wu, Wentong
2023-11-29 12:28 ` Krzysztof Kozlowski
2023-11-29 13:56 ` Wu, Wentong
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=202311290342.lucjHsTH-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fazilyildiran@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@intel.com \
--cc=zhifeng.wang@intel.com \
/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