public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Luke D. Jones" <luke@ljones.dev>, platform-driver-x86@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
	corentin.chary@gmail.com, "Luke D. Jones" <luke@ljones.dev>
Subject: Re: [PATCH v3 1/5] platform/x86: asus-armoury: move existing tunings to asus-armoury module
Date: Sun, 22 Sep 2024 04:12:44 +0800	[thread overview]
Message-ID: <202409220341.XurF2eMb-lkp@intel.com> (raw)
In-Reply-To: <20240918094250.82430-2-luke@ljones.dev>

Hi Luke,

kernel test robot noticed the following build warnings:

[auto build test WARNING on next-20240918]
[also build test WARNING on v6.11]
[cannot apply to linus/master v6.11 v6.11-rc7 v6.11-rc6]
[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/Luke-D-Jones/platform-x86-asus-armoury-move-existing-tunings-to-asus-armoury-module/20240918-174540
base:   next-20240918
patch link:    https://lore.kernel.org/r/20240918094250.82430-2-luke%40ljones.dev
patch subject: [PATCH v3 1/5] platform/x86: asus-armoury: move existing tunings to asus-armoury module
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20240922/202409220341.XurF2eMb-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240922/202409220341.XurF2eMb-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/202409220341.XurF2eMb-lkp@intel.com/

All warnings (new ones prefixed by >>, old ones prefixed by <<):

>> WARNING: modpost: module hid-asus uses symbol asus_wmi_evaluate_method from namespace ASUS_WMI, but does not import it.

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for GET_FREE_REGION
   Depends on [n]: SPARSEMEM [=n]
   Selected by [m]:
   - RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
   WARNING: unmet direct dependencies detected for OMAP2PLUS_MBOX
   Depends on [n]: MAILBOX [=y] && (ARCH_OMAP2PLUS || ARCH_K3)
   Selected by [m]:
   - TI_K3_M4_REMOTEPROC [=m] && REMOTEPROC [=y] && (ARCH_K3 || COMPILE_TEST [=y])

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

  parent reply	other threads:[~2024-09-21 20:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  9:42 [PATCH v3 0/5] platform/x86: introduce asus-armoury driver Luke D. Jones
2024-09-18  9:42 ` [PATCH v3 1/5] platform/x86: asus-armoury: move existing tunings to asus-armoury module Luke D. Jones
2024-09-18 15:37   ` Mario Limonciello
2024-09-20  7:27     ` Luke Jones
2024-09-21  7:13   ` Christophe JAILLET
2024-09-21  9:49     ` Luke Jones
2024-09-21 17:48   ` kernel test robot
2024-09-21 20:12   ` kernel test robot [this message]
2024-09-22  1:33   ` kernel test robot
2024-09-18  9:42 ` [PATCH v3 2/5] platform/x86: asus-armoury: add dgpu tgp control Luke D. Jones
2024-09-18 15:39   ` Mario Limonciello
2024-09-21  6:57     ` Luke Jones
2024-09-18  9:42 ` [PATCH v3 3/5] platform/x86: asus-armoury: add apu-mem control support Luke D. Jones
2024-09-18 15:44   ` Mario Limonciello
2024-09-21  7:05     ` Luke Jones
2024-09-18  9:42 ` [PATCH v3 4/5] platform/x86: asus-armoury: add core count control Luke D. Jones
2024-09-18  9:42 ` [PATCH v3 5/5] platform/x86: asus-wmi: deprecate bios features Luke D. Jones
2024-09-18 15:50   ` Mario Limonciello
2024-09-21  6:27     ` Luke Jones

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=202409220341.XurF2eMb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=corentin.chary@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox