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 X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 802A9C388F2 for ; Mon, 2 Nov 2020 10:28:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1B15121D40 for ; Mon, 2 Nov 2020 10:28:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ffwll.ch header.i=@ffwll.ch header.b="EzwfEuuE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728400AbgKBK22 (ORCPT ); Mon, 2 Nov 2020 05:28:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728005AbgKBK21 (ORCPT ); Mon, 2 Nov 2020 05:28:27 -0500 Received: from mail-oi1-x243.google.com (mail-oi1-x243.google.com [IPv6:2607:f8b0:4864:20::243]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E7D47C0617A6 for ; Mon, 2 Nov 2020 02:28:26 -0800 (PST) Received: by mail-oi1-x243.google.com with SMTP id 6so5025988oiy.4 for ; Mon, 02 Nov 2020 02:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=EzwfEuuEwGYTUTjIasAnUKUIVmBIxn7qJYQhUc2GVEKajha3SO3J3d/VjzMgnwV94F V1xFvThPUl79p5+V+oEa5uZ2gpuitZ5MzSvlI5wHu8TwB48Z8uCSz1bX+J83hOAQl2Mc ybmPexJOB3IDKeTvAmmWQSMGJBSZzm4EiWwGE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=TKsGDCI4l9zCRkysmkjKV02pknocWnxeU9aOmLQoswo+vZqdjqozKCA8f5YvUrxQTZ O9XnkdUo/ueBsXEdtpakTwnoWEwmLTGVWvroWcnRPIt+Q0eRxFz1J0r30a7yhImiACZV lWoyLeczAXlf/1huZEUoiF3mmaQeYMiRrKfidAsm7Z8SfCKtkJJjQOk9qaqXydRCtebG fPetpuQK21JQJEQjEmccOGZXM0jRbpNlPTUTUazyi5uC+w4GAv8l1PWIvDYN3sW7kOF/ vsqw+j/3f3zWPyj+IkcQhh4leHVQrPRunVSen4edZlq1Oc8Cq9s5/f++feat7YzwN+HG jqcQ== X-Gm-Message-State: AOAM532zd1pSvEtJob68cH59zbDTijLDr1BHR0aAzzfqVBvzbco9TFsG hi6DdEz0fu6ajdK8qHd94CeSNkPIzo2D8lrooqcIeA== X-Google-Smtp-Source: ABdhPJxtPz32ksTu7x/wIQLWRExfPZVZ9cFoMP8T8mP3YC5ZyI58He8otzTX9cJ+0Sx2RumLcBUlS7qWt0oefuIvIy0= X-Received: by 2002:aca:b141:: with SMTP id a62mr8909832oif.101.1604312906398; Mon, 02 Nov 2020 02:28:26 -0800 (PST) MIME-Version: 1.0 References: <20201102124327.2f82b2a7@canb.auug.org.au> <20201102052254-mutt-send-email-mst@kernel.org> In-Reply-To: <20201102052254-mutt-send-email-mst@kernel.org> From: Daniel Vetter Date: Mon, 2 Nov 2020 11:28:15 +0100 Message-ID: Subject: Re: linux-next: build failure after merge of the drm-misc tree To: "Michael S. Tsirkin" Cc: Stephen Rothwell , Christoph Hellwig , Intel Graphics , DRI , =?UTF-8?Q?Christian_K=C3=B6nig?= , Joerg Roedel , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 2, 2020 at 11:23 AM Michael S. Tsirkin wrote: > > On Mon, Nov 02, 2020 at 10:28:34AM +0100, Daniel Vetter wrote: > > On Mon, Nov 2, 2020 at 2:43 AM Stephen Rothwell wrote: > > > > > > Hi all, > > > > > > After merging the drm-misc tree, today's linux-next build (arm > > > multi_v7_defconfig) failed like this: > > > > > > In file included from drivers/gpu/drm/nouveau/nouveau_ttm.c:26: > > > include/linux/swiotlb.h: In function 'swiotlb_max_mapping_size': > > > include/linux/swiotlb.h:99:9: error: 'SIZE_MAX' undeclared (first use in this function) > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > include/linux/swiotlb.h:7:1: note: 'SIZE_MAX' is defined in header ''; did you forget to '#include '? > > > 6 | #include > > > +++ |+#include > > > 7 | #include > > > include/linux/swiotlb.h:99:9: note: each undeclared identifier is reported only once for each function it appears in > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > > > > Caused by commit > > > > > > abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > > > > but only exposed by commit > > > > > > 4dbafbd30aef ("drm/nouveu: fix swiotlb include") > > > > > > I applied the following fix for today: > > > > > > From: Stephen Rothwell > > > Date: Mon, 2 Nov 2020 12:34:57 +1100 > > > Subject: [PATCH] swiotlb: using SIZE_MAX needs limits.h included > > > > > > Fixes: abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > Signed-off-by: Stephen Rothwell > > > > I think simplest if this lands through dma-api tree into current -rc > > kernels. Or should we just put this into drm-misc-next since that's > > where the problem shows up? Christoph, any preference from dma-api > > side? > > -Daniel > > > Or I can merge it since I merged the original patch causing the > issue ... Works for me too. -Daniel > > > > --- > > > include/linux/swiotlb.h | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h > > > index 513913ff7486..ed9de7855d3b 100644 > > > --- a/include/linux/swiotlb.h > > > +++ b/include/linux/swiotlb.h > > > @@ -5,6 +5,9 @@ > > > #include > > > #include > > > #include > > > +#ifndef CONFIG_SWIOTLB > > > +#include > > > +#endif > > > > > > struct device; > > > struct page; > > > -- > > > 2.28.0 > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > > > > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch 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 X-Spam-Level: X-Spam-Status: No, score=-9.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 962BBC388F9 for ; Mon, 2 Nov 2020 10:28:29 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2B6682225E for ; Mon, 2 Nov 2020 10:28:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=ffwll.ch header.i=@ffwll.ch header.b="EzwfEuuE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2B6682225E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 136716E492; Mon, 2 Nov 2020 10:28:28 +0000 (UTC) Received: from mail-oi1-x241.google.com (mail-oi1-x241.google.com [IPv6:2607:f8b0:4864:20::241]) by gabe.freedesktop.org (Postfix) with ESMTPS id 076116E492 for ; Mon, 2 Nov 2020 10:28:27 +0000 (UTC) Received: by mail-oi1-x241.google.com with SMTP id 6so5025989oiy.4 for ; Mon, 02 Nov 2020 02:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=EzwfEuuEwGYTUTjIasAnUKUIVmBIxn7qJYQhUc2GVEKajha3SO3J3d/VjzMgnwV94F V1xFvThPUl79p5+V+oEa5uZ2gpuitZ5MzSvlI5wHu8TwB48Z8uCSz1bX+J83hOAQl2Mc ybmPexJOB3IDKeTvAmmWQSMGJBSZzm4EiWwGE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=KuLlYvpQFnS+V6E83SnVK4HnDhJ6U//+2J4o6kKD4KJ5xe9IuobMUx3YJmMNGrNxiH n5Kp/nzzh2jrGMae7tmY6qxZkxuK4wQtNalfnsXWb/hGxJW86RAmnkNN+auHDu55ruL4 ZX4t/Fo/BVlb32Y8jlY+XdvxhqcQLemT2ud+or3qcuhSKdeP3xssMI2lf4g6BlxEMi/5 Pjv/ecvRc0aeOXMaiDBKYEtkJQawCSi0+sK1AGwMJKGE1hnTQPdnbaCaw3rPKdu9bTrF qkqDBq1gjdtnaEAdG03vrmcLnvagi0VNOefnhNOWHrpyusKYtO0SPfnLAoYilwVz4xdb 6XHw== X-Gm-Message-State: AOAM530ZorvH0Gm9fbeE6ZjmEFB2RHckylyuBGPz+NSZPGAxwUtqco+v 7oD+ANm+EkmqsWUuwivyZUZuQnVLpu6GGOBnSKirzw== X-Google-Smtp-Source: ABdhPJxtPz32ksTu7x/wIQLWRExfPZVZ9cFoMP8T8mP3YC5ZyI58He8otzTX9cJ+0Sx2RumLcBUlS7qWt0oefuIvIy0= X-Received: by 2002:aca:b141:: with SMTP id a62mr8909832oif.101.1604312906398; Mon, 02 Nov 2020 02:28:26 -0800 (PST) MIME-Version: 1.0 References: <20201102124327.2f82b2a7@canb.auug.org.au> <20201102052254-mutt-send-email-mst@kernel.org> In-Reply-To: <20201102052254-mutt-send-email-mst@kernel.org> From: Daniel Vetter Date: Mon, 2 Nov 2020 11:28:15 +0100 Message-ID: Subject: Re: linux-next: build failure after merge of the drm-misc tree To: "Michael S. Tsirkin" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stephen Rothwell , Joerg Roedel , Intel Graphics , Linux Kernel Mailing List , DRI , Christoph Hellwig , Linux Next Mailing List , =?UTF-8?Q?Christian_K=C3=B6nig?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Mon, Nov 2, 2020 at 11:23 AM Michael S. Tsirkin wrote: > > On Mon, Nov 02, 2020 at 10:28:34AM +0100, Daniel Vetter wrote: > > On Mon, Nov 2, 2020 at 2:43 AM Stephen Rothwell wrote: > > > > > > Hi all, > > > > > > After merging the drm-misc tree, today's linux-next build (arm > > > multi_v7_defconfig) failed like this: > > > > > > In file included from drivers/gpu/drm/nouveau/nouveau_ttm.c:26: > > > include/linux/swiotlb.h: In function 'swiotlb_max_mapping_size': > > > include/linux/swiotlb.h:99:9: error: 'SIZE_MAX' undeclared (first use in this function) > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > include/linux/swiotlb.h:7:1: note: 'SIZE_MAX' is defined in header ''; did you forget to '#include '? > > > 6 | #include > > > +++ |+#include > > > 7 | #include > > > include/linux/swiotlb.h:99:9: note: each undeclared identifier is reported only once for each function it appears in > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > > > > Caused by commit > > > > > > abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > > > > but only exposed by commit > > > > > > 4dbafbd30aef ("drm/nouveu: fix swiotlb include") > > > > > > I applied the following fix for today: > > > > > > From: Stephen Rothwell > > > Date: Mon, 2 Nov 2020 12:34:57 +1100 > > > Subject: [PATCH] swiotlb: using SIZE_MAX needs limits.h included > > > > > > Fixes: abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > Signed-off-by: Stephen Rothwell > > > > I think simplest if this lands through dma-api tree into current -rc > > kernels. Or should we just put this into drm-misc-next since that's > > where the problem shows up? Christoph, any preference from dma-api > > side? > > -Daniel > > > Or I can merge it since I merged the original patch causing the > issue ... Works for me too. -Daniel > > > > --- > > > include/linux/swiotlb.h | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h > > > index 513913ff7486..ed9de7855d3b 100644 > > > --- a/include/linux/swiotlb.h > > > +++ b/include/linux/swiotlb.h > > > @@ -5,6 +5,9 @@ > > > #include > > > #include > > > #include > > > +#ifndef CONFIG_SWIOTLB > > > +#include > > > +#endif > > > > > > struct device; > > > struct page; > > > -- > > > 2.28.0 > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > > > > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel 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 X-Spam-Level: X-Spam-Status: No, score=-9.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 76845C00A89 for ; Mon, 2 Nov 2020 10:28:33 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0299D21D40 for ; Mon, 2 Nov 2020 10:28:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=ffwll.ch header.i=@ffwll.ch header.b="EzwfEuuE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0299D21D40 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ffwll.ch Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=intel-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 25C476E4AA; Mon, 2 Nov 2020 10:28:28 +0000 (UTC) Received: from mail-oi1-x241.google.com (mail-oi1-x241.google.com [IPv6:2607:f8b0:4864:20::241]) by gabe.freedesktop.org (Postfix) with ESMTPS id 076586E4AA for ; Mon, 2 Nov 2020 10:28:27 +0000 (UTC) Received: by mail-oi1-x241.google.com with SMTP id m13so5101013oih.8 for ; Mon, 02 Nov 2020 02:28:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=EzwfEuuEwGYTUTjIasAnUKUIVmBIxn7qJYQhUc2GVEKajha3SO3J3d/VjzMgnwV94F V1xFvThPUl79p5+V+oEa5uZ2gpuitZ5MzSvlI5wHu8TwB48Z8uCSz1bX+J83hOAQl2Mc ybmPexJOB3IDKeTvAmmWQSMGJBSZzm4EiWwGE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Z8GQ3+dlPgWj8N6iGHuphE6RpytAvFZo39Sbtwdhws=; b=iTiiofM28GrpjqGDr+aB4PdJq9xZ6pBOTbhcqg1Wz9fMVTIrMJl9qKazWTqJM7sCfE HO375LTFq6Omg5FPyoUPBl3HvtpeZlxCifKvoBRqX9I4uzFDcsjYDg05TIRM2hC/U0go k9TQW4a71UVUajBABWE1lPQLWb8diAHevOSfIo0ltBC0QiIJ6pRivebpvsfkls2sYkrt WxoqSougMb4ny7ts1moTWHAH++tPcX0wIMmyqwb3gbsx15QuvPuo5QyOBpaMVftY7h/J y7DyUnMaHoyT2VdPcOeZIoF1IJc7K32hWVkBDBCj91C8qi9vVn0A97BC26ox106DTxt3 4Zbw== X-Gm-Message-State: AOAM532KEecguy3nK47VedSXzE7ihGG8A73Gv+ybK1KGvNau0LVRSea2 nsJ2/2gh9R+NHIprs2p3x2vBGDLIa1Lau/YnoAvi7g== X-Google-Smtp-Source: ABdhPJxtPz32ksTu7x/wIQLWRExfPZVZ9cFoMP8T8mP3YC5ZyI58He8otzTX9cJ+0Sx2RumLcBUlS7qWt0oefuIvIy0= X-Received: by 2002:aca:b141:: with SMTP id a62mr8909832oif.101.1604312906398; Mon, 02 Nov 2020 02:28:26 -0800 (PST) MIME-Version: 1.0 References: <20201102124327.2f82b2a7@canb.auug.org.au> <20201102052254-mutt-send-email-mst@kernel.org> In-Reply-To: <20201102052254-mutt-send-email-mst@kernel.org> From: Daniel Vetter Date: Mon, 2 Nov 2020 11:28:15 +0100 Message-ID: To: "Michael S. Tsirkin" Subject: Re: [Intel-gfx] linux-next: build failure after merge of the drm-misc tree X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stephen Rothwell , Joerg Roedel , Intel Graphics , Linux Kernel Mailing List , DRI , Christoph Hellwig , Linux Next Mailing List , =?UTF-8?Q?Christian_K=C3=B6nig?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Mon, Nov 2, 2020 at 11:23 AM Michael S. Tsirkin wrote: > > On Mon, Nov 02, 2020 at 10:28:34AM +0100, Daniel Vetter wrote: > > On Mon, Nov 2, 2020 at 2:43 AM Stephen Rothwell wrote: > > > > > > Hi all, > > > > > > After merging the drm-misc tree, today's linux-next build (arm > > > multi_v7_defconfig) failed like this: > > > > > > In file included from drivers/gpu/drm/nouveau/nouveau_ttm.c:26: > > > include/linux/swiotlb.h: In function 'swiotlb_max_mapping_size': > > > include/linux/swiotlb.h:99:9: error: 'SIZE_MAX' undeclared (first use in this function) > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > include/linux/swiotlb.h:7:1: note: 'SIZE_MAX' is defined in header ''; did you forget to '#include '? > > > 6 | #include > > > +++ |+#include > > > 7 | #include > > > include/linux/swiotlb.h:99:9: note: each undeclared identifier is reported only once for each function it appears in > > > 99 | return SIZE_MAX; > > > | ^~~~~~~~ > > > > > > Caused by commit > > > > > > abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > > > > but only exposed by commit > > > > > > 4dbafbd30aef ("drm/nouveu: fix swiotlb include") > > > > > > I applied the following fix for today: > > > > > > From: Stephen Rothwell > > > Date: Mon, 2 Nov 2020 12:34:57 +1100 > > > Subject: [PATCH] swiotlb: using SIZE_MAX needs limits.h included > > > > > > Fixes: abe420bfae52 ("swiotlb: Introduce swiotlb_max_mapping_size()") > > > Signed-off-by: Stephen Rothwell > > > > I think simplest if this lands through dma-api tree into current -rc > > kernels. Or should we just put this into drm-misc-next since that's > > where the problem shows up? Christoph, any preference from dma-api > > side? > > -Daniel > > > Or I can merge it since I merged the original patch causing the > issue ... Works for me too. -Daniel > > > > --- > > > include/linux/swiotlb.h | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h > > > index 513913ff7486..ed9de7855d3b 100644 > > > --- a/include/linux/swiotlb.h > > > +++ b/include/linux/swiotlb.h > > > @@ -5,6 +5,9 @@ > > > #include > > > #include > > > #include > > > +#ifndef CONFIG_SWIOTLB > > > +#include > > > +#endif > > > > > > struct device; > > > struct page; > > > -- > > > 2.28.0 > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > > > > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx