From: kernel test robot <lkp@intel.com>
To: Breno Rodrigues Alves <breno3011alves@gmail.com>,
torvalds@linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, arnd@arndb.de,
linux-clk@vger.kernel.org, linux-input@vger.kernel.org,
linux-media@vger.kernel.org, linux-pci@vger.kernel.org,
linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
linux-staging@lists.linux.dev, linux-fbdev@vger.kernel.org,
linux-security-module@vger.kernel.org,
Breno Rodrigues Alves <breno3011alves@gmail.com>
Subject: Re: [PATCH v5] Kconfig: fix typos in core makefiles and purge defective DVB debug (v5)
Date: Thu, 10 Sep 2026 08:11:57 +0800 [thread overview]
Message-ID: <202609100824.ndDVSLWu-lkp@intel.com> (raw)
In-Reply-To: <20260905003005.118245-1-breno3011alves@gmail.com>
Hi Breno,
kernel test robot noticed the following build errors:
[auto build test ERROR on lee-leds/for-leds-next]
[also build test ERROR on broonie-regulator/for-next linus/master v7.3-rc2 next-20260909]
[cannot apply to linux/master]
[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/Breno-Rodrigues-Alves/Kconfig-fix-typos-in-core-makefiles-and-purge-defective-DVB-debug-v5/20260904-213005
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link: https://lore.kernel.org/r/20260905003005.118245-1-breno3011alves%40gmail.com
patch subject: [PATCH v5] Kconfig: fix typos in core makefiles and purge defective DVB debug (v5)
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260910/202609100824.ndDVSLWu-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260910/202609100824.ndDVSLWu-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/202609100824.ndDVSLWu-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> drivers/media/dvb-core/dvb_net.c:76:35: error: 'TS_SZ' undeclared here (not in a function)
76 | static unsigned char ule_hist[100*TS_SZ] = { 0 };
| ^~~~~
>> drivers/media/dvb-core/dvb_net.c:76:22: warning: 'ule_hist' defined but not used [-Wunused-variable]
76 | static unsigned char ule_hist[100*TS_SZ] = { 0 };
| ^~~~~~~~
vim +/TS_SZ +76 drivers/media/dvb-core/dvb_net.c
^1da177e4c3f41 drivers/media/dvb/dvb-core/dvb_net.c Linus Torvalds 2005-04-16 70
e9f8b7ccd92d83 drivers/media/dvb-core/dvb_net.c Breno Rodrigues Alves 2026-09-04 71 #ifdef CONFIG_DVB_ULE_DEBUG
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 72 /*
ba711e1cee7553 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 73 * The code inside DVB_ULE_DEBUG keeps a history of the
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 74 * last 100 TS cells processed.
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 75 */
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 @76 static unsigned char ule_hist[100*TS_SZ] = { 0 };
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 77 static unsigned char *ule_where = ule_hist, ule_dump;
b93a25e120d5a4 drivers/media/dvb-core/dvb_net.c Mauro Carvalho Chehab 2017-12-11 78
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-09-10 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 0:30 Breno Rodrigues Alves
2026-09-07 6:59 ` Thomas Zimmermann
2026-09-09 14:54 ` Dan Carpenter
2026-09-10 0:11 ` 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=202609100824.ndDVSLWu-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=breno3011alves@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®