linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, 0day robot <lkp@intel.com>
Subject: drivers/leds/leds-pca955x.c:149:19: warning: unused function 'pca95xx_num_led_regs'
Date: Sat, 6 Nov 2021 01:25:11 +0800	[thread overview]
Message-ID: <202111060155.nIX7S32Q-lkp@intel.com> (raw)

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

tree:   https://github.com/0day-ci/linux/commits/Andrew-Jeffery/leds-pca955x-Expose-GPIOs-for-all-pins/20210922-122145
head:   c09828c1b9528b9e07d46e8afde8bc26456b6151
commit: 240ea6dc56b47b440fad24d4c8d83da4da37951b leds: pca955x: Make the gpiochip always expose all pins
date:   6 weeks ago
config: mips-randconfig-r013-20210928 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project dc6e8dfdfe7efecfda318d43a06fae18b40eb498)
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 mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/240ea6dc56b47b440fad24d4c8d83da4da37951b
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Andrew-Jeffery/leds-pca955x-Expose-GPIOs-for-all-pins/20210922-122145
        git checkout 240ea6dc56b47b440fad24d4c8d83da4da37951b
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/leds/

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/leds/leds-pca955x.c:149:19: warning: unused function 'pca95xx_num_led_regs'
   static inline int pca95xx_num_led_regs(int bits)
   ^
   fatal error: error in backend: Nested variants found in inline asm string: ' .set push
   .set mips64r2
   .if ( 0x00 ) != -1)) 0x00 ) != -1)) : ($( static struct ftrace_branch_data __attribute__((__aligned__(4))) __attribute__((__section__("_ftrace_branch"))) __if_trace = $( .func = __func__, .file = "arch/mips/include/asm/bitops.h", .line = 105, $); 0x00 ) != -1)) : $))) ) && ( 0 ); .set push; .set mips64r2; .rept 1; sync 0x00; .endr; .set pop; .else; ; .endif
   1: ll $0, $1
   or $0, $2
   sc $0, $1
   beqz $0, 1b
   .set pop
   '
   clang-14: error: clang frontend command failed with exit code 70 (use -v to see invocation)
   clang version 14.0.0 (git://gitmirror/llvm_project 847a6807332b13f43704327c2d30103ec0347c77)
   Target: mipsel-unknown-linux
   Thread model: posix
   InstalledDir: /opt/cross/clang-847a680733/bin
   clang-14: note: diagnostic msg:
   Makefile arch drivers include kernel nr_bisected scripts source usr


vim +/pca95xx_num_led_regs +149 drivers/leds/leds-pca955x.c

f46e9203d9a100 Nate Case 2008-07-16  147  
f46e9203d9a100 Nate Case 2008-07-16  148  /* 4 bits per LED selector register */
f46e9203d9a100 Nate Case 2008-07-16 @149  static inline int pca95xx_num_led_regs(int bits)
f46e9203d9a100 Nate Case 2008-07-16  150  {
f46e9203d9a100 Nate Case 2008-07-16  151  	return (bits + 3)  / 4;
f46e9203d9a100 Nate Case 2008-07-16  152  }
f46e9203d9a100 Nate Case 2008-07-16  153  

---
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: 32396 bytes --]

                 reply	other threads:[~2021-11-05 17:26 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=202111060155.nIX7S32Q-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@aj.id.au \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).