From: kernel test robot <lkp@intel.com>
To: Kartik <kkartik@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
keescook@chromium.org, andy@kernel.org,
akpm@linux-foundation.org, arnd@arndb.de, petlozup@nvidia.com,
pshete@nvidia.com, ulf.hansson@linaro.org, frank.li@vivo.com,
robh@kernel.org, stefank@nvidia.com, pdeschrijver@nvidia.com,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-mm@kvack.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 7/8] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234
Date: Fri, 13 Oct 2023 02:59:14 +0800 [thread overview]
Message-ID: <202310130245.1Ndq4Syg-lkp@intel.com> (raw)
In-Reply-To: <20231011093412.7994-8-kkartik@nvidia.com>
Hi Kartik,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tegra/for-next]
[also build test WARNING on kees/for-next/hardening akpm-mm/mm-everything linus/master v6.6-rc5 next-20231012]
[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/Kartik/mm-util-Introduce-kmemdup_array-to-duplicate-an-array/20231011-192039
base: https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
patch link: https://lore.kernel.org/r/20231011093412.7994-8-kkartik%40nvidia.com
patch subject: [PATCH v4 7/8] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234
config: arm64-randconfig-002-20231012 (https://download.01.org/0day-ci/archive/20231013/202310130245.1Ndq4Syg-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/202310130245.1Ndq4Syg-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/202310130245.1Ndq4Syg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/soc/tegra/fuse/fuse-tegra.c:314:36: warning: 'tegra_fuse_acpi_match' defined but not used [-Wunused-const-variable=]
314 | static const struct acpi_device_id tegra_fuse_acpi_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~
vim +/tegra_fuse_acpi_match +314 drivers/soc/tegra/fuse/fuse-tegra.c
313
> 314 static const struct acpi_device_id tegra_fuse_acpi_match[] = {
315 { "NVDA200F" },
316 { /* sentinel */ }
317 };
318 MODULE_DEVICE_TABLE(acpi, tegra_fuse_acpi_match);
319
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-12 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 9:34 [PATCH v4 0/8] soc/tegra: fuse: Add ACPI support Kartik
2023-10-11 9:34 ` [PATCH v4 1/8] mm/util: Introduce kmemdup_array() to duplicate an array Kartik
2023-10-11 15:36 ` Andy Shevchenko
2023-10-11 16:13 ` Kartik
2023-10-11 9:34 ` [PATCH v4 2/8] soc/tegra: fuse: Use dev_err_probe for probe failures Kartik
2023-10-11 9:34 ` [PATCH v4 3/8] soc/tegra: fuse: Refactor resource mapping Kartik
2023-10-11 9:34 ` [PATCH v4 4/8] soc/tegra: fuse: Add tegra_acpi_init_apbmisc() Kartik
2023-10-11 9:34 ` [PATCH v4 5/8] soc/tegra: fuse: Add function to add lookups Kartik
2023-10-11 9:34 ` [PATCH v4 6/8] soc/tegra: fuse: Add function to print SKU info Kartik
2023-10-11 9:34 ` [PATCH v4 7/8] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234 Kartik
2023-10-12 18:59 ` kernel test robot [this message]
2023-10-11 9:34 ` [PATCH v4 8/8] soc/tegra: fuse: Add support for Tegra241 Kartik
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=202310130245.1Ndq4Syg-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=frank.li@vivo.com \
--cc=jonathanh@nvidia.com \
--cc=keescook@chromium.org \
--cc=kkartik@nvidia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pdeschrijver@nvidia.com \
--cc=petlozup@nvidia.com \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=stefank@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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