llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Paul Luse <paulluselinux@gmail.com>, linux-raid@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	paul.e.luse@intel.com, Paul Luse <paulluselinux@gmail.com>
Subject: Re: [PATCH] md:  CI log retrival test - do not review
Date: Mon, 7 Oct 2024 06:16:52 +0800	[thread overview]
Message-ID: <202410070623.1WRxUPy0-lkp@intel.com> (raw)
In-Reply-To: <20241004124227.3540-1-paulluselinux@gmail.com>

Hi Paul,

kernel test robot noticed the following build errors:

[auto build test ERROR on song-md/md-next]
[also build test ERROR on linus/master v6.12-rc1 next-20241004]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Paul-Luse/md-CI-log-retrival-test-do-not-review/20241004-204420
base:   https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-next
patch link:    https://lore.kernel.org/r/20241004124227.3540-1-paulluselinux%40gmail.com
patch subject: [PATCH] md:  CI log retrival test - do not review
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20241007/202410070623.1WRxUPy0-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241007/202410070623.1WRxUPy0-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/202410070623.1WRxUPy0-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/md/raid1.c:68:1: error: use of undeclared identifier 'x'
      68 | x
         | ^
   1 error generated.


vim +/x +68 drivers/md/raid1.c

    54	
    55	#define START(node) ((node)->start)
    56	#define LAST(node) ((node)->last)
    57	INTERVAL_TREE_DEFINE(struct serial_info, node, sector_t, _subtree_last,
    58			     START, LAST, static inline, raid1_rb);
    59	
    60	static int check_and_add_serial(struct md_rdev *rdev, struct r1bio *r1_bio,
    61					struct serial_info *si, int idx)
    62	{
    63		unsigned long flags;
    64		int ret = 0;
    65		sector_t lo = r1_bio->sector;
    66		sector_t hi = lo + r1_bio->sectors;
    67		struct serial_in_rdev *serial = &rdev->serial[idx];
  > 68	x
    69		spin_lock_irqsave(&serial->serial_lock, flags);
    70		/* collision happened */
    71		if (raid1_rb_iter_first(&serial->serial_rb, lo, hi))
    72			ret = -EBUSY;
    73		else {
    74			si->start = lo;
    75			si->last = hi;
    76			raid1_rb_insert(si, &serial->serial_rb);
    77		}
    78		spin_unlock_irqrestore(&serial->serial_lock, flags);
    79	
    80		return ret;
    81	}
    82	

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

           reply	other threads:[~2024-10-06 22:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20241004124227.3540-1-paulluselinux@gmail.com>]

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=202410070623.1WRxUPy0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul.e.luse@intel.com \
    --cc=paulluselinux@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;
as well as URLs for NNTP newsgroup(s).