Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751581AbdFIL7I (ORCPT ); Fri, 9 Jun 2017 07:59:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47298 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751524AbdFIL7H (ORCPT ); Fri, 9 Jun 2017 07:59:07 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C625CC049D5C Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=msnitzer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com C625CC049D5C Date: Fri, 9 Jun 2017 07:59:05 -0400 From: Mike Snitzer To: Damien Le Moal Cc: Stephen Rothwell , Alasdair G Kergon , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build failure after merge of the device-mapper tree Message-ID: <20170609115905.GA11110@redhat.com> References: <20170609131237.41b77828@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 09 Jun 2017 11:59:07 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 29 On Fri, Jun 09 2017 at 12:28am -0400, Damien Le Moal wrote: > Stephen, > > On 6/9/17 12:12, Stephen Rothwell wrote: > > Hi all, > > > > After merging the device-mapper tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/md/dm-zoned-target.c:947:2: error: unknown field 'suspend' specified in initializer > > .suspend = dmz_suspend, > > ^ > > drivers/md/dm-zoned-target.c:947:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] > > .suspend = dmz_suspend, > > ^ > > > > Caused by commit > > > > 02da2e15e81f ("dm zoned: drive-managed zoned block device target") > > > > I have used the device-mapper tree from next-20170608 for today. > > My apologies for that. My mistake. > I just posted a patch to dm-devel to fix this. > Everything should come in order after Mike's review. I'm to blame for the above issue. I've now fixed it up.