From: kernel test robot <lkp@intel.com>
To: "luo.liu" <luo.liu.linux@163.com>,
sakari.ailus@linux.intel.com, mchehab@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, luo.liu.linux@163.com
Subject: Re: [PATCH] v4l2-async: add debugfs under CONFIG_DEBUG_FS
Date: Tue, 20 Jan 2026 21:47:56 +0800 [thread overview]
Message-ID: <202601202104.uDfihrMe-lkp@intel.com> (raw)
In-Reply-To: <20260120065710.1120819-1-luo.liu.linux@163.com>
Hi luo.liu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d08c85ac8894995d4b0d8fb48d2f6a3e53cd79ab]
url: https://github.com/intel-lab-lkp/linux/commits/luo-liu/v4l2-async-add-debugfs-under-CONFIG_DEBUG_FS/20260120-150913
base: d08c85ac8894995d4b0d8fb48d2f6a3e53cd79ab
patch link: https://lore.kernel.org/r/20260120065710.1120819-1-luo.liu.linux%40163.com
patch subject: [PATCH] v4l2-async: add debugfs under CONFIG_DEBUG_FS
config: powerpc-randconfig-002-20260120 (https://download.01.org/0day-ci/archive/20260120/202601202104.uDfihrMe-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601202104.uDfihrMe-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/202601202104.uDfihrMe-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/debugfs.h:16,
from drivers/media/v4l2-core/v4l2-async.c:8:
>> drivers/media/v4l2-core/v4l2-async.c:967:23: warning: 'pending_subdevs_fops' defined but not used [-Wunused-const-variable=]
967 | DEFINE_SHOW_ATTRIBUTE(pending_subdevs);
| ^~~~~~~~~~~~~~~
include/linux/seq_file.h:213:37: note: in definition of macro 'DEFINE_SHOW_ATTRIBUTE'
213 | static const struct file_operations __name ## _fops = { \
| ^~~~~~
vim +/pending_subdevs_fops +967 drivers/media/v4l2-core/v4l2-async.c
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 949
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 950 static int pending_subdevs_show(struct seq_file *s, void *data)
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 951 {
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 952 struct v4l2_async_notifier *notif;
adb2dcd5f2d49d3 Sakari Ailus 2023-02-16 953 struct v4l2_async_connection *asc;
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 954
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 955 mutex_lock(&list_lock);
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 956
b6d42c35c03dc1a Sakari Ailus 2023-02-22 957 list_for_each_entry(notif, ¬ifier_list, notifier_entry) {
3c8c153914812a9 Sakari Ailus 2021-03-05 958 seq_printf(s, "%s:\n", v4l2_async_nf_name(notif));
9bf19fbf0c8bc43 Sakari Ailus 2023-04-18 959 list_for_each_entry(asc, ¬if->waiting_list, asc_entry)
adb2dcd5f2d49d3 Sakari Ailus 2023-02-16 960 print_waiting_match(s, &asc->match);
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 961 }
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 962
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 963 mutex_unlock(&list_lock);
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 964
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 965 return 0;
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 966 }
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 @967 DEFINE_SHOW_ATTRIBUTE(pending_subdevs);
517fd2b6a058bc4 Ezequiel Garcia 2021-01-08 968
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-20 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:57 [PATCH] v4l2-async: add debugfs under CONFIG_DEBUG_FS luo.liu
2026-01-20 13:47 ` 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=202601202104.uDfihrMe-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luo.liu.linux@163.com \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sakari.ailus@linux.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