All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: kbuild-all@lists.01.org, linux-wireless@vger.kernel.org
Subject: [mac80211-next:master 2177/2199] net/ethtool/cabletest.c:230:5: sparse: sparse: symbol 'ethnl_act_cable_test_tdr_cfg' was not declared. Should it be static?
Date: Thu, 28 May 2020 00:37:12 +0800	[thread overview]
Message-ID: <202005280023.WcZcdZML%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
head:   119aadf816f5373dc82ca4109d6d5b777e00475b
commit: f2bc8ad31a7f814237bc6301d59296d76505a688 [2177/2199] net: ethtool: Allow PHY cable test TDR data to configured
config: x86_64-randconfig-s022-20200527 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-240-gf0fe1cd9-dirty
        git checkout f2bc8ad31a7f814237bc6301d59296d76505a688
        # save the attached .config to linux build tree
        make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> net/ethtool/cabletest.c:230:5: sparse: sparse: symbol 'ethnl_act_cable_test_tdr_cfg' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38238 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [mac80211-next:master 2177/2199] net/ethtool/cabletest.c:230:5: sparse: sparse: symbol 'ethnl_act_cable_test_tdr_cfg' was not declared. Should it be static?
Date: Thu, 28 May 2020 00:37:12 +0800	[thread overview]
Message-ID: <202005280023.WcZcdZML%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
head:   119aadf816f5373dc82ca4109d6d5b777e00475b
commit: f2bc8ad31a7f814237bc6301d59296d76505a688 [2177/2199] net: ethtool: Allow PHY cable test TDR data to configured
config: x86_64-randconfig-s022-20200527 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-240-gf0fe1cd9-dirty
        git checkout f2bc8ad31a7f814237bc6301d59296d76505a688
        # save the attached .config to linux build tree
        make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> net/ethtool/cabletest.c:230:5: sparse: sparse: symbol 'ethnl_act_cable_test_tdr_cfg' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38238 bytes --]

             reply	other threads:[~2020-05-27 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 16:37 kbuild test robot [this message]
2020-05-27 16:37 ` [mac80211-next:master 2177/2199] net/ethtool/cabletest.c:230:5: sparse: sparse: symbol 'ethnl_act_cable_test_tdr_cfg' was not declared. Should it be static? kbuild test robot
2020-05-27 16:37 ` [RFC PATCH mac80211-next] net: ethtool: ethnl_act_cable_test_tdr_cfg() can be static kbuild test robot
2020-05-27 16:37   ` kbuild test robot

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=202005280023.WcZcdZML%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-wireless@vger.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 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.