mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	Forest Bond <forest@alittletooquiet.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [PATCH 2/5] staging: vt6656: Remove unused rf_type in baseband.c
Date: Sat, 12 Mar 2022 00:06:14 +0800	[thread overview]
Message-ID: <202203112347.5u5Hv6vj-lkp@intel.com> (raw)
In-Reply-To: <77dcff8602084484532fcbd734aafd138087c5ee.1646935331.git.philipp.g.hortmann@gmail.com>

Hi Philipp,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on staging/staging-testing]

url:    https://github.com/0day-ci/linux/commits/Philipp-Hortmann/staging-vt6656-Remove-unused-5GHz-support/20220311-025658
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git b25c7dc13fb8842e8634bd846a7a96f2176f0244
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20220311/202203112347.5u5Hv6vj-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 276ca87382b8f16a65bddac700202924228982f6)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/747c899152efe7f0dbbcdd5399f1b1de3a7ba51d
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Philipp-Hortmann/staging-vt6656-Remove-unused-5GHz-support/20220311-025658
        git checkout 747c899152efe7f0dbbcdd5399f1b1de3a7ba51d
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/bluetooth/ drivers/staging/vt6656/

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

All warnings (new ones prefixed by >>):

>> drivers/staging/vt6656/baseband.c:170:35: warning: unused variable 'vt3342_vnt_threshold' [-Wunused-const-variable]
   static const struct vnt_threshold vt3342_vnt_threshold[] = {
                                     ^
   1 warning generated.


vim +/vt3342_vnt_threshold +170 drivers/staging/vt6656/baseband.c

69a809e1569312 Oscar Carter 2020-03-28  169  
69a809e1569312 Oscar Carter 2020-03-28 @170  static const struct vnt_threshold vt3342_vnt_threshold[] = {
69a809e1569312 Oscar Carter 2020-03-28  171  	{0, 0x00, 0x38},	/* Max sensitivity */
69a809e1569312 Oscar Carter 2020-03-28  172  	{66, 0x00, 0x43},
69a809e1569312 Oscar Carter 2020-03-28  173  	{65, 0x00, 0x52},
69a809e1569312 Oscar Carter 2020-03-28  174  	{64, 0x00, 0x68},
69a809e1569312 Oscar Carter 2020-03-28  175  	{63, 0x00, 0x80},
69a809e1569312 Oscar Carter 2020-03-28  176  	{62, 0x00, 0x9c},
69a809e1569312 Oscar Carter 2020-03-28  177  	{61, 0x00, 0xc0},
69a809e1569312 Oscar Carter 2020-03-28  178  	{60, 0x00, 0xea},
69a809e1569312 Oscar Carter 2020-03-28  179  	{59, 0x01, 0x30},
69a809e1569312 Oscar Carter 2020-03-28  180  	{58, 0x01, 0x70},
69a809e1569312 Oscar Carter 2020-03-28  181  	{57, 0x01, 0xb0},
69a809e1569312 Oscar Carter 2020-03-28  182  	{56, 0x02, 0x30},
69a809e1569312 Oscar Carter 2020-03-28  183  	{55, 0x02, 0xc0},
69a809e1569312 Oscar Carter 2020-03-28  184  	{53, 0x04, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  185  	{51, 0x07, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  186  	{49, 0x0a, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  187  	{47, 0x11, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  188  	{45, 0x18, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  189  	{43, 0x26, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  190  	{42, 0x36, 0x00},
69a809e1569312 Oscar Carter 2020-03-28  191  	{41, 0xff, 0x00}
69a809e1569312 Oscar Carter 2020-03-28  192  };
69a809e1569312 Oscar Carter 2020-03-28  193  

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

  reply	other threads:[~2022-03-11 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 18:54 [PATCH 0/5] staging: vt6656: Remove unused 5GHz support Philipp Hortmann
2022-03-10 18:54 ` [PATCH 1/5] staging: vt6656: Remove unused rf_type in channel.c Philipp Hortmann
2022-03-10 18:54 ` [PATCH 2/5] staging: vt6656: Remove unused rf_type in baseband.c Philipp Hortmann
2022-03-11 16:06   ` kernel test robot [this message]
2022-03-10 18:54 ` [PATCH 3/5] staging: vt6656: Remove unused rf_type in rf.c; top level Philipp Hortmann
2022-03-10 18:54 ` [PATCH 4/5] staging: vt6656: Remove unused rf_type in rf.c; unused variables Philipp Hortmann
2022-03-10 18:54 ` [PATCH 5/5] staging: vt6656: Remove unused rf_type in card.c Philipp Hortmann
2022-03-10 21:30   ` kernel test robot
2022-03-14 17:35 ` [PATCH 0/5] staging: vt6656: Remove unused 5GHz support Greg Kroah-Hartman

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=202203112347.5u5Hv6vj-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=llvm@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.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

all inboxes | Powered by JetHome®