All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 15/15] net/wireless/wext-proc.c:122:36: warning: 'wireless_seq_ops' defined but not used
Date: Wed, 07 Oct 2026 00:51:08 +0200	[thread overview]
Message-ID: <202610070013.n2gVftny-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android17-6.18
head:   51015f38e9dca4ae0e4cdfd507558f2b438dd124
commit: dd99bb34c52de463398910adc71917769dde6f54 [15/15] Revert "ANDROID: suppress GKI configs for 32-bit builds"
config: arm-randconfig-r2309-20261006 (https://download.01.org/0day-ci/archive/20261007/202610070013.n2gVftny-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 16.1.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261007/202610070013.n2gVftny-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/202610070013.n2gVftny-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> net/wireless/wext-proc.c:122:36: warning: 'wireless_seq_ops' defined but not used [-Wunused-const-variable=]
     122 | static const struct seq_operations wireless_seq_ops = {
         |                                    ^~~~~~~~~~~~~~~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for PHYLINK
   Depends on [n]: NETDEVICES [=n]
   Selected by [y]:
   - GKI_HIDDEN_ETHERNET_CONFIGS [=y]
   WARNING: unmet direct dependencies detected for DRM_GEM_SHMEM_HELPER
   Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
   Selected by [y]:
   - GKI_HIDDEN_DRM_CONFIGS [=y] && DRM [=y]
   WARNING: unmet direct dependencies detected for DRM_TTM
   Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
   Selected by [y]:
   - GKI_HIDDEN_DRM_CONFIGS [=y] && HAS_IOMEM [=y] && DRM [=y]
   WARNING: unmet direct dependencies detected for WEXT_PROC
   Depends on [n]: NET [=y] && WIRELESS [=y] && PROC_FS [=n] && WEXT_CORE [=y]
   Selected by [y]:
   - GKI_LEGACY_WEXT_ALLCONFIG [=y]


vim +/wireless_seq_ops +122 net/wireless/wext-proc.c

3d23e349d807177 Johannes Berg 2009-09-29  121  
3d23e349d807177 Johannes Berg 2009-09-29 @122  static const struct seq_operations wireless_seq_ops = {
3d23e349d807177 Johannes Berg 2009-09-29  123  	.start = wireless_dev_seq_start,
3d23e349d807177 Johannes Berg 2009-09-29  124  	.next  = wireless_dev_seq_next,
3d23e349d807177 Johannes Berg 2009-09-29  125  	.stop  = wireless_dev_seq_stop,
3d23e349d807177 Johannes Berg 2009-09-29  126  	.show  = wireless_dev_seq_show,
3d23e349d807177 Johannes Berg 2009-09-29  127  };
3d23e349d807177 Johannes Berg 2009-09-29  128  

:::::: The code at line 122 was first introduced by commit
:::::: 3d23e349d807177eaf519d444677cee86b1a04cf wext: refactor

:::::: TO: Johannes Berg <johannes@sipsolutions.net>
:::::: CC: John W. Linville <linville@tuxdriver.com>

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

                 reply	other threads:[~2026-10-06 22:51 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=202610070013.n2gVftny-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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.