public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
	"Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Subject: Re: [PATCH] staging: greybus: Convert uart.c from IDR to XArray
Date: Sun, 15 Aug 2021 01:20:29 +0800	[thread overview]
Message-ID: <202108150119.cNtCvCi9-lkp@intel.com> (raw)
In-Reply-To: <20210814145613.6493-1-fmdefrancesco@gmail.com>

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

Hi "Fabio,

Thank you for the patch! Yet something to improve:

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

url:    https://github.com/0day-ci/linux/commits/Fabio-M-De-Francesco/staging-greybus-Convert-uart-c-from-IDR-to-XArray/20210814-225807
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 0bd35146642bdc56f1b87d75f047b1c92bd2bd39
config: riscv-randconfig-r042-20210814 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 1f7b25ea76a925aca690da28de9d78db7ca99d0c)
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
        # https://github.com/0day-ci/linux/commit/901c5fde0540c767590bce646219889730c4a41b
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Fabio-M-De-Francesco/staging-greybus-Convert-uart-c-from-IDR-to-XArray/20210814-225807
        git checkout 901c5fde0540c767590bce646219889730c4a41b
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=riscv SHELL=/bin/bash drivers/staging/greybus/

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

All errors (new ones prefixed by >>):

>> drivers/staging/greybus/uart.c:346:2: error: no member named 'xa_lock' in 'struct mutex'
           xa_lock(&table_lock);
           ^~~~~~~~~~~~~~~~~~~~
   include/linux/xarray.h:530:39: note: expanded from macro 'xa_lock'
   #define xa_lock(xa)             spin_lock(&(xa)->xa_lock)
                                              ~~~~  ^
   drivers/staging/greybus/uart.c:358:2: error: no member named 'xa_lock' in 'struct mutex'
           xa_unlock(&table_lock);
           ^~~~~~~~~~~~~~~~~~~~~~
   include/linux/xarray.h:531:43: note: expanded from macro 'xa_unlock'
   #define xa_unlock(xa)           spin_unlock(&(xa)->xa_lock)
                                                ~~~~  ^
   2 errors generated.


vim +346 drivers/staging/greybus/uart.c

   341	
   342	static struct gb_tty *get_gb_by_minor(unsigned int minor)
   343	{
   344		struct gb_tty *gb_tty;
   345	
 > 346		xa_lock(&table_lock);
   347		gb_tty = xa_load(&tty_minors, minor);
   348		if (gb_tty) {
   349			mutex_lock(&gb_tty->mutex);
   350			if (gb_tty->disconnected) {
   351				mutex_unlock(&gb_tty->mutex);
   352				gb_tty = NULL;
   353			} else {
   354				tty_port_get(&gb_tty->port);
   355				mutex_unlock(&gb_tty->mutex);
   356			}
   357		}
   358		xa_unlock(&table_lock);
   359		return gb_tty;
   360	}
   361	

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

  reply	other threads:[~2021-08-14 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 14:56 [PATCH] staging: greybus: Convert uart.c from IDR to XArray Fabio M. De Francesco
2021-08-14 17:20 ` kernel test robot [this message]
2021-08-14 17:35 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2021-08-14 17:56 Fabio M. De Francesco

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=202108150119.cNtCvCi9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=elder@kernel.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@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