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 7EEB6C7EE23 for ; Mon, 22 May 2023 16:36:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233040AbjEVQgL (ORCPT ); Mon, 22 May 2023 12:36:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231731AbjEVQgJ (ORCPT ); Mon, 22 May 2023 12:36:09 -0400 Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9C69FF1; Mon, 22 May 2023 09:36:07 -0700 (PDT) Received: by mail-ot1-x334.google.com with SMTP id 46e09a7af769-6af6b6837acso1425688a34.1; Mon, 22 May 2023 09:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684773367; x=1687365367; 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=gE6VEcd6SehC09OLRuj4spGCMv2zTi9X2ZUJCimN/cs=; b=qXdboosidh2M1j9oJmWe2Vzv5zswW5Ta90fX/3QP4glyDrkjOQ1uDu+ghyYwnWa5od Qh1n+VgXDY44q/AmQvJWADGHdU7sAdQLubfxKSi7HDEkrEgN+yr2e6r1HqeCWXnZ8OIy MRRiCa9SPdionSCLe26ou5pHylT2HKDb69XeJdUTcjIjCa2S6EqvJnXwnNyPeoRuWmpA NGD3vMOzZkV6Ay5aUTr4y5b7f0SaeMFL97RGaJ50A/Rqbk3AicN2McLe9AVMiPqjkp3c 4JJBq3v3lBKizJ3t/1qrAbvIoBOphCFVzx/3v+R8c1ECmKJDXIXbGXXOPRauY9refL8e yw4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684773367; x=1687365367; 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=gE6VEcd6SehC09OLRuj4spGCMv2zTi9X2ZUJCimN/cs=; b=Z02EZAQn1ChShvmOJXwZOJaZpKVeQR5b0vvJtO0lVpE0HIrmVREGxxdKm9bNs/k020 v8NBywGoPHbEku6zCjRj3YAjDVG+g4K9nsPYNqvIdn/LoOZaL0BcmcXQfr3986cPv1pq qvcKFv4cPuwuiXkjaIwHeDLQSB9KHI5fntIdsvKDk/fa9bsnC8ua2h0wt+e7n5rH47md IZpiFCWoOopHbMow9Ckb1c4ZW3vgWRphtFUe5DI6g17eFfyIWcZ1Podkx3jZiXOZHyuq hsv508mAWpDyg7g/Fa2dAcMbiw3m6aIhdvVmQTxIrOIXISpjNnN/1FRi4fP7TulRAD9f nhcQ== X-Gm-Message-State: AC+VfDzMTiLPt6a7TuhC+9gkDci24m9dMMnvuTxnli+jaDqYD/y/FrVW bKx2AsMFTqCBZclH8ZXIPw6N7Rr846o0iLIY4+A= X-Google-Smtp-Source: ACHHUZ5Q2A3P446/ClvG0cbEyqJw5C98bhbbV/2l1fuktu3rGaOBg+8fbLOO5RN66inW4ZDkM7KG57e8jxOpWY0meHE= X-Received: by 2002:a05:6870:6183:b0:192:736c:ae28 with SMTP id a3-20020a056870618300b00192736cae28mr4686856oah.58.1684773366819; Mon, 22 May 2023 09:36:06 -0700 (PDT) MIME-Version: 1.0 References: <20230522171557.32027acf@canb.auug.org.au> In-Reply-To: From: Alex Deucher Date: Mon, 22 May 2023 12:35:55 -0400 Message-ID: Subject: Re: linux-next: build failure after merge of the amdgpu tree To: Nick Desaulniers 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 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 allmodconf= ig > > clang-17) failed like this: > > > > drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c:146:54: error: format specifie= s type 'unsigned long long' but the argument has type 'dma_addr_t' (aka 'un= signed 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 the > AMDGPU tree. > 1. https://lore.kernel.org/lkml/20230522171557.32027acf@canb.auug.org.au/ > 2. https://lore.kernel.org/lkml/20230522171145.38a8bd4d@canb.auug.org.au/ > 3. https://lore.kernel.org/lkml/20230522170031.5fb87a64@canb.auug.org.au/ > > Our CI is red as a result. > https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/5= 045716034/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. Alex > > > > > -- > > Cheers, > > Stephen Rothwell > > Thanks for reporting these, Stephen.