From: kernel test robot <lkp@intel.com>
To: javen <javen_xu@realsil.com.cn>,
hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Javen Xu <javen_xu@realsil.com.cn>
Subject: Re: [PATCH net-next v1 3/3] realtek: Update Makefile and Kconfig
Date: Wed, 28 Jan 2026 06:33:57 +0800 [thread overview]
Message-ID: <202601280610.ncyvilQz-lkp@intel.com> (raw)
In-Reply-To: <20260127113425.1989-4-javen_xu@realsil.com.cn>
Hi javen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/javen/r816e-add-a-fake-driver-r816e-for-RTL8116af/20260127-193831
base: net-next/main
patch link: https://lore.kernel.org/r/20260127113425.1989-4-javen_xu%40realsil.com.cn
patch subject: [PATCH net-next v1 3/3] realtek: Update Makefile and Kconfig
config: openrisc-allmodconfig (https://download.01.org/0day-ci/archive/20260128/202601280610.ncyvilQz-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260128/202601280610.ncyvilQz-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/202601280610.ncyvilQz-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/realtek/r816e/r816e.c:48:32: warning: 'rtl816e_pm_ops' defined but not used [-Wunused-const-variable=]
48 | static const struct dev_pm_ops rtl816e_pm_ops = {
| ^~~~~~~~~~~~~~
vim +/rtl816e_pm_ops +48 drivers/net/ethernet/realtek/r816e/r816e.c
638d27c0a2f682 Javen Xu 2026-01-27 47
638d27c0a2f682 Javen Xu 2026-01-27 @48 static const struct dev_pm_ops rtl816e_pm_ops = {
638d27c0a2f682 Javen Xu 2026-01-27 49 SYSTEM_SLEEP_PM_OPS(rtl816e_pm_suspend, rtl816e_pm_resume)
638d27c0a2f682 Javen Xu 2026-01-27 50 };
638d27c0a2f682 Javen Xu 2026-01-27 51
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-27 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:34 [PATCH net-next v1 0/3] r816e: Add r816e driver in Realtek javen
2026-01-27 11:34 ` [PATCH net-next v1 1/3] r816e: add a fake driver r816e for RTL8116af javen
2026-01-27 17:10 ` kernel test robot
2026-01-27 11:34 ` [PATCH net-next v1 2/3] r816e: Add a Makefile in the r816e folder javen
2026-01-27 11:34 ` [PATCH net-next v1 3/3] realtek: Update Makefile and Kconfig javen
2026-01-27 22:33 ` kernel test robot
2026-01-27 22:33 ` kernel test robot [this message]
2026-01-27 20:58 ` [PATCH net-next v1 0/3] r816e: Add r816e driver in Realtek Heiner Kallweit
2026-01-28 6:53 ` javen
2026-01-28 13:04 ` Andrew Lunn
2026-01-28 19:08 ` Heiner Kallweit
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=202601280610.ncyvilQz-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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