All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Yang <mmyangfl@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Jakub Kicinski <kuba@kernel.org>,
	Andrew Lunn <andrew@lunn.ch>
Subject: [linux-next:master 3282/4370] drivers/net/dsa/motorcomm/chip.c:4229:22: warning: unused variable 'priv'
Date: Sat, 05 Sep 2026 17:58:08 +0800	[thread overview]
Message-ID: <202609051727.O4ApRZZK-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   af5f12805e5cefa4fe68d6127c7e1fb78cd5535c
commit: 9af9a816821365e57736307bfdfcf06d89065556 [3282/4370] net: dsa: motorcomm: Add LED support
config: mips-randconfig-r061-20260905 (https://download.01.org/0day-ci/archive/20260905/202609051727.O4ApRZZK-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260905/202609051727.O4ApRZZK-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/202609051727.O4ApRZZK-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/net/dsa/motorcomm/chip.c: In function 'yt921x_dsa_teardown':
>> drivers/net/dsa/motorcomm/chip.c:4229:22: warning: unused variable 'priv' [-Wunused-variable]
     struct yt921x_priv *priv = to_yt921x_priv(ds);
                         ^~~~


vim +/priv +4229 drivers/net/dsa/motorcomm/chip.c

  4226	
  4227	static void yt921x_dsa_teardown(struct dsa_switch *ds)
  4228	{
> 4229		struct yt921x_priv *priv = to_yt921x_priv(ds);
  4230	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-09-05  9:58 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=202609051727.O4ApRZZK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=kuba@kernel.org \
    --cc=mmyangfl@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.