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 7F3E3C43334 for ; Fri, 22 Jul 2022 10:00:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235022AbiGVKAT (ORCPT ); Fri, 22 Jul 2022 06:00:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38152 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234516AbiGVKAN (ORCPT ); Fri, 22 Jul 2022 06:00:13 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8734926F4 for ; Fri, 22 Jul 2022 03:00:11 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 3FE4868AFE; Fri, 22 Jul 2022 12:00:08 +0200 (CEST) Date: Fri, 22 Jul 2022 12:00:06 +0200 From: Christoph Hellwig To: Tvrtko Ursulin Cc: Robert Beckett , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , Daniel Vetter , kernel@collabora.com, Christoph Hellwig , Thomas Hellstrom , Matthew Auld , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] drm/i915: stop using swiotlb Message-ID: <20220722100006.GC14113@lst.de> References: <20220721174307.1085741-1-bob.beckett@collabora.com> <118ae557-a7cb-10b2-9198-2ceb92948dd7@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <118ae557-a7cb-10b2-9198-2ceb92948dd7@linux.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 22, 2022 at 10:13:48AM +0100, Tvrtko Ursulin wrote: > Christoph - ack from you? Also, if we merge it via the normal process it > will hit 5.21 only. Does that work for you? While I'd like to kill off swiotlb_max_segment rather sooner than later I'm fine with following the normal process. But I don't think there will be a 5.21 with the recent Linux versioning practice :)