From: kernel test robot <lkp@intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Sasha Levin <sashal@kernel.org>
Subject: [stable:linux-5.10.y 3594/9999] drivers/gpu/drm/vc4/vc4_dsi.c:617:35: warning: unused variable 'dsi0_regs'
Date: Thu, 27 Jul 2023 20:27:04 +0800 [thread overview]
Message-ID: <202307272055.DLQgWCti-lkp@intel.com> (raw)
Hi Maxime,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y
head: 3602dbc57b556eff2456715301d35a1ef8964bba
commit: 6cc1edddcf02f69664887ea7ed4b604481ae300e [3594/9999] drm/vc4: dsi: Introduce a variant structure
config: mips-randconfig-r023-20230727 (https://download.01.org/0day-ci/archive/20230727/202307272055.DLQgWCti-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230727/202307272055.DLQgWCti-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/202307272055.DLQgWCti-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/vc4/vc4_dsi.c:617:35: warning: unused variable 'dsi0_regs' [-Wunused-const-variable]
617 | static const struct debugfs_reg32 dsi0_regs[] = {
| ^
1 warning generated.
vim +/dsi0_regs +617 drivers/gpu/drm/vc4/vc4_dsi.c
4078f5757144234 Eric Anholt 2017-01-31 616
3051719af11eb48 Eric Anholt 2019-02-20 @617 static const struct debugfs_reg32 dsi0_regs[] = {
3051719af11eb48 Eric Anholt 2019-02-20 618 VC4_REG32(DSI0_CTRL),
3051719af11eb48 Eric Anholt 2019-02-20 619 VC4_REG32(DSI0_STAT),
3051719af11eb48 Eric Anholt 2019-02-20 620 VC4_REG32(DSI0_HSTX_TO_CNT),
3051719af11eb48 Eric Anholt 2019-02-20 621 VC4_REG32(DSI0_LPRX_TO_CNT),
3051719af11eb48 Eric Anholt 2019-02-20 622 VC4_REG32(DSI0_TA_TO_CNT),
3051719af11eb48 Eric Anholt 2019-02-20 623 VC4_REG32(DSI0_PR_TO_CNT),
3051719af11eb48 Eric Anholt 2019-02-20 624 VC4_REG32(DSI0_DISP0_CTRL),
3051719af11eb48 Eric Anholt 2019-02-20 625 VC4_REG32(DSI0_DISP1_CTRL),
3051719af11eb48 Eric Anholt 2019-02-20 626 VC4_REG32(DSI0_INT_STAT),
3051719af11eb48 Eric Anholt 2019-02-20 627 VC4_REG32(DSI0_INT_EN),
3051719af11eb48 Eric Anholt 2019-02-20 628 VC4_REG32(DSI0_PHYC),
3051719af11eb48 Eric Anholt 2019-02-20 629 VC4_REG32(DSI0_HS_CLT0),
3051719af11eb48 Eric Anholt 2019-02-20 630 VC4_REG32(DSI0_HS_CLT1),
3051719af11eb48 Eric Anholt 2019-02-20 631 VC4_REG32(DSI0_HS_CLT2),
3051719af11eb48 Eric Anholt 2019-02-20 632 VC4_REG32(DSI0_HS_DLT3),
3051719af11eb48 Eric Anholt 2019-02-20 633 VC4_REG32(DSI0_HS_DLT4),
3051719af11eb48 Eric Anholt 2019-02-20 634 VC4_REG32(DSI0_HS_DLT5),
3051719af11eb48 Eric Anholt 2019-02-20 635 VC4_REG32(DSI0_HS_DLT6),
3051719af11eb48 Eric Anholt 2019-02-20 636 VC4_REG32(DSI0_HS_DLT7),
3051719af11eb48 Eric Anholt 2019-02-20 637 VC4_REG32(DSI0_PHY_AFEC0),
3051719af11eb48 Eric Anholt 2019-02-20 638 VC4_REG32(DSI0_PHY_AFEC1),
3051719af11eb48 Eric Anholt 2019-02-20 639 VC4_REG32(DSI0_ID),
4078f5757144234 Eric Anholt 2017-01-31 640 };
4078f5757144234 Eric Anholt 2017-01-31 641
:::::: The code at line 617 was first introduced by commit
:::::: 3051719af11eb48dc8947826cfb66dbe0f281c7d drm/vc4: Use drm_print_regset32() for our debug register dumping.
:::::: TO: Eric Anholt <eric@anholt.net>
:::::: CC: Eric Anholt <eric@anholt.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-27 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202307272055.DLQgWCti-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=maxime@cerno.tech \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@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