From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A7C4C433EF for ; Mon, 11 Jul 2022 08:15:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229838AbiGKIPv (ORCPT ); Mon, 11 Jul 2022 04:15:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229837AbiGKIP2 (ORCPT ); Mon, 11 Jul 2022 04:15:28 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 43F7B1DA5F; Mon, 11 Jul 2022 01:15:24 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id DEE7BB80E41; Mon, 11 Jul 2022 08:15:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F614C34115; Mon, 11 Jul 2022 08:15:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1657527321; bh=bHT6yX754bDNr+YlySEm4rQB15/WYr8mKVfdle6pm9c=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=nM9gmnfPlCOHIBGv6E//DWjkYWhBo2srCG3m5iQ2CyVDPW2GPbmqov9snxszAo6wf SxyfAvqmfGeeYCHc/K9GSyaoxmYRQ2wp3n7XhhhP+duEEs6kPgINr3Bd7r+Wj6B2H2 in0gCtSiG071XUtbEddFv6G7nzzqVrTFX8sdxigHkHV1uZrvE4az+tk+l2G4y9aRLY tRMS+F9z60e1nM7kPGDk6qrhFsLNskQJDFIQFDuvR4Xr4J9SI629iwTFbPGCVgaYNS 6NobdIb6yRNX7rqSjVFtuQpjJQJ5WrnVFJBulpAYDP+M+NrPEMQJAm9K0fi1fFZPZx 53KZp4jOO/CpQ== Received: from [213.208.244.172] (helo=wait-a-minute.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oAoZb-006aag-JT; Mon, 11 Jul 2022 09:15:19 +0100 Date: Mon, 11 Jul 2022 09:15:19 +0100 Message-ID: <87mtdgkqug.wl-maz@kernel.org> From: Marc Zyngier To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the irqchip tree In-Reply-To: <20220711154252.4b88a601@canb.auug.org.au> References: <20220711154252.4b88a601@canb.auug.org.au> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 213.208.244.172 X-SA-Exim-Rcpt-To: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 11 Jul 2022 06:42:52 +0100, Stephen Rothwell wrote: > > Hi all, > > After merging the irqchip tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/gpio/gpio-thunderx.c:18: > include/asm-generic/msi.h:32:3: error: conflicting types for 'msi_alloc_info_t'; have 'struct msi_alloc_info' > 32 | } msi_alloc_info_t; > | ^~~~~~~~~~~~~~~~ > In file included from include/linux/gpio/driver.h:15, > from drivers/gpio/gpio-thunderx.c:10: > arch/x86/include/asm/msi.h:7:31: note: previous declaration of 'msi_alloc_info_t' with type 'msi_alloc_info_t' {aka 'struct irq_alloc_info'} > 7 | typedef struct irq_alloc_info msi_alloc_info_t; > | ^~~~~~~~~~~~~~~~ > drivers/gpio/gpio-thunderx.c: In function 'thunderx_gpio_populate_parent_alloc_info': > drivers/gpio/gpio-thunderx.c:416:34: error: initialization of 'msi_alloc_info_t *' {aka 'struct msi_alloc_info *'} from incompatible pointer type 'msi_alloc_info_t *' {aka 'struct irq_alloc_info *'} [-Werror=incompatible-pointer-types] > 416 | msi_alloc_info_t *info = &gfwspec->msiinfo; > | ^ > cc1: all warnings being treated as errors > > Caused by commit > > 91a29af413de ("gpio: Remove dynamic allocation from populate_parent_alloc_arg()") > > I have used the irqchip tree from next-20220707 again for today. Huh. Twice sorry about that one. Patch sent to fix the breakage, and will push this into irqchip-next shortly. Thanks, M. -- Without deviation from the norm, progress is not possible.