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 94123C7EE31 for ; Mon, 22 May 2023 16:30:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232836AbjEVQaE (ORCPT ); Mon, 22 May 2023 12:30:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232924AbjEVQ3x (ORCPT ); Mon, 22 May 2023 12:29:53 -0400 Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4DB75FD for ; Mon, 22 May 2023 09:29:52 -0700 (PDT) Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-64d3e5e5980so3695699b3a.2 for ; Mon, 22 May 2023 09:29:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1684772991; x=1687364991; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=FAkKcxK0XGy2Mfzb+3G4ZZig1suIGlcPXW3ZGdiAVSA=; b=gKMZ7XX4R2VVh8UsICMu0Rsyke0XrW2c+iRdHHRt3WLWOycJO32Iy04zCNODgFfd4R D4saMqcStc+sMP83KAqZHxF2yw/+92d97pUSNL7+DK5dQh/BOcnBAvDWU4hq8cJ8XihR OQLsKlHjjTFnvdXZubmLG44LfUVnxjSa3p52hs0BL3K4cwahT81s2Hx9+Bdv0qu7aLbF ypDYOKDI/6neL9kriVO66DUnXuCexjPu/JMQ3Be9CuN3HLdNfGmSa68Haud473dFlm6G uHkL8p193PWUoqP27x/gjhz+62Sa43tbwWREDY4bohSEJx4mwzjNkV4JO3kgrnBTjdwE e0yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684772991; x=1687364991; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=FAkKcxK0XGy2Mfzb+3G4ZZig1suIGlcPXW3ZGdiAVSA=; b=JSgyKl7pMpgcdh7MUCF4vmP+5ZYaHHn7TjuMf5//qM6Xq4Iwv9RQORPFUJrsHLl1/p /p+t31lWAXpVs7nyj8DIOJHhIdEmtaqJU516q+LBN148xXIQ+Tnxu9Dezz6wlbQ7ugPM YX7mhdoWL/tQ4dl7s+Q6f33X/PUuO2tOwcfYXbXwetFJB6xYiABsSO0ifN8xiYZJSeRk GubkNICh3054c+9AWRDoWyH/qREVTLiD3s0YUecF1+rScx8QAv9H2hBsrFkc6e0a5iCR //HvlkpGWQp9ryzD9a//IxYGxeL4wQReaEv5YhkgvE9Aoorosa2pzlFaXpL7waTAu25o tuLg== X-Gm-Message-State: AC+VfDwFv910tknMXa8MGUUVidv1dHEAT/xGZGGsC+eqSgExnJz9Ii77 Xwv1vglV64b0wvY715or9PUoIQ== X-Google-Smtp-Source: ACHHUZ5GdkVEPhjfb0wo1cG4veSdeV7NVtA9Usryrtr3shd7i6atVl1mHOPkqK3UwqkqrLKZFvovrA== X-Received: by 2002:a05:6a00:1307:b0:64b:256:204c with SMTP id j7-20020a056a00130700b0064b0256204cmr14436082pfu.20.1684772991208; Mon, 22 May 2023 09:29:51 -0700 (PDT) Received: from google.com ([2620:15c:2d1:203:f7a6:d766:a921:add2]) by smtp.gmail.com with ESMTPSA id r14-20020a63514e000000b0050f93a3586fsm4597933pgl.37.2023.05.22.09.29.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 May 2023 09:29:50 -0700 (PDT) Date: Mon, 22 May 2023 09:29:44 -0700 From: Nick Desaulniers To: Alex Deucher Cc: Alex Deucher , Alex Deucher , Felix Kuehling , Harish Kasiviswanathan , Rajneesh Bhardwaj , Linux Kernel Mailing List , Linux Next Mailing List , Stephen Rothwell , llvm@lists.linux.dev, Linus Torvalds Subject: Re: linux-next: build failure after merge of the amdgpu tree Message-ID: References: <20230522171557.32027acf@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230522171557.32027acf@canb.auug.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org 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 allmodconfig > clang-17) failed like this: > > drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c:146:54: error: format specifies 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 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/5045716034/jobs/9053211936 When will AMD start testing their kernels with Clang? > > -- > Cheers, > Stephen Rothwell Thanks for reporting these, Stephen.