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 0FD02C77B73 for ; Mon, 22 May 2023 16:47:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232895AbjEVQr2 (ORCPT ); Mon, 22 May 2023 12:47:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49918 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231766AbjEVQr0 (ORCPT ); Mon, 22 May 2023 12:47:26 -0400 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E13FFDC for ; Mon, 22 May 2023 09:47:25 -0700 (PDT) Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-75b1975ea18so45734985a.3 for ; Mon, 22 May 2023 09:47:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1684774045; x=1687366045; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=RtYZcbQKacTkkwOnNbr0k7FvVbVL4fzfTWwOXkqVav4=; b=DmcJi/OcG35j8NGwwuXsQr3VopobdJqXFO0zhgiKpZ9nx+yyMBmR1ZR2MKnPQmt/jt y5E19p81y/cmOUbQizusn5nlIzG59cql6X/zy3xzjYBje52Y1g3iUZW2ZYYW3+WtNXDZ PrrxKi0bNM7kF9RQVTMnjZhTWb+91sj25c+Qwc3u4kIA7SoVNq4O0+bhUjaZElcLdUW5 z/nJexHU62dZ4vEz6PspVFHKvP247ivyMTffdVisJEBmlITsUGsy007nBK2cxALN27ia PuGkWJ3q9w+2QDuisPKOw+g9VfuwhKYUyrJlNLd+XeBqqKxo4+fk64qU50JqYw4zsjzb ffOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684774045; x=1687366045; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=RtYZcbQKacTkkwOnNbr0k7FvVbVL4fzfTWwOXkqVav4=; b=Sa4SqNUX+raUBCvilQbuMsrt4dIQEN3qqXIPH+o/e0afLOStMbON8hMqR+elkY7CUY 3wThKLh7j2CQKwH7VttBzdvKTDs3Nn2k2XjmJ1BuZwDQ260yXmnEdS1t0P8Hng0kwBhr o8tii9c5wFWCJmVslnTzJt3bdBOLTxtLtf1yxO2a1RIginwNWXzQVJi/bhuSpzVniY1R 5i2AycEqStUpFYLjMo/JsmQBgZFvQxMeICNAs3lDFGxnzggFsCey4/ErggMj/qmTCy+/ Nj5/Nx/JRvk5X6vdk1Qbp/SJAs6SCkpBq5NwvJlgbIw7mjk4ufAXVjF/Jck4Wkhbgaxu 3jfg== X-Gm-Message-State: AC+VfDyse24qTQOWscmT0oNJHndhtW2QLHREzs3DUk2O3PpZ5fj/lorS 9DjvAsre/DX+fu7uVef6cgr6r7op80WwuMlN807cGQ== X-Google-Smtp-Source: ACHHUZ6W5buVDy/kIOeIyMoEFAvmSJ/P7EkykMBmkr+MDoVlESJiSwTnjP7ULqt2dw5RubCBiuQorIcPzsV0ggE+Fsk= X-Received: by 2002:a05:620a:b96:b0:75b:23a0:e7c9 with SMTP id k22-20020a05620a0b9600b0075b23a0e7c9mr1336547qkh.42.1684774044909; Mon, 22 May 2023 09:47:24 -0700 (PDT) MIME-Version: 1.0 References: <20230522171557.32027acf@canb.auug.org.au> In-Reply-To: From: Nick Desaulniers Date: Mon, 22 May 2023 09:47:14 -0700 Message-ID: Subject: Re: linux-next: build failure after merge of the amdgpu tree To: Alex Deucher Cc: Alex Deucher , Felix Kuehling , Harish Kasiviswanathan , Rajneesh Bhardwaj , Linux Kernel Mailing List , Linux Next Mailing List , Stephen Rothwell , llvm@lists.linux.dev, Linus Torvalds Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 22, 2023 at 9:36=E2=80=AFAM Alex Deucher wrote: > > On Mon, May 22, 2023 at 12:29=E2=80=AFPM Nick Desaulniers > wrote: > > > > On Mon, May 22, 2023 at 05:15:57PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the amdgpu tree, today's linux-next build (arm allmodco= nfig > > > clang-17) failed like this: > > > > > > drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c:146:54: error: format specif= ies type 'unsigned long long' but the argument has type 'dma_addr_t' (aka '= unsigned int') [-Werror,-Wformat] > > > > > > Caused by commit > > > > > > d020a29b6b58 ("drm/amdgpu: Allocate GART table in RAM for AMD APU") > > > > > > Reported by the kernelci.org bot. > > > > Alex, > > This is the third report of linux-next being broken for clang due to th= e > > AMDGPU tree. > > 1. https://lore.kernel.org/lkml/20230522171557.32027acf@canb.auug.org.a= u/ > > 2. https://lore.kernel.org/lkml/20230522171145.38a8bd4d@canb.auug.org.a= u/ > > 3. https://lore.kernel.org/lkml/20230522170031.5fb87a64@canb.auug.org.a= u/ > > > > Our CI is red as a result. > > https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs= /5045716034/jobs/9053211936 > > > > When will AMD start testing their kernels with Clang? > > We have clang as part of our CI system and have had it for a while. > I'm not sure why it didn't catch these. Our CI clang builds are > currently passing. Can you verify that the driver configs are enabled for those builds? Looking through my CI reports, it looks like allmodconfig/allyesconfig is red from this tree for ARCH=3Dx86_64 and ARCH=3Darm64. Examples: x86_64: https://github.com/ClangBuiltLinux/continuous-integration2/actions/= runs/5045594636/jobs/9052932014 arm64: https://github.com/ClangBuiltLinux/continuous-integration2/actions/r= uns/5045594636/jobs/9052930995 > > Alex > > > > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > > > Thanks for reporting these, Stephen. --=20 Thanks, ~Nick Desaulniers