On Thu, Sep 14 2023 at 10:54P -0400, kernel test robot <l...@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-...@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-...@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 <l...@intel.com> > | Closes: > https://lore.kernel.org/oe-kbuild-all/202309151023.qpbcnocn-...@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
