mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mingyou Chen <qby140326@gmail.com>,
	hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, cryolitia.pukngae@linux.dev,
	Mingyou Chen <qby140326@gmail.com>
Subject: Re: [PATCH v3] platform/x86: tongfang-mifs-wmi: Add new Tongfang MIFS WMI driver
Date: Sun, 25 Jan 2026 14:18:57 +0100	[thread overview]
Message-ID: <202601251425.LsolyF4U-lkp@intel.com> (raw)
In-Reply-To: <20260125071501.12616-1-qby140326@gmail.com>

Hi Mingyou,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on next-20260123]
[cannot apply to v6.16-rc1]
[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/Mingyou-Chen/platform-x86-tongfang-mifs-wmi-Add-new-Tongfang-MIFS-WMI-driver/20260125-151740
base:   linus/master
patch link:    https://lore.kernel.org/r/20260125071501.12616-1-qby140326%40gmail.com
patch subject: [PATCH v3] platform/x86: tongfang-mifs-wmi: Add new Tongfang MIFS WMI driver
reproduce: (https://download.01.org/0day-ci/archive/20260125/202601251425.LsolyF4U-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/202601251425.LsolyF4U-lkp@intel.com/

All warnings (new ones prefixed by >>):

   ERROR: Cannot find file ./include/linux/mutex.h
   ERROR: Cannot find file ./include/linux/mutex.h
   WARNING: No kernel-doc for file ./include/linux/mutex.h
   ERROR: Cannot find file ./include/linux/fwctl.h
   WARNING: No kernel-doc for file ./include/linux/fwctl.h
>> Documentation/wmi/devices/tongfang-mifs-wmi.rst:61: WARNING: Literal block expected; none found. [docutils]
>> Documentation/wmi/devices/tongfang-mifs-wmi.rst:69: WARNING: Title underline too short.
--
   WMI Methods (MICommonInterface)
   ============================== [docutils]
>> Documentation/wmi/devices/tongfang-mifs-wmi.rst:69: WARNING: Title underline too short.


vim +61 Documentation/wmi/devices/tongfang-mifs-wmi.rst

    59	
    60	
  > 61	Reverse-Engineering the EC WMI interface
    62	========================================
    63	
    64	The OEM software can be download from `this link <https://iknow.lenovo.com.cn/detail/429447>`_
    65	
    66	Nothing is obfuscated, In this case, `ILSpy <https://github.com/icsharpcode/ILSpy>`_ could be helpful.
    67	
    68	WMI Methods (MICommonInterface)
  > 69	==============================
    70	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2026-01-25 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25  7:15 Mingyou Chen
2026-01-25 13:18 ` kernel test robot [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=202601251425.LsolyF4U-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cryolitia.pukngae@linux.dev \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=qby140326@gmail.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

Powered by JetHome