Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Joe Thornber <ejt@redhat.com>,
	llvm@lists.linux.dev, dm-devel@redhat.com,
	oe-kbuild-all@lists.linux.dev
Subject: Re: [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression
Date: Thu, 14 Sep 2023 23:34:00 -0400	[thread overview]
Message-ID: <ZQPQqCzlu3AUtumF@redhat.com> (raw)
In-Reply-To: <202309151023.QPBCNoCN-lkp@intel.com>

On Thu, Sep 14 2023 at 10:54P -0400,
kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
> head:   edcabec81f12dfc9b86b05084bba3232efdc5e4e
> commit: 59d814674dd66fc64ba229605174bfe0b8e566d5 [2/4] dm persistent data: Introduce extent allocator
> config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230915/202309151023.QPBCNoCN-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230915/202309151023.QPBCNoCN-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/202309151023.QPBCNoCN-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected ';' after expression
>            spin_unlock(&ea->lock)
>                                  ^
>                                  ;
>    drivers/md/persistent-data/dm-extent-allocator.c:544:24: error: expected ';' after expression
>            spin_unlock(&ea->lock)
>                                  ^
>                                  ;
>    2 errors generated.


These were my fault.. Fixed, sorry about the noise.

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


      reply	other threads:[~2023-09-15  3:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  2:54 [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression kernel test robot
2023-09-15  3:34 ` Mike Snitzer [this message]

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=ZQPQqCzlu3AUtumF@redhat.com \
    --to=snitzer@kernel.org \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@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